Hi Mike,
I understand that the system displays the following error in the
application log of the event viewer.
"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."
Source: Userenv
Category: None
Event ID: 1090
Mike, please try the following suggestions and check if these steps resolve
the issue.
Suggestion 1:
1. Click on Start -> Run ->type CMD ->click OK
2. In the command prompt, type cd \%windir%\system32 and press enter
3. Type regsvr32 /n /I userenv.dll and press enter
4. Type cd wbem and press enter
5. Type mofcomp scersop.mof and press enter
6. Type gpupdate /force and press enter
7. Restart the system.
If for any reason, if the issue comes back, allow the OS to rebuild the WMI
Repository
1. Stop Service via Services snap-in or net stop winmgmt
2. Re-register DLLs that exist in the C:\WINDOWS\system32\wbem\Repository
folder and \system32\wbem folder using the following command.
for /f %s in ("dir /b *.dll") do regsvr32 /s %s
3. Rename the existing C:\WINDOWS\system32\wbem\Repository to
C:\WINDOWS\system32\wbem\NEWRepository.
4. Reboot and allow WBEM to rebuild the repository again in
c:\windows\system32\wbem\repository.
5. Run a gpupdate and see if the Event 1090 is resolved. If not proceed to
step 6.
6. Stop Service via Services snap-in or net stop winmgmt
7. Register the files in the rebuilt c:\windows\system32\wbem\repository
folder.
Suggestion 2 - Namespace reset Method
1. Stop Service (net stop winmgmt)
2. Re-register DLLs that exist in the C:\WINDOWS\system32\wbem\,
System32\wbem folder.
3. Perform a gpupdate and see if we have fixed the Userenv 1090
4. Per Q281888 check the following registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Wbem\Scripting
The default namespace value should have the value data of root\cimv2.
5. Run the following switches:
winmgmt /regserver winmgmt /resyncperf winmgmt -e
6. Reboot and perform a gpupdate, see if 1090 event is cleared.
Hope the issue is resolved.
Thank you,
Rashmi
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Content-Class: urn:content-classes:message
| From: "Mike" <***@doyleengineering.com>
| Sender: "Mike" <***@doyleengineering.com>
| Subject: RSoP Error
| Date: Tue, 18 May 2004 09:45:12 -0700
| Lines: 25
| Message-ID: <e9b301c43cf7$7d0e14c0$***@phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Thread-Index: AcQ8930OL+WauZofTxqfpIF1mHpZwQ==
| Newsgroups: microsoft.public.windows.group_policy
| Path: cpmsftngxa10.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.windows.group_policy:6888
| NNTP-Posting-Host: tk2msftngxa12.phx.gbl 10.40.1.164
| X-Tomcat-NG: microsoft.public.windows.group_policy
|
| Hi, everyone. I need some help please.
|
| I am receivingf the following error in the application
| event log and have tried the fixes in the knowledge base
| but to no avail.
|
| "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."
|
| Source: Userenv
| Category: None
| Event ID: 1090
|
| I cannot run RSoP mmc snap-in.
|
| When I run the Wbemtest.exe program I cannot connect to
| the root\default.... I get an invalid namespace error.
|
| Can anyone help?
|
| Thanks for your time.
|
| Mike
|