Error 1090 Rsop
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Event ID 1090 :
Windows Failed To Record Resultant Set Of Policy (rsop) Information
Windows failed to record Resultant Set of Policy (RSoP) information Windows Server wmidiag utility > Group Policy Question 0 Sign in to vote Hi there. Getting this error on the servers in our event id 1090 failover clustering Terminal Services farm. We have six servers, all 2008 R2 64-bit, all exactly the same. Windows failed to record Resultant Set of Policy (RSoP) information, which describes the scope
Windows Could Not Record The Resultant Set Of Policy (rsop) Information For The Group Policy
of Group Policy objects applied to the computer or user. This could be caused by Windows Management Instrumentation (WMI) service being disabled, stopped, or other WMI errors. Group Policy settings successfully applied to the computer or user; however, management tools may not report accurately. and when I try and run an RSOP I am not able to pick a user (either
Event Id 1091
Current User or another user). I did some searching, looks to be an answer in expertsexchange but I don't want to pay the subscription fee. Also, the WMIDiag VB doesn't run on Server 2008 R2 64-bit.We have quite a bit of Group Policy: Loopback in merge mode, specific policy against groups of users, both Policies and Preferences. Can anybody help me out ? Friday, October 01, 2010 5:20 PM Reply | Quote Answers 2 Sign in to vote Hi, I would like to suggest you run the following commands to re-register WMI components to check the result: Regsvr32 %SystemRoot%\System32\wbem\wmidcprv.dll cd /d %windir%\system32\wbem for %i in (*.dll) do RegSvr32 -s %i for %i in (*.exe) do %i /RegServer The Windows Management Instrumentation Tester window may appear, this is normal and we can go ahead to close it. If it does not work, I also suggest you run the following commands to repair WMI namespace: net stop winmgmt wmic /NAMESPACE:\\root path "__namespace.name='wmi'" delete mofcomp %windir%\system32\wbem\wmi.mof net start winmgmt After that, please restart the computer to chec
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help the module userenv dll was loaded Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services
Service Dependencies Wmi Not Found
Groups Website Testing Store Headlines Experts Exchange > Questions > Event ID: 1090 - couldn't log the RSoP session status causes event id 1065 loss of mapped drive and VM failure Want to Advertise Here? Solved Event ID: 1090 - couldn't log the RSoP session status causes loss of mapped drive and VM failure Posted on 2009-04-14 Windows XP VMware https://social.technet.microsoft.com/Forums/windowsserver/en-US/977735d6-73d0-4947-af9a-dd3cd13527ae/event-id-1090-windows-failed-to-record-resultant-set-of-policy-rsop-information?forum=winserverGP 1 Verified Solution 18 Comments 10,313 Views Last Modified: 2012-08-14 I have noticed that my 2 guest VM's (XP Pro) running on my XP Pro Host randomly turned off. Users would report that it was suddenly unavailable. They would restart just fine and then disappear a few days later with no apparent pattern. Upon checking the Event Log I see that the failure has the following pattern: first, event ID: 1090 occurs - https://www.experts-exchange.com/questions/24323013/Event-ID-1090-couldn't-log-the-RSoP-session-status-causes-loss-of-mapped-drive-and-VM-failure.html Windows couldn't log the RSoP session status. Source - userenv User: NT AUTHORITY\SYSTEM. This is followed after a few seconds by - Event ID: 100 (User: N/A) (Source: vmauthd) - Cannot connect to VMX R:\VMDataStore1\RDP-Court\RDP-Court.vmx That is the path to the data store and the corresponding vmx file. The data store is mapped to the R:\ drive letter. This error is followed by matching errors for all the other VMs and after that I get several more RSoP failures. So how do I get the PSoP failures to stop? What more info is needed to troubleshoot this? I assume the RSoP failure is causing the mapped drive problem. 0 Question by:wintensivetech Facebook Twitter LinkedIn Google LVL 35 Best Solution bytorimar Sorry, there are some irritating line breaks in the instructions, here they come again, better readable: 1) Disable and stop the Windows Management Instrumentation service 2) Delete contents of "C:\windows\system32\wbem\Repository" Go to Solution 17 Comments LVL 35 Overall: Level 35 Windows XP 14 VMware 3 Message Expert Comment by:torimar2009-04-15 Are those machines XP SP2? Then try this hotfix: http://support.microsoft.com/kb/894794 Another way that is reported to fix the issue is this procedure from a command prompt: cd /d %windir%\system32 regsvr32 /n /I userenv.dll cd wbem mofcomp scersop.mof gpupdate /force Then reboot the machine twice. Alternatively,