Asked by:
The computer failed to take a snapshot of the volume for backup
Question
-
Hi- I realize this is probably kindergarten stuff for some of us, but I'm stumped. Basic problem is WHS backup fails on one of my computers, and the system gets very slow while it's failing. I think I've traced the problem to a "VolSnap" error on the client.
Client's Event Viewer returns the following:
Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 12297
Date: 6/29/2009
Time: 11:59:21 PM
User: N/A
Computer: FRANKSDESKTOP
Description:
Volume Shadow Copy Service error: The I/O writes cannot be flushed during the shadow copy creation period on volume \\?\Volume{29f1e8e8-a1b8-11da-bec2-806d6172696f}\. The volume index in the shadow copy set is 0. Error details: Flush[0x8000ffff], Release[0x00000000], OnRun[0x00000000].For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 43 4f 52 4c 4f 56 4c 43 CORLOVLC
0008: 35 38 39 00 00 00 00 00 589.....
0010: 43 4f 52 4c 4f 56 4c 43 CORLOVLC
0018: 34 38 36 00 00 00 00 00 486.....
When I follow the link, this is what I get:Top of Form 1
&&&&&&&
Details
Product:
Windows Operating System
ID:
12297
Source:
VSS
Version:
5.2.3790.1830
Message:
Volume Shadow Copy Service: The system may be low on resources.
Explanation
This event indicates that Volume Shadow Copy Service was not able to allocate enough system resources to perform an operation.
Cause
Possible causes include:
The system is low on memory.
The system is low on CPU resources.
The system has a high disk I/O load.
User Action
Do one or more of the following:
Monitor the system resources (CPU usage and disk I/O performance) to identify what is causing the system to be low on resources.
Schedule Volume Shadow Copy Service or other operations during the least busy periods for the system.
Move the Diff Area to a different, dedicated volume.
But using the Performance monitor under Admin Tools did not reveal any apparent performance issues.
Any ideas? Thanks in advance- Frank
Tuesday, June 30, 2009 6:41 AM
All replies
-
Please check free disk space for all of your hard disks / partitions. Disks could be running low on free space. If free space is OK please try running chkdsk /r on each of your partitions. In addition you can defragment the harddrive (after running chkdsk). Please note that chkdsk and defrag may take a long time to run and there's no guarantee it will help.
Could also be failing hardware (memory, disk cabling disk controller) or a driver problem, particularly if any of the storage/chipset drivers was recently updated.Tuesday, June 30, 2009 7:36 AMModerator -
Thanks for the quick reply but none of these have helped. I did search previous threads on the subject but none of the suggestions therein helped either.
There are three volumes and they range from 1/10 to 1/6 full, so there's plenty of free space. Other programs access them OK so I doubt it's a driver or hardware problem.
I did notice when running chkdsk from a CMD window that it returned a "could not lock drive" error, and I had to tell it to check the volumes when I rebooted. Does VolSnap have to lock the volume to take a snapshot?
System is an ASUS M3A32-MVP board, Phenom II 940, no overclocks, 2GB RAM, WinXP SP3.Wednesday, July 1, 2009 3:22 AM -
Thanks for the quick reply but none of these have helped. I did search previous threads on the subject but none of the suggestions therein helped either.
There are three volumes and they range from 1/10 to 1/6 full, so there's plenty of free space. Other programs access them OK so I doubt it's a driver or hardware problem.
I did notice when running chkdsk from a CMD window that it returned a "could not lock drive" error, and I had to tell it to check the volumes when I rebooted. Does VolSnap have to lock the volume to take a snapshot?
System is an ASUS M3A32-MVP board, Phenom II 940, no overclocks, 2GB RAM, WinXP SP3.
You could try opening a command prompt and typing vssadmin list writers, then see if there are any errors. (Also, you could try vssadmin list providers and see what it shows.)Wednesday, July 1, 2009 4:49 AMModerator -
i well i still am haveing a problem like that. i too have done all, what i could find on the web site about this problem. i question to you is " Is the hard drive that is giving you a problem a 1 tb or larger ? is it a WD " green " drive ?" " you have done the " do not allow the computer to power save on the nic"? " i will know latter today if i got my problem fixed because i just changed out my "1tb wd green drive" and put in a 640 gb in to my xp 32 bit sp3 case. i have been hearing a lot of problems with hard drives larger than 1tb in a xp 32 bit set up. even after the the flashing of the Motherboards bios." its some thing with windows xp. OK have a great day and lots of funWednesday, July 1, 2009 6:20 AM
-
OK, we may be getting somewhere. "Vssadmin list writers" shows a "WMI Writer" that has failed, and several others that are stable:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.vssadmin 1.0 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.Writer name: 'Microsoft Writer (Service State)'
Writer Id: {e38c2e3c-d4fb-4f4d-9550-fcafda8aae9a}
Writer Instance Id: {991d6931-2a15-4265-9712-152d81f56137}
State: [1] StableWriter name: 'Microsoft Writer (Bootable State)'
Writer Id: {f2436e37-09f5-41af-9b2a-4ca2435dbfd5}
Writer Instance Id: {3c040a48-5ef6-4aa7-a42e-86277e4daff0}
State: [1] StableWriter name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {cc1d5dbc-4ce6-4f34-9d32-b5d3af18f5d3}
State: [1] StableWriter name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {72d9e2ae-8608-41be-821a-447370f2bc32}
State: [7] FailedGlad we can cut-and-paste these!
"Vssadmin list providers" returns the following:
vssadmin 1.0 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.Provider name: 'MS Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7The hard drive is a Seagate ST3500320AS, a half-terabyte with three NTFS volumes.
Thoughts?Thursday, July 2, 2009 12:50 AM -
OK, we may be getting somewhere. "Vssadmin list writers" shows a "WMI Writer" that has failed, and several others that are stable:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.vssadmin 1.0 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.Writer name: 'Microsoft Writer (Service State)'
Writer Id: {e38c2e3c-d4fb-4f4d-9550-fcafda8aae9a}
Writer Instance Id: {991d6931-2a15-4265-9712-152d81f56137}
State: [1] StableWriter name: 'Microsoft Writer (Bootable State)'
Writer Id: {f2436e37-09f5-41af-9b2a-4ca2435dbfd5}
Writer Instance Id: {3c040a48-5ef6-4aa7-a42e-86277e4daff0}
State: [1] StableWriter name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {cc1d5dbc-4ce6-4f34-9d32-b5d3af18f5d3}
State: [1] StableWriter name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {72d9e2ae-8608-41be-821a-447370f2bc32}
State: [7] FailedGlad we can cut-and-paste these!
"Vssadmin list providers" returns the following:
vssadmin 1.0 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.Provider name: 'MS Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7The hard drive is a Seagate ST3500320AS, a half-terabyte with three NTFS volumes.
Thoughts?
You might try this WMI Diagnosis Utility and see if it helps.Friday, July 3, 2009 6:21 PMModerator -
Thanks for the tip. I did, and here are the results. Note that I tried re-registering the DCOM elements as directed, but the error cane up again:
19504 20:59:50 (0) ** WMIDiag v2.0 started on Friday, July 03, 2009 at 20:47.
19505 20:59:50 (0) **
19506 20:59:50 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - January 2007.
19507 20:59:50 (0) **
19508 20:59:50 (0) ** This script is not supported under any Microsoft standard support program or service.
19509 20:59:50 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
19510 20:59:50 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
19511 20:59:50 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
19512 20:59:50 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
19513 20:59:50 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
19514 20:59:50 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
19515 20:59:50 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
19516 20:59:50 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
19517 20:59:50 (0) ** of the possibility of such damages.
19518 20:59:50 (0) **
19519 20:59:50 (0) **
19520 20:59:50 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19521 20:59:50 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
19522 20:59:50 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19523 20:59:50 (0) **
19524 20:59:50 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19525 20:59:50 (0) ** Windows XP - No service pack - 32-bit (2600) - User 'FRANKSDESKTOP\FRANK WILSEY' on computer 'FRANKSDESKTOP'.
19526 20:59:50 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19527 20:59:50 (0) ** Environment: ........................................................................................................ OK..
19528 20:59:50 (0) ** System drive: ....................................................................................................... C: (Disk #0 Partition #0).
19529 20:59:50 (0) ** Drive type: ......................................................................................................... IDE (ST3500320AS).
19530 20:59:50 (0) ** There are no missing WMI system files: .............................................................................. OK.
19531 20:59:50 (0) ** There are no missing WMI repository files: .......................................................................... OK.
19532 20:59:50 (0) ** WMI repository state: ............................................................................................... N/A.
19533 20:59:50 (0) ** BEFORE running WMIDiag:
19534 20:59:50 (0) ** The WMI repository has a size of: ................................................................................... 8 MB.
19535 20:59:50 (0) ** - Disk free space on 'C:': .......................................................................................... 165835 MB.
19536 20:59:50 (0) ** - INDEX.BTR, 1458176 bytes, 7/3/2009 8:46:35 PM
19537 20:59:50 (0) ** - INDEX.MAP, 780 bytes, 7/3/2009 8:46:35 PM
19538 20:59:50 (0) ** - OBJECTS.DATA, 6815744 bytes, 7/3/2009 8:46:35 PM
19539 20:59:50 (0) ** - OBJECTS.MAP, 3424 bytes, 7/3/2009 8:46:35 PM
19540 20:59:50 (0) ** AFTER running WMIDiag:
19541 20:59:50 (0) ** The WMI repository has a size of: ................................................................................... 8 MB.
19542 20:59:50 (0) ** - Disk free space on 'C:': .......................................................................................... 164827 MB.
19543 20:59:50 (0) ** - INDEX.BTR, 1458176 bytes, 7/3/2009 8:48:05 PM
19544 20:59:50 (0) ** - INDEX.MAP, 780 bytes, 7/3/2009 8:48:05 PM
19545 20:59:50 (0) ** - OBJECTS.DATA, 6815744 bytes, 7/3/2009 8:48:05 PM
19546 20:59:50 (0) ** - OBJECTS.MAP, 3424 bytes, 7/3/2009 8:48:05 PM
19547 20:59:50 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19548 20:59:50 (0) ** Windows Firewall: ................................................................................................... NOT INSTALLED.
19549 20:59:50 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19550 20:59:50 (0) ** DCOM Status: ........................................................................................................ OK.
19551 20:59:50 (0) ** WMI registry setup: ................................................................................................. OK.
19552 20:59:50 (0) ** WMI Service has no dependents: ...................................................................................... OK.
19553 20:59:50 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
19554 20:59:50 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
19555 20:59:50 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19556 20:59:50 (0) ** WMI service DCOM setup: ............................................................................................. OK.
19557 20:59:50 (2) !! WARNING: WMI DCOM components registration is missing for the following EXE/DLLs: .................................... 6 WARNING(S)!
19558 20:59:50 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{7A0227F6-7108-11D1-AD90-00C04FD8FDFF}\InProcServer32)
19559 20:59:50 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{D71EE747-F455-4804-9DF6-2ED81025F2C1}\InProcServer32)
19560 20:59:50 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{ED51D12E-511F-4999-8DCD-C2BAC91BE86E}\InProcServer32)
19561 20:59:50 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{4C6055D8-84B9-4111-A7D3-6623894EEDB3}\InProcServer32)
19562 20:59:50 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{A1044801-8F7E-11D1-9E7C-00C04FC324A8}\InProcServer32)
19563 20:59:50 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{F7CE2E13-8C90-11D1-9E7B-00C04FC324A8}\InProcServer32)
19564 20:59:50 (0) ** => WMI System components are not properly registered as COM objects, which could make WMI to
19565 20:59:50 (0) ** fail depending on the operation requested.
19566 20:59:50 (0) ** => For a .DLL, you can correct the DCOM configuration by executing the 'REGSVR32.EXE <Filename.DLL>' command.
19567 20:59:50 (0) **
19568 20:59:50 (0) ** WMI ProgID registrations: ........................................................................................... OK.
19569 20:59:50 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
19570 20:59:50 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
19571 20:59:50 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
19572 20:59:50 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
19573 20:59:50 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19574 20:59:50 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
19575 20:59:50 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
19576 20:59:50 (0) ** - REMOVED ACE:
19577 20:59:50 (0) ** ACEType: &h0
19578 20:59:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
19579 20:59:50 (0) ** ACEFlags: &h0
19580 20:59:50 (0) ** ACEMask: &h1
19581 20:59:50 (0) ** DCOM_RIGHT_EXECUTE
19582 20:59:50 (0) **
19583 20:59:50 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
19584 20:59:50 (0) ** Removing default security will cause some operations to fail!
19585 20:59:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
19586 20:59:50 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
19587 20:59:50 (0) **
19588 20:59:50 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
19589 20:59:50 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
19590 20:59:50 (0) ** - REMOVED ACE:
19591 20:59:50 (0) ** ACEType: &h0
19592 20:59:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
19593 20:59:50 (0) ** ACEFlags: &h0
19594 20:59:50 (0) ** ACEMask: &h1
19595 20:59:50 (0) ** DCOM_RIGHT_EXECUTE
19596 20:59:50 (0) **
19597 20:59:50 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
19598 20:59:50 (0) ** Removing default security will cause some operations to fail!
19599 20:59:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
19600 20:59:50 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
19601 20:59:50 (0) **
19602 20:59:50 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
19603 20:59:50 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
19604 20:59:50 (0) ** - REMOVED ACE:
19605 20:59:50 (0) ** ACEType: &h0
19606 20:59:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
19607 20:59:50 (0) ** ACEFlags: &h0
19608 20:59:50 (0) ** ACEMask: &h1
19609 20:59:50 (0) ** DCOM_RIGHT_EXECUTE
19610 20:59:50 (0) **
19611 20:59:50 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
19612 20:59:50 (0) ** Removing default security will cause some operations to fail!
19613 20:59:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
19614 20:59:50 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
19615 20:59:50 (0) **
19616 20:59:50 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ..................................................................... MODIFIED.
19617 20:59:50 (1) !! ERROR: Actual trustee 'NT AUTHORITY\NETWORK SERVICE' DOES NOT match corresponding expected trustee rights (Actual->Default)
19618 20:59:50 (0) ** - ACTUAL ACE:
19619 20:59:50 (0) ** ACEType: &h0
19620 20:59:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
19621 20:59:50 (0) ** ACEFlags: &h2
19622 20:59:50 (0) ** CONTAINER_INHERIT_ACE
19623 20:59:50 (0) ** ACEMask: &h1
19624 20:59:50 (0) ** WBEM_ENABLE
19625 20:59:50 (0) ** - EXPECTED ACE:
19626 20:59:50 (0) ** ACEType: &h0
19627 20:59:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
19628 20:59:50 (0) ** ACEFlags: &h12
19629 20:59:50 (0) ** CONTAINER_INHERIT_ACE
19630 20:59:50 (0) ** INHERITED_ACE
19631 20:59:50 (0) ** ACEMask: &h13
19632 20:59:50 (0) ** WBEM_ENABLE
19633 20:59:50 (0) ** WBEM_METHOD_EXECUTE
19634 20:59:50 (0) ** WBEM_WRITE_PROVIDER
19635 20:59:50 (0) **
19636 20:59:50 (0) ** => The actual ACE has the right(s) '&h12 WBEM_METHOD_EXECUTE WBEM_WRITE_PROVIDER' removed!
19637 20:59:50 (0) ** This will cause some operations to fail!
19638 20:59:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the removed right.
19639 20:59:50 (0) ** For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
19640 20:59:50 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
19641 20:59:50 (0) ** The security diagnostic is based on the WMI namespace expected defaults.
19642 20:59:50 (0) ** A specific WMI application can always require a security setup different
19643 20:59:50 (0) ** than the WMI security defaults.
19644 20:59:50 (0) **
19645 20:59:50 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ..................................................................... MODIFIED.
19646 20:59:50 (1) !! ERROR: Actual trustee 'NT AUTHORITY\LOCAL SERVICE' DOES NOT match corresponding expected trustee rights (Actual->Default)
19647 20:59:50 (0) ** - ACTUAL ACE:
19648 20:59:50 (0) ** ACEType: &h0
19649 20:59:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
19650 20:59:50 (0) ** ACEFlags: &h2
19651 20:59:50 (0) ** CONTAINER_INHERIT_ACE
19652 20:59:50 (0) ** ACEMask: &h1
19653 20:59:50 (0) ** WBEM_ENABLE
19654 20:59:50 (0) ** - EXPECTED ACE:
19655 20:59:50 (0) ** ACEType: &h0
19656 20:59:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
19657 20:59:50 (0) ** ACEFlags: &h12
19658 20:59:50 (0) ** CONTAINER_INHERIT_ACE
19659 20:59:50 (0) ** INHERITED_ACE
19660 20:59:50 (0) ** ACEMask: &h13
19661 20:59:50 (0) ** WBEM_ENABLE
19662 20:59:50 (0) ** WBEM_METHOD_EXECUTE
19663 20:59:50 (0) ** WBEM_WRITE_PROVIDER
19664 20:59:50 (0) **
19665 20:59:50 (0) ** => The actual ACE has the right(s) '&h12 WBEM_METHOD_EXECUTE WBEM_WRITE_PROVIDER' removed!
19666 20:59:50 (0) ** This will cause some operations to fail!
19667 20:59:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the removed right.
19668 20:59:50 (0) ** For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
19669 20:59:50 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
19670 20:59:50 (0) ** The security diagnostic is based on the WMI namespace expected defaults.
19671 20:59:50 (0) ** A specific WMI application can always require a security setup different
19672 20:59:50 (0) ** than the WMI security defaults.
19673 20:59:50 (0) **
19674 20:59:50 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ..................................................................... MODIFIED.
19675 20:59:50 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
19676 20:59:50 (0) ** - REMOVED ACE:
19677 20:59:50 (0) ** ACEType: &h0
19678 20:59:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
19679 20:59:50 (0) ** ACEFlags: &h12
19680 20:59:50 (0) ** CONTAINER_INHERIT_ACE
19681 20:59:50 (0) ** INHERITED_ACE
19682 20:59:50 (0) ** ACEMask: &h13
19683 20:59:50 (0) ** WBEM_ENABLE
19684 20:59:50 (0) ** WBEM_METHOD_EXECUTE
19685 20:59:50 (0) ** WBEM_WRITE_PROVIDER
19686 20:59:50 (0) **
19687 20:59:50 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
19688 20:59:50 (0) ** Removing default security will cause some operations to fail!
19689 20:59:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
19690 20:59:50 (0) ** For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
19691 20:59:50 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
19692 20:59:50 (0) ** The security diagnostic is based on the WMI namespace expected defaults.
19693 20:59:50 (0) ** A specific WMI application can always require a security setup different
19694 20:59:50 (0) ** than the WMI security defaults.
19695 20:59:50 (0) **
19696 20:59:50 (0) **
19697 20:59:50 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
19698 20:59:50 (0) ** DCOM security error(s) detected: .................................................................................... 3.
19699 20:59:50 (0) ** WMI security warning(s) detected: ................................................................................... 0.
19700 20:59:50 (0) ** WMI security error(s) detected: ..................................................................................... 3.
19701 20:59:50 (0) **
19702 20:59:50 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
19703 20:59:50 (1) !! ERROR: Overall WMI security status: ................................................................................. ERROR!
19704 20:59:50 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
19705 20:59:50 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 2.
19706 20:59:50 (0) ** - ROOT/SUBSCRIPTION, MSFT_UCScenarioControl.Name="Microsoft WMI Updating Consumer Scenario Control".
19707 20:59:50 (0) ** 'SELECT * FROM __InstanceOperationEvent WHERE TargetInstance ISA 'MSFT_UCScenario''
19708 20:59:50 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
19709 20:59:50 (0) ** 'select * from MSFT_SCMEventLogEvent'
19710 20:59:50 (0) **
19711 20:59:50 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
19712 20:59:50 (0) ** WMI ADAP status: .................................................................................................... OK.
19713 20:59:50 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 1 NAMESPACE(S)!
19714 20:59:50 (0) ** - ROOT/SERVICEMODEL.
19715 20:59:50 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
19716 20:59:50 (0) ** use an encrypted connection by specifying the PACKET PRIVACY authentication level.
19717 20:59:50 (0) ** (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
19718 20:59:50 (0) ** i.e. 'WMIC.EXE /NODE:"FRANKSDESKTOP" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
19719 20:59:50 (0) **
19720 20:59:50 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
19721 20:59:50 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
19722 20:59:50 (0) ** WMI GET operations: ................................................................................................. OK.
19723 20:59:50 (0) ** WMI MOF representations: ............................................................................................ OK.
19724 20:59:50 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
19725 20:59:50 (1) !! ERROR: WMI ENUMERATION operation errors reported: ................................................................... 1 ERROR(S)!
19726 20:59:50 (0) ** - Root/Default, InstancesOf, 'SystemRestore', 0x80080005 - Server execution failed.
19727 20:59:50 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\SR.MOF'
19728 20:59:50 (0) **
19729 20:59:50 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
19730 20:59:50 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
19731 20:59:50 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
19732 20:59:50 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
19733 20:59:50 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
19734 20:59:50 (0) ** WMI static instances retrieved: ..................................................................................... 814.
19735 20:59:50 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
19736 20:59:50 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
19737 20:59:50 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19738 20:59:50 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
19739 20:59:50 (0) ** DCOM: ............................................................................................................. 13.
19740 20:59:50 (0) ** WINMGMT: .......................................................................................................... 2.
19741 20:59:50 (0) ** WMIADAPTER: ....................................................................................................... 0.
19742 20:59:50 (0) ** => Verify the WMIDiag LOG at line #19089 for more details.
19743 20:59:50 (0) **
19744 20:59:50 (0) ** # of additional Event Log events AFTER WMIDiag execution:
19745 20:59:50 (0) ** DCOM: ............................................................................................................. 1.
19746 20:59:50 (0) ** WINMGMT: .......................................................................................................... 0.
19747 20:59:50 (0) ** WMIADAPTER: ....................................................................................................... 0.
19748 20:59:50 (2) !! WARNING: => Verify the WMIDiag LOG at line #19156 for more details.
19749 20:59:50 (0) **
19750 20:59:50 (0) ** 1 error(s) 0x80080005 - (WBEM_UNKNOWN) This error code is external to WMI.
19751 20:59:50 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19752 20:59:50 (0) ** WMI Registry key setup: ............................................................................................. OK.
19753 20:59:50 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19754 20:59:50 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19755 20:59:50 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19756 20:59:50 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19757 20:59:50 (0) **
19758 20:59:50 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19759 20:59:50 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
19760 20:59:50 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19761 20:59:50 (0) **
19762 20:59:50 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\DOCUMENTS AND SETTINGS\FRANK WILSEY\LOCAL SETTINGS\TEMP\WMIDIAG-V2.0_XP___.CLI.RTM.32_FRANKSDESKTOP_2009.07.03_20.47.53.LOG' for details.
19763 20:59:50 (0) **
19764 20:59:50 (0) ** WMIDiag v2.0 ended on Friday, July 03, 2009 at 20:59 (W:67 E:28 S:1).Saturday, July 4, 2009 1:32 AM -
Update.............................
Last night, we had a successful automatic backup. WMI writer showed "stable" when the backup was done.
This morning, it tried to backup again and that attempt failed. WMI writer was stable before the attempt, and showed "failed" afterwards. So it looks like something having to do with the backup is killing the WMI writer.
Here is the failure info:
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {861f4029-0a32-4b57-9801-2bc789019477}
State: [7] FailedSaturday, July 4, 2009 12:40 PM -
I can't think of any reason why it would work once then not the next time (unless you have some flakey hardware). Did you try rebooting the client, then backing it up? Just to confirm, you already ran chkdsk /r on each drive in your computer?Update.............................
Last night, we had a successful automatic backup. WMI writer showed "stable" when the backup was done.
This morning, it tried to backup again and that attempt failed. WMI writer was stable before the attempt, and showed "failed" afterwards. So it looks like something having to do with the backup is killing the WMI writer.
Here is the failure info:
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {861f4029-0a32-4b57-9801-2bc789019477}
State: [7] FailedSaturday, July 4, 2009 2:22 PMModerator -
"Just to confirm, you already ran chkdsk /r on each drive in your computer?"
Yes I had, and did it again for good measure. Same result: failure.
I suppose flaky hardware is a possibility, but I'm not having any problems with any of my other software. And, there are other threads here and elsewhere that describe the same scenario where WHS backup generally doesn't work on one of several computers, but does once in a while. My gut tells me we might have a bug somewhere.
What do you make of the WMIdiag errors from the report I posted earlier, especially:
19557 20:59:50 (2) !! WARNING: WMI DCOM components registration is missing for the following EXE/DLLs: .................................... 6 WARNING(S)!
19558 20:59:50 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{7A0227F6-7108-11D1-AD90-00C04FD8FDFF}\InProcServer32)
19559 20:59:50 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{D71EE747-F455-4804-9DF6-2ED81025F2C1}\InProcServer32)
19560 20:59:50 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{ED51D12E-511F-4999-8DCD-C2BAC91BE86E}\InProcServer32)
19561 20:59:50 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{4C6055D8-84B9-4111-A7D3-6623894EEDB3}\InProcServer32)
19562 20:59:50 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{A1044801-8F7E-11D1-9E7C-00C04FC324A8}\InProcServer32)
19563 20:59:50 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{F7CE2E13-8C90-11D1-9E7B-00C04FC324A8}\InProcServer32)
19564 20:59:50 (0) ** => WMI System components are not properly registered as COM objects, which could make WMI to
19565 20:59:50 (0) ** fail depending on the operation requested.
19566 20:59:50 (0) ** => For a .DLL, you can correct the DCOM configuration by executing the 'REGSVR32.EXE <Filename.DLL>' command.
19567 20:59:50 (0) **
which I did try to fix as instructed, but this did not get rid of the error;
Or:
19574 20:59:50 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
19575 20:59:50 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
19576 20:59:50 (0) ** - REMOVED ACE:
19577 20:59:50 (0) ** ACEType: &h0
19578 20:59:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
19579 20:59:50 (0) ** ACEFlags: &h0
19580 20:59:50 (0) ** ACEMask: &h1
19581 20:59:50 (0) ** DCOM_RIGHT_EXECUTE
19582 20:59:50 (0) **
19583 20:59:50 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
19584 20:59:50 (0) ** Removing default security will cause some operations to fail!
19585 20:59:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
19586 20:59:50 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
19587 20:59:50 (0) **
19588 20:59:50 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
19589 20:59:50 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
19590 20:59:50 (0) ** - REMOVED ACE:
19591 20:59:50 (0) ** ACEType: &h0
19592 20:59:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
19593 20:59:50 (0) ** ACEFlags: &h0
19594 20:59:50 (0) ** ACEMask: &h1
19595 20:59:50 (0) ** DCOM_RIGHT_EXECUTE
19596 20:59:50 (0) **
19597 20:59:50 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
19598 20:59:50 (0) ** Removing default security will cause some operations to fail!
19599 20:59:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
19600 20:59:50 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
19601 20:59:50 (0) **
19602 20:59:50 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
19603 20:59:50 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
19604 20:59:50 (0) ** - REMOVED ACE:
19605 20:59:50 (0) ** ACEType: &h0
19606 20:59:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
19607 20:59:50 (0) ** ACEFlags: &h0
19608 20:59:50 (0) ** ACEMask: &h1
19609 20:59:50 (0) ** DCOM_RIGHT_EXECUTE
19610 20:59:50 (0) **
19611 20:59:50 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
19612 20:59:50 (0) ** Removing default security will cause some operations to fail!
19613 20:59:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
19614 20:59:50 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
19615 20:59:50 (0) **
19616 20:59:50 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ..................................................................... MODIFIED.
19617 20:59:50 (1) !! ERROR: Actual trustee 'NT AUTHORITY\NETWORK SERVICE' DOES NOT match corresponding expected trustee rights (Actual->Default)
19618 20:59:50 (0) ** - ACTUAL ACE:
19619 20:59:50 (0) ** ACEType: &h0
19620 20:59:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
19621 20:59:50 (0) ** ACEFlags: &h2
19622 20:59:50 (0) ** CONTAINER_INHERIT_ACE
19623 20:59:50 (0) ** ACEMask: &h1
19624 20:59:50 (0) ** WBEM_ENABLE
19625 20:59:50 (0) ** - EXPECTED ACE:
19626 20:59:50 (0) ** ACEType: &h0
19627 20:59:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
19628 20:59:50 (0) ** ACEFlags: &h12
19629 20:59:50 (0) ** CONTAINER_INHERIT_ACE
19630 20:59:50 (0) ** INHERITED_ACE
19631 20:59:50 (0) ** ACEMask: &h13
19632 20:59:50 (0) ** WBEM_ENABLE
19633 20:59:50 (0) ** WBEM_METHOD_EXECUTE
19634 20:59:50 (0) ** WBEM_WRITE_PROVIDER
19635 20:59:50 (0) **
19636 20:59:50 (0) ** => The actual ACE has the right(s) '&h12 WBEM_METHOD_EXECUTE WBEM_WRITE_PROVIDER' removed!
19637 20:59:50 (0) ** This will cause some operations to fail!
19638 20:59:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the removed right.
19639 20:59:50 (0) ** For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
19640 20:59:50 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
19641 20:59:50 (0) ** The security diagnostic is based on the WMI namespace expected defaults.
19642 20:59:50 (0) ** A specific WMI application can always require a security setup different
19643 20:59:50 (0) ** than the WMI security defaults.
19644 20:59:50 (0) **
19645 20:59:50 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ..................................................................... MODIFIED.
19646 20:59:50 (1) !! ERROR: Actual trustee 'NT AUTHORITY\LOCAL SERVICE' DOES NOT match corresponding expected trustee rights (Actual->Default)
19647 20:59:50 (0) ** - ACTUAL ACE:
19648 20:59:50 (0) ** ACEType: &h0
19649 20:59:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
19650 20:59:50 (0) ** ACEFlags: &h2
19651 20:59:50 (0) ** CONTAINER_INHERIT_ACE
19652 20:59:50 (0) ** ACEMask: &h1
19653 20:59:50 (0) ** WBEM_ENABLE
19654 20:59:50 (0) ** - EXPECTED ACE:
19655 20:59:50 (0) ** ACEType: &h0
19656 20:59:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
19657 20:59:50 (0) ** ACEFlags: &h12
19658 20:59:50 (0) ** CONTAINER_INHERIT_ACE
19659 20:59:50 (0) ** INHERITED_ACE
19660 20:59:50 (0) ** ACEMask: &h13
19661 20:59:50 (0) ** WBEM_ENABLE
19662 20:59:50 (0) ** WBEM_METHOD_EXECUTE
19663 20:59:50 (0) ** WBEM_WRITE_PROVIDER
19664 20:59:50 (0) **
19665 20:59:50 (0) ** => The actual ACE has the right(s) '&h12 WBEM_METHOD_EXECUTE WBEM_WRITE_PROVIDER' removed!
19666 20:59:50 (0) ** This will cause some operations to fail!
19667 20:59:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the removed right.
19668 20:59:50 (0) ** For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
19669 20:59:50 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
19670 20:59:50 (0) ** The security diagnostic is based on the WMI namespace expected defaults.
19671 20:59:50 (0) ** A specific WMI application can always require a security setup different
19672 20:59:50 (0) ** than the WMI security defaults.
19673 20:59:50 (0) **
19674 20:59:50 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ..................................................................... MODIFIED.
19675 20:59:50 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
19676 20:59:50 (0) ** - REMOVED ACE:
19677 20:59:50 (0) ** ACEType: &h0
19678 20:59:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
19679 20:59:50 (0) ** ACEFlags: &h12
19680 20:59:50 (0) ** CONTAINER_INHERIT_ACE
19681 20:59:50 (0) ** INHERITED_ACE
19682 20:59:50 (0) ** ACEMask: &h13
19683 20:59:50 (0) ** WBEM_ENABLE
19684 20:59:50 (0) ** WBEM_METHOD_EXECUTE
19685 20:59:50 (0) ** WBEM_WRITE_PROVIDER
19686 20:59:50 (0) **
19687 20:59:50 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
19688 20:59:50 (0) ** Removing default security will cause some operations to fail!
19689 20:59:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
19690 20:59:50 (0) ** For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
19691 20:59:50 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
19692 20:59:50 (0) ** The security diagnostic is based on the WMI namespace expected defaults.
19693 20:59:50 (0) ** A specific WMI application can always require a security setup different
19694 20:59:50 (0) ** than the WMI security defaults.
19695 20:59:50 (0) **
19696 20:59:50 (0) **
19697 20:59:50 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
19698 20:59:50 (0) ** DCOM security error(s) detected: .................................................................................... 3.
19699 20:59:50 (0) ** WMI security warning(s) detected: ................................................................................... 0.
19700 20:59:50 (0) ** WMI security error(s) detected: ..................................................................................... 3.
19701 20:59:50 (0) **
19702 20:59:50 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
19703 20:59:50 (1) !! ERROR: Overall WMI security status: ................................................................................. ERROR!
19704 20:59:50 (0) ** - Started at 'Root' -----------------------------
I did open wmimgmt.msc but it was not clear how to fix these errors, so I didn't try to.
Or:
19725 20:59:50 (1) !! ERROR: WMI ENUMERATION operation errors reported: ................................................................... 1 ERROR(S)!
19726 20:59:50 (0) ** - Root/Default, InstancesOf, 'SystemRestore', 0x80080005 - Server execution failed.
19727 20:59:50 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\SR.MOF'
Or:
19748 20:59:50 (2) !! WARNING: => Verify the WMIDiag LOG at line #19156 for more details.
19749 20:59:50 (0) **
19750 20:59:50 (0) ** 1 error(s) 0x80080005 - (WBEM_UNKNOWN) This error code is external to WMI.
Here's the section they refer to:
19156 20:59:48 (3) Querying event log to locate events created during the execution of WMIDiag since Friday, July 03, 2009 at 20:47.
19157 20:59:48 (3)
19158 20:59:48 (3) 001 DCOM event(s):
19159 20:59:48 (4)
19160 20:59:48 (3) #012307: DCOM (10010) - Error - 03 July 2009 20:57:18 (GMT+4)
19161 20:59:48 (3) The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with
19162 20:59:48 (3) DCOM within the required timeout.
19163 20:59:48 (3)
19762 20:59:50 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\DOCUMENTS AND SETTINGS\...\LOCAL SETTINGS\TEMP\WMIDIAG-V2.0_XP___.CLI.RTM.32_FRANKSDESKTOP_2009.07.03_20.47.53.LOG' for details.
I could post the entire log, but it is extremely long..... if you wish, I will.
Thanks-
FrankMonday, July 6, 2009 1:06 AM -
"Just to confirm, you already ran chkdsk /r on each drive in your computer?"
Yes I had, and did it again for good measure. Same result: failure.
I suppose flaky hardware is a possibility, but I'm not having any problems with any of my other software. And, there are other threads here and elsewhere that describe the same scenario where WHS backup generally doesn't work on one of several computers, but does once in a while. My gut tells me we might have a bug somewhere.
What do you make of the WMIdiag errors from the report I posted earlier, especially:
19557 20:59:50 (2) !! WARNING: WMI DCOM components registration is missing for the following EXE/DLLs: .................................... 6 WARNING(S)!
19558 20:59:50 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{7A0227F6-7108-11D1-AD90-00C04FD8FDFF}\InProcServer32)
19559 20:59:50 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{D71EE747-F455-4804-9DF6-2ED81025F2C1}\InProcServer32)
19560 20:59:50 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{ED51D12E-511F-4999-8DCD-C2BAC91BE86E}\InProcServer32)
19561 20:59:50 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{4C6055D8-84B9-4111-A7D3-6623894EEDB3}\InProcServer32)
19562 20:59:50 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{A1044801-8F7E-11D1-9E7C-00C04FC324A8}\InProcServer32)
19563 20:59:50 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{F7CE2E13-8C90-11D1-9E7B-00C04FC324A8}\InProcServer32)
19564 20:59:50 (0) ** => WMI System components are not properly registered as COM objects, which could make WMI to
19565 20:59:50 (0) ** fail depending on the operation requested.
19566 20:59:50 (0) ** => For a .DLL, you can correct the DCOM configuration by executing the 'REGSVR32.EXE <Filename.DLL>' command.
19567 20:59:50 (0) **
which I did try to fix as instructed, but this did not get rid of the error;
Or:
19574 20:59:50 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
19575 20:59:50 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
19576 20:59:50 (0) ** - REMOVED ACE:
19577 20:59:50 (0) ** ACEType: &h0
19578 20:59:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
19579 20:59:50 (0) ** ACEFlags: &h0
19580 20:59:50 (0) ** ACEMask: &h1
19581 20:59:50 (0) ** DCOM_RIGHT_EXECUTE
19582 20:59:50 (0) **
19583 20:59:50 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
19584 20:59:50 (0) ** Removing default security will cause some operations to fail!
19585 20:59:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
19586 20:59:50 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
19587 20:59:50 (0) **
19588 20:59:50 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
19589 20:59:50 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
19590 20:59:50 (0) ** - REMOVED ACE:
19591 20:59:50 (0) ** ACEType: &h0
19592 20:59:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
19593 20:59:50 (0) ** ACEFlags: &h0
19594 20:59:50 (0) ** ACEMask: &h1
19595 20:59:50 (0) ** DCOM_RIGHT_EXECUTE
19596 20:59:50 (0) **
19597 20:59:50 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
19598 20:59:50 (0) ** Removing default security will cause some operations to fail!
19599 20:59:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
19600 20:59:50 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
19601 20:59:50 (0) **
19602 20:59:50 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
19603 20:59:50 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
19604 20:59:50 (0) ** - REMOVED ACE:
19605 20:59:50 (0) ** ACEType: &h0
19606 20:59:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
19607 20:59:50 (0) ** ACEFlags: &h0
19608 20:59:50 (0) ** ACEMask: &h1
19609 20:59:50 (0) ** DCOM_RIGHT_EXECUTE
19610 20:59:50 (0) **
19611 20:59:50 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
19612 20:59:50 (0) ** Removing default security will cause some operations to fail!
19613 20:59:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
19614 20:59:50 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
19615 20:59:50 (0) **
19616 20:59:50 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ..................................................................... MODIFIED.
19617 20:59:50 (1) !! ERROR: Actual trustee 'NT AUTHORITY\NETWORK SERVICE' DOES NOT match corresponding expected trustee rights (Actual->Default)
19618 20:59:50 (0) ** - ACTUAL ACE:
19619 20:59:50 (0) ** ACEType: &h0
19620 20:59:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
19621 20:59:50 (0) ** ACEFlags: &h2
19622 20:59:50 (0) ** CONTAINER_INHERIT_ACE
19623 20:59:50 (0) ** ACEMask: &h1
19624 20:59:50 (0) ** WBEM_ENABLE
19625 20:59:50 (0) ** - EXPECTED ACE:
19626 20:59:50 (0) ** ACEType: &h0
19627 20:59:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
19628 20:59:50 (0) ** ACEFlags: &h12
19629 20:59:50 (0) ** CONTAINER_INHERIT_ACE
19630 20:59:50 (0) ** INHERITED_ACE
19631 20:59:50 (0) ** ACEMask: &h13
19632 20:59:50 (0) ** WBEM_ENABLE
19633 20:59:50 (0) ** WBEM_METHOD_EXECUTE
19634 20:59:50 (0) ** WBEM_WRITE_PROVIDER
19635 20:59:50 (0) **
19636 20:59:50 (0) ** => The actual ACE has the right(s) '&h12 WBEM_METHOD_EXECUTE WBEM_WRITE_PROVIDER' removed!
19637 20:59:50 (0) ** This will cause some operations to fail!
19638 20:59:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the removed right.
19639 20:59:50 (0) ** For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
19640 20:59:50 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
19641 20:59:50 (0) ** The security diagnostic is based on the WMI namespace expected defaults.
19642 20:59:50 (0) ** A specific WMI application can always require a security setup different
19643 20:59:50 (0) ** than the WMI security defaults.
19644 20:59:50 (0) **
19645 20:59:50 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ..................................................................... MODIFIED.
19646 20:59:50 (1) !! ERROR: Actual trustee 'NT AUTHORITY\LOCAL SERVICE' DOES NOT match corresponding expected trustee rights (Actual->Default)
19647 20:59:50 (0) ** - ACTUAL ACE:
19648 20:59:50 (0) ** ACEType: &h0
19649 20:59:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
19650 20:59:50 (0) ** ACEFlags: &h2
19651 20:59:50 (0) ** CONTAINER_INHERIT_ACE
19652 20:59:50 (0) ** ACEMask: &h1
19653 20:59:50 (0) ** WBEM_ENABLE
19654 20:59:50 (0) ** - EXPECTED ACE:
19655 20:59:50 (0) ** ACEType: &h0
19656 20:59:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
19657 20:59:50 (0) ** ACEFlags: &h12
19658 20:59:50 (0) ** CONTAINER_INHERIT_ACE
19659 20:59:50 (0) ** INHERITED_ACE
19660 20:59:50 (0) ** ACEMask: &h13
19661 20:59:50 (0) ** WBEM_ENABLE
19662 20:59:50 (0) ** WBEM_METHOD_EXECUTE
19663 20:59:50 (0) ** WBEM_WRITE_PROVIDER
19664 20:59:50 (0) **
19665 20:59:50 (0) ** => The actual ACE has the right(s) '&h12 WBEM_METHOD_EXECUTE WBEM_WRITE_PROVIDER' removed!
19666 20:59:50 (0) ** This will cause some operations to fail!
19667 20:59:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the removed right.
19668 20:59:50 (0) ** For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
19669 20:59:50 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
19670 20:59:50 (0) ** The security diagnostic is based on the WMI namespace expected defaults.
19671 20:59:50 (0) ** A specific WMI application can always require a security setup different
19672 20:59:50 (0) ** than the WMI security defaults.
19673 20:59:50 (0) **
19674 20:59:50 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ..................................................................... MODIFIED.
19675 20:59:50 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
19676 20:59:50 (0) ** - REMOVED ACE:
19677 20:59:50 (0) ** ACEType: &h0
19678 20:59:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
19679 20:59:50 (0) ** ACEFlags: &h12
19680 20:59:50 (0) ** CONTAINER_INHERIT_ACE
19681 20:59:50 (0) ** INHERITED_ACE
19682 20:59:50 (0) ** ACEMask: &h13
19683 20:59:50 (0) ** WBEM_ENABLE
19684 20:59:50 (0) ** WBEM_METHOD_EXECUTE
19685 20:59:50 (0) ** WBEM_WRITE_PROVIDER
19686 20:59:50 (0) **
19687 20:59:50 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
19688 20:59:50 (0) ** Removing default security will cause some operations to fail!
19689 20:59:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
19690 20:59:50 (0) ** For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
19691 20:59:50 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
19692 20:59:50 (0) ** The security diagnostic is based on the WMI namespace expected defaults.
19693 20:59:50 (0) ** A specific WMI application can always require a security setup different
19694 20:59:50 (0) ** than the WMI security defaults.
19695 20:59:50 (0) **
19696 20:59:50 (0) **
19697 20:59:50 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
19698 20:59:50 (0) ** DCOM security error(s) detected: .................................................................................... 3.
19699 20:59:50 (0) ** WMI security warning(s) detected: ................................................................................... 0.
19700 20:59:50 (0) ** WMI security error(s) detected: ..................................................................................... 3.
19701 20:59:50 (0) **
19702 20:59:50 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
19703 20:59:50 (1) !! ERROR: Overall WMI security status: ................................................................................. ERROR!
19704 20:59:50 (0) ** - Started at 'Root' -----------------------------
I did open wmimgmt.msc but it was not clear how to fix these errors, so I didn't try to.
Or:
19725 20:59:50 (1) !! ERROR: WMI ENUMERATION operation errors reported: ................................................................... 1 ERROR(S)!
19726 20:59:50 (0) ** - Root/Default, InstancesOf, 'SystemRestore', 0x80080005 - Server execution failed.
19727 20:59:50 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\SR.MOF'
Or:
19748 20:59:50 (2) !! WARNING: => Verify the WMIDiag LOG at line #19156 for more details.
19749 20:59:50 (0) **
19750 20:59:50 (0) ** 1 error(s) 0x80080005 - (WBEM_UNKNOWN) This error code is external to WMI.
Here's the section they refer to:
19156 20:59:48 (3) Querying event log to locate events created during the execution of WMIDiag since Friday, July 03, 2009 at 20:47.
19157 20:59:48 (3)
19158 20:59:48 (3) 001 DCOM event(s):
19159 20:59:48 (4)
19160 20:59:48 (3) #012307: DCOM (10010) - Error - 03 July 2009 20:57:18 (GMT+4)
19161 20:59:48 (3) The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with
19162 20:59:48 (3) DCOM within the required timeout.
19163 20:59:48 (3)
19762 20:59:50 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\DOCUMENTS AND SETTINGS\...\LOCAL SETTINGS\TEMP\WMIDIAG-V2.0_XP___.CLI.RTM.32_FRANKSDESKTOP_2009.07.03_20.47.53.LOG' for details.
I could post the entire log, but it is extremely long..... if you wish, I will.
Thanks-
Frank
I think the best thing at this point is to file a bug report on Connect.Monday, July 6, 2009 2:14 AMModerator -
OK, done. I'll post the results here when they come.Monday, July 6, 2009 4:09 AM
-
Thanks for the tip. I did, and here are the results. Note that I tried re-registering the DCOM elements as directed, but the error cane up again:
19504 20:59:50 (0) ** WMIDiag v2.0 started on Friday, July 03, 2009 at 20:47.
19525 20:59:50 (0) ** Windows XP - No service pack - 32-bit (2600) - User 'FRANKSDESKTOP\FRANK WILSEY' on computer 'FRANKSDESKTOP'.
19526 20:59:50 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19527 20:59:50 (0) ** Environment: ........................................................................................................ OK..
Is this correct? Is this Windows XP without SP2? If so, please install SP2 as Windows Home Server does not support XP without SP2.
Thanks!
Lara Jones [MSFT] | Program Manager
Community Support and Beta | Windows Home Server Team
Windows Home Server Team Blog
Connect Windows Home Server
Windows Home ServerMonday, July 6, 2009 5:08 PMModerator
