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.

Details
Product: Windows Operating System
Event ID: 1090
Source: Userenv
Version: 5.2
Symbolic Name: EVENT_FAILED_WBEM_SERVICES
Message: 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.
   
Explanation

The Resultant Set of Policy (RSoP) information for this application of Group Policy could not be processed. Even though Group Policy might have been successfully applied, the RSoP diagnostic information is not available.

RSoP data is generated when Group Policy settings are applied. This data provides diagnostic information regarding the application of Group Policy. RSoP data is stored in the local Windows Management Instrumentation (WMI) repository of the computer on which Group Policy is processing. Usually, an error logging RSoP data indicates a WMI problem.

   
User Action

To investigate the source of the RSoP failure, do the following:

  1. Review Event Viewer for events logged by WMI and, if appropriate, the extension that cannot log the RSoP data. This might indicate the cause of the problem.
  2. Verify that the WMI service (winmgmt) is running.
  3. Click Start, click Run, type wbemtest.exe and then click OK. Verify that you can access the root sop namespace on the affected computer.
  4. At the command prompt, type gpupdate, and then check Event Viewer to see whether the Userenv 1090 event or another WMI-related event is logged again. If the problem still exists, stop and then re-start the Winmgmt service.

If none of the above actions identified the problem, see the ‘Troubleshooting Group Policy in Windows Server 2003’
white paper at the Microsoft Web site.

Related:

Leave a Reply