[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

Event ID:      1090 on Server 2003 DC

Posted on 2007-10-09
19
Medium Priority
?
1,307 Views
Last Modified: 2008-07-09
I am getting this error on my 2k3 Domain controller. I am unable to uninstall any progams. Nothing shows up in network connections.

Event Type:      Error
Event Source:      Userenv
Event Category:      None
Event ID:      1090
Date:            10/9/2007
Time:            6:02:31 AM
User:            NT AUTHORITY\SYSTEM
Computer:      SSPP-S-DC1
Description:
Windows couldn't log the RSoP (Resultant Set of Policies) session status. An attempt to connect to WMI failed. No more RSoP logging will be done for this application of policy.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


 I hav ran wmidiag and it shows me the following.

.1478 07:46:58 (0) ** There are no missing WMI system files: .............................................................................. OK.
.1479 07:46:58 (1) !! ERROR: The following WMI repository file(s) is/are missing: ......................................................... 5 ERROR(S)!
.1480 07:46:58 (0) ** - INDEX.BTR
.1481 07:46:58 (0) ** - MAPPING.VER
.1482 07:46:58 (0) ** - MAPPING1.MAP
.1483 07:46:58 (0) ** - MAPPING2.MAP
.1484 07:46:58 (0) ** - OBJECTS.DATA

.1530 07:46:58 (2) !! WARNING: => The DCOM Default Impersonation is NOT set to 'Identify'.
.1531 07:46:58 (0) **    This could prevent WMI to work correctly.
.1532 07:46:58 (0) **    You can fix the DCOM configuration by:

.1559 07:46:58 (1) !! ERROR: WMI ADAP status: ............................................................................................. NOT AVAILABLE.


.1568 07:46:58 (0) ** - Root, 0x1CE - The remote server machine does not exist or is unavailable.
.1569 07:46:58 (0) **
.1570 07:46:58 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 5 ERROR(S)!
.1571 07:46:58 (0) ** - Root, 0x800706BA - The RPC server is unavailable..
.1572 07:46:58 (0) ** - Root, 0x800706BA - The RPC server is unavailable..
.1573 07:46:58 (0) ** - Root/Default, 0x800706BA - The RPC server is unavailable..
.1574 07:46:58 (0) ** - Root/CIMv2, 0x800706BA - The RPC server is unavailable..
.1575 07:46:58 (0) ** - Root/WMI, 0x800706BA - The RPC server is unavailable..

.1591 07:46:58 (0) ** 1 error(s) 0x1CE - (WBEM_UNKNOWN) This error code is external to WMI.
.1592 07:46:58 (0) **
.1593 07:46:58 (0) ** 5 error(s) 0x800706BA - (WBEM_UNKNOWN) This error code is external to WMI.
.1594 07:46:58 (0) ** => This error is not a WMI error. It is typically an RPC error due to the following reasons:
.1595 07:46:58 (0) **    - The application queried by the WMI provider is not installed, not available or not running
.1596 07:46:58 (0) **      at the time of the request was made. This error can also be generated because
.1597 07:46:58 (0) **      the application supporting the providers has been uninstalled.
.1598 07:46:58 (0) **    - The WMI operation was extremely intensive making the RPC communication to fail.


0
Comment
Question by:derekjr
  • 12
  • 5
  • 2
19 Comments
 
LVL 26

Expert Comment

by:Farhan Kazi
ID: 20040210
Greetings Derekjr,

Have you gone through following post ?
http://www.experts-exchange.com/OS/Miscellaneous/Q_21962563.html

Try following steps to fix this problem:

Click Start -> Run -> Cmd.exe
* Now type the following commands in order.

%homedrive%
cd %windir%\system32\wbem\repository
net stop winmgmt
del * /s /q
regsvr32 wbemupgd.dll

* Restart the computer.

Hope this helps!
Farhan
0
 

Author Comment

by:derekjr
ID: 20040344
I think i tried this already. I will try it again. Another thing though every time i reboot the server i get active directory is rebuilding indices.
0
 

Author Comment

by:derekjr
ID: 20040488
That  didn't work.
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
LVL 26

Expert Comment

by:Farhan Kazi
ID: 20046264
Did you run WMIDiag again to check the errors? can you please post the output here.
0
 

Author Comment

by:derekjr
ID: 20047664
.1425 08:01:47 (0) ** WMIDiag v2.0 started on Wednesday, October 10, 2007 at 08:01.
.1426 08:01:47 (0) **
.1427 08:01:47 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - January 2007.
.1428 08:01:47 (0) **
.1429 08:01:47 (0) ** This script is not supported under any Microsoft standard support program or service.
.1430 08:01:47 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
.1431 08:01:47 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
.1432 08:01:47 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
.1433 08:01:47 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
.1434 08:01:47 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
.1435 08:01:47 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
.1436 08:01:47 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
.1437 08:01:47 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
.1438 08:01:47 (0) ** of the possibility of such damages.
.1439 08:01:47 (0) **
.1440 08:01:47 (0) **
.1441 08:01:47 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1442 08:01:47 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
.1443 08:01:47 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1444 08:01:47 (0) **
.1445 08:01:47 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1446 08:01:47 (0) ** Windows Server 2003 - No service pack - 32-bit (3790) - User 'SSPP\ADMINISTRATOR' on computer 'SSPP-S-DC1'.
.1447 08:01:47 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1448 08:01:47 (0) ** Environment: ........................................................................................................ OK..
.1449 08:01:47 (0) ** There are no missing WMI system files: .............................................................................. OK.
.1450 08:01:47 (0) ** There are no missing WMI repository files: .......................................................................... OK.
.1451 08:01:47 (0) ** WMI repository state: ............................................................................................... N/A.
.1452 08:01:47 (0) ** BEFORE running WMIDiag:
.1453 08:01:47 (0) ** The WMI repository has a size of: ................................................................................... 0 MB.
.1454 08:01:47 (0) ** - Disk free space on 'C:': .......................................................................................... 14254 MB.
.1455 08:01:47 (0) **   - INDEX.BTR,                     57344 bytes,        10/9/2007 9:00:05 AM
.1456 08:01:47 (0) **   - MAPPING.VER,                   4 bytes,            10/9/2007 11:57:30 AM
.1457 08:01:47 (0) **   - MAPPING1.MAP,                  116 bytes,          10/9/2007 11:56:30 AM
.1458 08:01:47 (0) **   - MAPPING2.MAP,                  116 bytes,          10/9/2007 11:57:30 AM
.1459 08:01:47 (0) **   - OBJECTS.DATA,                  81920 bytes,        10/9/2007 9:00:05 AM
.1460 08:01:47 (0) ** AFTER running WMIDiag:
.1461 08:01:47 (0) ** The WMI repository has a size of: ................................................................................... 0 MB.
.1462 08:01:47 (0) ** - Disk free space on 'C:': .......................................................................................... 14254 MB.
.1463 08:01:47 (0) **   - INDEX.BTR,                     57344 bytes,        10/9/2007 9:00:05 AM
.1464 08:01:47 (0) **   - MAPPING.VER,                   4 bytes,            10/9/2007 11:57:30 AM
.1465 08:01:47 (0) **   - MAPPING1.MAP,                  116 bytes,          10/9/2007 11:56:30 AM
.1466 08:01:47 (0) **   - MAPPING2.MAP,                  116 bytes,          10/9/2007 11:57:30 AM
.1467 08:01:47 (0) **   - OBJECTS.DATA,                  81920 bytes,        10/9/2007 9:00:05 AM
.1468 08:01:47 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1469 08:01:47 (0) ** Windows Firewall: ................................................................................................... NOT INSTALLED.
.1470 08:01:47 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1471 08:01:47 (2) !! WARNING: DCOM Status: ............................................................................................... WARNING!
.1472 08:01:47 (2) !! WARNING: => The DCOM Default Impersonation is NOT set to 'Identify'.
.1473 08:01:47 (0) **    This could prevent WMI to work correctly.
.1474 08:01:47 (0) **    You can fix the DCOM configuration by:
.1475 08:01:47 (0) **    - Executing the 'DCOMCNFG.EXE' command.
.1476 08:01:47 (0) **    - Expanding 'Component Services' and 'Computers' nodes.
.1477 08:01:47 (0) **    - Editing properties of 'My Computer' node.
.1478 08:01:47 (0) **    - Editing the 'Default properties' tab.
.1479 08:01:47 (0) **    - Set the 'Default Impersonation level' listbox to 'Identify'.
.1480 08:01:47 (0) **    From the command line, the DCOM configuration can be corrected with the following command:
.1481 08:01:47 (0) **    i.e. 'REG.EXE Add HKLM\SOFTWARE\Microsoft\Ole /v LegacyImpersonationLevel /t REG_DWORD /d 2 /f'
.1482 08:01:47 (0) **
.1483 08:01:47 (0) ** WMI registry setup: ................................................................................................. OK.
.1484 08:01:47 (0) ** WMI Service has no dependents: ...................................................................................... OK.
.1485 08:01:47 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
.1486 08:01:47 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
.1487 08:01:47 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1488 08:01:47 (0) ** WMI service DCOM setup: ............................................................................................. OK.
.1489 08:01:47 (0) ** WMI components DCOM registrations: .................................................................................. OK.
.1490 08:01:47 (0) ** WMI ProgID registrations: ........................................................................................... OK.
.1491 08:01:47 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
.1492 08:01:47 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
.1493 08:01:47 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
.1494 08:01:47 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
.1495 08:01:47 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1496 08:01:47 (0) ** Overall DCOM security status: ....................................................................................... OK.
.1497 08:01:47 (0) ** Overall WMI security status: ........................................................................................ OK.
.1498 08:01:47 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
.1499 08:01:47 (0) ** WMI permanent SUBSCRIPTION(S): ...................................................................................... NONE.
.1500 08:01:47 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
.1501 08:01:47 (1) !! ERROR: WMI ADAP status: ............................................................................................. NOT AVAILABLE.
.1502 08:01:47 (0) **    You can start the WMI AutoDiscovery/AutoPurge (ADAP) process to resynchronize
.1503 08:01:47 (0) **    the performance counters with the WMI performance classes with the following commands:
.1504 08:01:47 (0) **    i.e. 'WINMGMT.EXE /CLEARADAP'
.1505 08:01:47 (0) **    i.e. 'WINMGMT.EXE /RESYNCPERF'
.1506 08:01:47 (0) **    The ADAP process logs informative events in the Windows NT event log.
.1507 08:01:47 (0) **    More information can be found on MSDN at:
.1508 08:01:47 (0) **    http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmisdk/wmi/wmi_adap_event_log_events.asp
.1509 08:01:47 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: .......................................... 1 ERROR(S)!
.1510 08:01:47 (0) ** - Root, 0x1CE - The remote server machine does not exist or is unavailable.
.1511 08:01:47 (0) **
.1512 08:01:47 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 5 ERROR(S)!
.1513 08:01:47 (0) ** - Root, 0x800706BA - The RPC server is unavailable..
.1514 08:01:47 (0) ** - Root, 0x800706BA - The RPC server is unavailable..
.1515 08:01:47 (0) ** - Root/Default, 0x800706BA - The RPC server is unavailable..
.1516 08:01:47 (0) ** - Root/CIMv2, 0x800706BA - The RPC server is unavailable..
.1517 08:01:47 (0) ** - Root/WMI, 0x800706BA - The RPC server is unavailable..
.1518 08:01:47 (0) **
.1519 08:01:47 (0) ** WMI GET operations: ................................................................................................. OK.
.1520 08:01:47 (0) ** WMI MOF representations: ............................................................................................ OK.
.1521 08:01:47 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
.1522 08:01:47 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
.1523 08:01:47 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
.1524 08:01:47 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
.1525 08:01:47 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
.1526 08:01:47 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
.1527 08:01:47 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
.1528 08:01:47 (0) ** WMI static instances retrieved: ..................................................................................... 0.
.1529 08:01:47 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
.1530 08:01:47 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
.1531 08:01:47 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1532 08:01:47 (0) **
.1533 08:01:47 (0) ** 1 error(s) 0x1CE - (WBEM_UNKNOWN) This error code is external to WMI.
.1534 08:01:47 (0) **
.1535 08:01:47 (0) ** 5 error(s) 0x800706BA - (WBEM_UNKNOWN) This error code is external to WMI.
.1536 08:01:47 (0) ** => This error is not a WMI error. It is typically an RPC error due to the following reasons:
.1537 08:01:47 (0) **    - The application queried by the WMI provider is not installed, not available or not running
.1538 08:01:47 (0) **      at the time of the request was made. This error can also be generated because
.1539 08:01:47 (0) **      the application supporting the providers has been uninstalled.
.1540 08:01:47 (0) **    - The WMI operation was extremely intensive making the RPC communication to fail.
.1541 08:01:47 (0) ** => To correct this situation, you can:
.1542 08:01:47 (0) **    - Install or start the application supporting these providers.
.1543 08:01:47 (0) **
.1544 08:01:47 (0) ** => Errors starting with 0x8007 are Win32 errors, NOT WMI errors. More information can be found
.1545 08:01:47 (0) **    with the 'NET.EXE HELPMSG <dddd>' command, where <dddd> is the last four hex digits (0x06BA)
.1546 08:01:47 (0) **    converted in decimal (1722).
.1547 08:01:47 (0) **    - NET HELPMSG 1722
.1548 08:01:47 (0) **
.1549 08:01:47 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1550 08:01:47 (0) ** WMI Registry key setup: ............................................................................................. OK.
.1551 08:01:47 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1552 08:01:47 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1553 08:01:47 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1554 08:01:47 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1555 08:01:47 (0) **
.1556 08:01:47 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1557 08:01:47 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
.1558 08:01:47 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1559 08:01:47 (0) **
.1560 08:01:47 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!.  Check 'C:\DOCUMENTS AND SETTINGS\ADMINISTRATOR.SSPP\LOCAL SETTINGS\TEMP\WMIDIAG-V2.0_2003_.SRV.RTM.32_SSPP-S-DC1_2007.10.10_08.01.29.LOG' for details.
.1561 08:01:47 (0) **
.1562 08:01:47 (0) ** WMIDiag v2.0 ended on Wednesday, October 10, 2007 at 08:01 (W:36 E:13 S:1).
0
 
LVL 41

Expert Comment

by:graye
ID: 20048463
I'd recommend that you forget about WMI and concentrate your efforts on why the Remote Procedure Calls (RPC) service is not working

http://www.microsoft.com/technet/technetmag/issues/2007/07/HowITWorks/
0
 

Author Comment

by:derekjr
ID: 20048698
In dcdiag the only error i get is NTFRS Service is stopped.
When i perform repadmin ./bind i don't get any errors.

 DNS is working fine i am able to ping other DC's

0
 
LVL 26

Expert Comment

by:Farhan Kazi
ID: 20056390

I have a doubt that the WMI service on your system may not be started/starting.
Can you run this command as an administrator and post here the output?

Click Start -> Run -> Cmd.exe -> OK

sc query winmgmt

Also send us the output of this command "net start winmgmt"
0
 

Author Comment

by:derekjr
ID: 20056473

SERVICE_NAME: winmgmt
        TYPE               : 20  WIN32_SHARE_PROCESS  
        STATE              : 4  RUNNING
                                (STOPPABLE, PAUSABLE, ACCEPTS_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0


The requested service has already been started.

More help is available by typing NET HELPMSG 2182.
0
 
LVL 26

Expert Comment

by:Farhan Kazi
ID: 20057229
Hi,
WMI Service seems to be running fine.
But all WMI operations are failing.

Please try these steps to register WMI binaries:

1. Open an administrative console window (cmd) and change to the WBEM folder (cd "%windir%\system32\wbem").

2. Enter the following command: net stop winmgmt

3. Enter the following command: for /f %s in ('dir /b /s *.dll') do regsvr32 /s %s

4. Enter the following command: winmgmt /regserver

5. Enter the following command: wmiprvse /regserver

6. Enter the following command: net start winmgmt

Run WMIDiag again after this, to see if the errors are resolved.

If still the errors prevail, then it suggests that some WMI binaries have been modified/changed.
In that case, you can try to replace all binaries in "%windir%\system32\wbem" folder with ones from a working system, where same OS is running.
0
 

Author Comment

by:derekjr
ID: 20057297
.1425 10:20:14 (0) ** WMIDiag v2.0 started on Thursday, October 11, 2007 at 10:20.
.1426 10:20:14 (0) **
.1427 10:20:14 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - January 2007.
.1428 10:20:14 (0) **
.1429 10:20:14 (0) ** This script is not supported under any Microsoft standard support program or service.
.1430 10:20:14 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
.1431 10:20:14 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
.1432 10:20:14 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
.1433 10:20:14 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
.1434 10:20:14 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
.1435 10:20:14 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
.1436 10:20:14 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
.1437 10:20:14 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
.1438 10:20:14 (0) ** of the possibility of such damages.
.1439 10:20:14 (0) **
.1440 10:20:14 (0) **
.1441 10:20:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1442 10:20:14 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
.1443 10:20:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1444 10:20:14 (0) **
.1445 10:20:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1446 10:20:14 (0) ** Windows Server 2003 - No service pack - 32-bit (3790) - User 'SSPP\ADMINISTRATOR' on computer 'SSPP-S-DC1'.
.1447 10:20:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1448 10:20:14 (0) ** Environment: ........................................................................................................ OK..
.1449 10:20:14 (0) ** There are no missing WMI system files: .............................................................................. OK.
.1450 10:20:14 (0) ** There are no missing WMI repository files: .......................................................................... OK.
.1451 10:20:14 (0) ** WMI repository state: ............................................................................................... N/A.
.1452 10:20:14 (0) ** BEFORE running WMIDiag:
.1453 10:20:14 (0) ** The WMI repository has a size of: ................................................................................... 0 MB.
.1454 10:20:14 (0) ** - Disk free space on 'C:': .......................................................................................... 14253 MB.
.1455 10:20:14 (0) **   - INDEX.BTR,                     57344 bytes,        10/9/2007 9:00:05 AM
.1456 10:20:14 (0) **   - MAPPING.VER,                   4 bytes,            10/11/2007 10:18:35 AM
.1457 10:20:14 (0) **   - MAPPING1.MAP,                  116 bytes,          10/11/2007 10:18:35 AM
.1458 10:20:14 (0) **   - MAPPING2.MAP,                  116 bytes,          10/11/2007 10:18:35 AM
.1459 10:20:14 (0) **   - OBJECTS.DATA,                  81920 bytes,        10/9/2007 9:00:05 AM
.1460 10:20:14 (0) ** AFTER running WMIDiag:
.1461 10:20:14 (0) ** The WMI repository has a size of: ................................................................................... 0 MB.
.1462 10:20:14 (0) ** - Disk free space on 'C:': .......................................................................................... 14253 MB.
.1463 10:20:14 (0) **   - INDEX.BTR,                     57344 bytes,        10/11/2007 10:20:13 AM
.1464 10:20:14 (0) **   - MAPPING.VER,                   4 bytes,            10/11/2007 10:20:13 AM
.1465 10:20:14 (0) **   - MAPPING1.MAP,                  120 bytes,          10/11/2007 10:20:05 AM
.1466 10:20:14 (0) **   - MAPPING2.MAP,                  120 bytes,          10/11/2007 10:20:13 AM
.1467 10:20:14 (0) **   - OBJECTS.DATA,                  90112 bytes,        10/11/2007 10:20:13 AM
.1468 10:20:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1469 10:20:14 (0) ** Windows Firewall: ................................................................................................... NOT INSTALLED.
.1470 10:20:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1471 10:20:14 (2) !! WARNING: DCOM Status: ............................................................................................... WARNING!
.1472 10:20:14 (2) !! WARNING: => The DCOM Default Impersonation is NOT set to 'Identify'.
.1473 10:20:14 (0) **    This could prevent WMI to work correctly.
.1474 10:20:14 (0) **    You can fix the DCOM configuration by:
.1475 10:20:14 (0) **    - Executing the 'DCOMCNFG.EXE' command.
.1476 10:20:14 (0) **    - Expanding 'Component Services' and 'Computers' nodes.
.1477 10:20:14 (0) **    - Editing properties of 'My Computer' node.
.1478 10:20:14 (0) **    - Editing the 'Default properties' tab.
.1479 10:20:14 (0) **    - Set the 'Default Impersonation level' listbox to 'Identify'.
.1480 10:20:14 (0) **    From the command line, the DCOM configuration can be corrected with the following command:
.1481 10:20:14 (0) **    i.e. 'REG.EXE Add HKLM\SOFTWARE\Microsoft\Ole /v LegacyImpersonationLevel /t REG_DWORD /d 2 /f'
.1482 10:20:14 (0) **
.1483 10:20:14 (0) ** WMI registry setup: ................................................................................................. OK.
.1484 10:20:14 (0) ** WMI Service has no dependents: ...................................................................................... OK.
.1485 10:20:14 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
.1486 10:20:14 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
.1487 10:20:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1488 10:20:14 (0) ** WMI service DCOM setup: ............................................................................................. OK.
.1489 10:20:14 (0) ** WMI components DCOM registrations: .................................................................................. OK.
.1490 10:20:14 (0) ** WMI ProgID registrations: ........................................................................................... OK.
.1491 10:20:14 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
.1492 10:20:14 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
.1493 10:20:14 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
.1494 10:20:14 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
.1495 10:20:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1496 10:20:14 (0) ** Overall DCOM security status: ....................................................................................... OK.
.1497 10:20:14 (0) ** Overall WMI security status: ........................................................................................ OK.
.1498 10:20:14 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
.1499 10:20:14 (0) ** WMI permanent SUBSCRIPTION(S): ...................................................................................... NONE.
.1500 10:20:14 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
.1501 10:20:14 (1) !! ERROR: WMI ADAP status: ............................................................................................. NOT AVAILABLE.
.1502 10:20:14 (0) **    You can start the WMI AutoDiscovery/AutoPurge (ADAP) process to resynchronize
.1503 10:20:14 (0) **    the performance counters with the WMI performance classes with the following commands:
.1504 10:20:14 (0) **    i.e. 'WINMGMT.EXE /CLEARADAP'
.1505 10:20:14 (0) **    i.e. 'WINMGMT.EXE /RESYNCPERF'
.1506 10:20:14 (0) **    The ADAP process logs informative events in the Windows NT event log.
.1507 10:20:14 (0) **    More information can be found on MSDN at:
.1508 10:20:14 (0) **    http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmisdk/wmi/wmi_adap_event_log_events.asp
.1509 10:20:14 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: .......................................... 1 ERROR(S)!
.1510 10:20:14 (0) ** - Root, 0x1CE - The remote server machine does not exist or is unavailable.
.1511 10:20:14 (0) **
.1512 10:20:14 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 5 ERROR(S)!
.1513 10:20:14 (0) ** - Root, 0x800706BA - The RPC server is unavailable..
.1514 10:20:14 (0) ** - Root, 0x800706BA - The RPC server is unavailable..
.1515 10:20:14 (0) ** - Root/Default, 0x800706BA - The RPC server is unavailable..
.1516 10:20:14 (0) ** - Root/CIMv2, 0x800706BA - The RPC server is unavailable..
.1517 10:20:14 (0) ** - Root/WMI, 0x800706BA - The RPC server is unavailable..
.1518 10:20:14 (0) **
.1519 10:20:14 (0) ** WMI GET operations: ................................................................................................. OK.
.1520 10:20:14 (0) ** WMI MOF representations: ............................................................................................ OK.
.1521 10:20:14 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
.1522 10:20:14 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
.1523 10:20:14 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
.1524 10:20:14 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
.1525 10:20:14 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
.1526 10:20:14 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
.1527 10:20:14 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
.1528 10:20:14 (0) ** WMI static instances retrieved: ..................................................................................... 0.
.1529 10:20:14 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
.1530 10:20:14 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
.1531 10:20:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1532 10:20:14 (0) **
.1533 10:20:14 (0) ** 1 error(s) 0x1CE - (WBEM_UNKNOWN) This error code is external to WMI.
.1534 10:20:14 (0) **
.1535 10:20:14 (0) ** 5 error(s) 0x800706BA - (WBEM_UNKNOWN) This error code is external to WMI.
.1536 10:20:14 (0) ** => This error is not a WMI error. It is typically an RPC error due to the following reasons:
.1537 10:20:14 (0) **    - The application queried by the WMI provider is not installed, not available or not running
.1538 10:20:14 (0) **      at the time of the request was made. This error can also be generated because
.1539 10:20:14 (0) **      the application supporting the providers has been uninstalled.
.1540 10:20:14 (0) **    - The WMI operation was extremely intensive making the RPC communication to fail.
.1541 10:20:14 (0) ** => To correct this situation, you can:
.1542 10:20:14 (0) **    - Install or start the application supporting these providers.
.1543 10:20:14 (0) **
.1544 10:20:14 (0) ** => Errors starting with 0x8007 are Win32 errors, NOT WMI errors. More information can be found
.1545 10:20:14 (0) **    with the 'NET.EXE HELPMSG <dddd>' command, where <dddd> is the last four hex digits (0x06BA)
.1546 10:20:14 (0) **    converted in decimal (1722).
.1547 10:20:14 (0) **    - NET HELPMSG 1722
.1548 10:20:14 (0) **
.1549 10:20:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1550 10:20:14 (0) ** WMI Registry key setup: ............................................................................................. OK.
.1551 10:20:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1552 10:20:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1553 10:20:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1554 10:20:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1555 10:20:14 (0) **
.1556 10:20:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1557 10:20:14 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
.1558 10:20:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1559 10:20:14 (0) **
.1560 10:20:14 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!.  Check 'C:\DOCUMENTS AND SETTINGS\ADMINISTRATOR.SSPP\LOCAL SETTINGS\TEMP\WMIDIAG-V2.0_2003_.SRV.RTM.32_SSPP-S-DC1_2007.10.11_10.20.01.LOG' for details.
.1561 10:20:14 (0) **
.1562 10:20:14 (0) ** WMIDiag v2.0 ended on Thursday, October 11, 2007 at 10:20 (W:36 E:13 S:1).
0
 

Author Comment

by:derekjr
ID: 20057446
The only other 2k3 server i have is a sharepoint server running 64 bit. Would i be able to copy the whole  wbem folder from that>
0
 
LVL 41

Expert Comment

by:graye
ID: 20057990
If you're interested in a different point of view....

I rather doubt the problem is with WMI.  Instead I believe the issue is with RPC (which effects WMI, as well as a bunch of other things including uninstalling applications).  

The most likely issue is a mis-configuration (either by accident, virus attack, or over zealous administrators trying to harden the system)

I'd suggest that you concentrate on diagnosing RPC issues.
0
 

Author Comment

by:derekjr
ID: 20058952
THE RPC service is running. I don't get any errors when i run dcdiag. I am not sure on what direction to go with this.
0
 

Author Comment

by:derekjr
ID: 20077338
Does anyone have any suggestions? I am to the point of dcpromo this box and rebuilding it.
0
 

Author Comment

by:derekjr
ID: 20103578
Well i went to run DCPROMO on this box and it gave me an error that it couldn't start FRS. I attempted to start the server and got  error 1068
0
 
LVL 26

Expert Comment

by:Farhan Kazi
ID: 20104466
Did you try replacing all binaries in the "%windir%\system32\wbem" folder with those from a working Windows2003 OS?

If you tried that also, and still getting the same error, then this could be a problem in your system's DCOM settings or something else.
Identifying causes in such cases needs access to the system. Without that, it's pretty tough to pinpoint the cause.
I suggest you open up a case with Microsoft Product Support Services(PSS) for the issue if it's critical. They should be able to help you.
0
 

Author Comment

by:derekjr
ID: 20106370
I don't have another server running 2003.
 Well i have a sharepoint box but it isn't a DC and it is standard 64 bit. I am running  2003 ENT 32bit on this DC
0
 

Accepted Solution

by:
derekjr earned 0 total points
ID: 21526372
this can be closed. i reinstalled server
0

Featured Post

Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Let's recap what we learned from yesterday's Skyport Systems webinar.
Wouldn't it be nice if objects in Active Directory automatically moved into the correct Organizational Units? This is what AutoAD aims to do and as a plus, it automatically creates Sites, Subnets, and Organizational Units.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

834 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question