Announcement

Collapse
No announcement yet.

Event ID 1090 on W2k3 Domain Controller

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Event ID 1090 on W2k3 Domain Controller

    I am getting this error on my 2k3 Domain controller. I am unable to uninstall any programs. Nothing shows up in network connections. RPC server is unavailable. the list goes on and on.

    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.

    Any help would be appreciated

  • #2
    Re: Event ID 1090 on W2k3 Domain Controller

    please follow this link and verify that these resolutions are not applicable to your symptoms.

    http://www.eventid.net/display.asp?e...serenv&phase=1
    its easier to beg forgiveness than ask permission.
    Give karma where karma is due...

    Comment


    • #3
      Re: Event ID 1090 on W2k3 Domain Controller

      Yes i have already tried these. When i attempt this one

      A miss-configuration by an application developer caused Logical Disk manager, rsop.msc, and WSUS updates to fail on Windows 2003 Enterprise SP1 server. To resolve the problem, go to Start -> Programs -> Administrative Tools -> Component Services. Here, select Component Services under the Console Root -> Computers -> My Computer. Right click My Computer -> Properties. Select the Default Properties tab. Select Default Authentication Level: “Connect" and Default Impersonation Level: "Identify". This restored the functionality.

      The MMC closes down.

      Comment

      Working...
      X