.Net Runtime Optimization Service Error After upgrading to Window Server 2008 Service Pack 2
After upgrading Windows Server 2008 Enterprise to SP2, I've been seeing the following error in the application event log: .NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.GroupPolicy.Targeting.Interop, Version=2.0.0.0, Culture=Neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=x86 . Error code = 0x800700b6 So far I've upgraded 2 DC's and both have had the same error. I haven't been able to find any documentation about this specific error.
July 29th, 2009 7:58pm
Hello,pleas post the complete event log entry especially we need the event id number.Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
Free Windows Admin Tool Kit Click here and download it now
July 30th, 2009 4:06am
Hello jasims,
Thank you for posting here.
As the given information about the error message is not clear, to help you troubleshoot the issue, we may need to collect full event application log on those two problematic servers.
Steps:
1. Open Event Viewer.
2. Expand and Navigate to Application and Services Logs
3. Locate the Category node that contains the error message you see. (please give me the name of the category name)
4. right-click on the category node and select Save Events As
5. Save it as the event log file (.evtx) and then send to us via tfwst@microsoft.com
Please also tell us the Event ID of the specific error message so that we can perform further research on it.
I appreciate your time and effort.
Thank you for your co-operation.This posting is provided "AS IS" with no warranties, and confers no rights.
July 30th, 2009 2:00pm
Log Name: Application Source: .NET Runtime Optimization Service Date: 7/29/2009 12:13:51 PM Event ID: 1101 Task Category: None Level: Error Keywords: Classic User: N/A Computer: (deleted) Description: .NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.GroupPolicy.Targeting.Interop, Version=2.0.0.0, Culture=Neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=x86 . Error code = 0x800700b6 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name=".NET Runtime Optimization Service" /> <EventID Qualifiers="0">1101</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2009-07-29T16:13:51.000Z" /> <EventRecordID>7860</EventRecordID> <Channel>Application</Channel> <Computer>(deleted)</Computer> <Security /> </System> <EventData> <Data>.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.GroupPolicy.Targeting.Interop, Version=2.0.0.0, Culture=Neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=x86 . Error code = 0x800700b6 </Data> <Data>Microsoft.GroupPolicy.Targeting.Interop, Version=2.0.0.0, Culture=Neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=x86</Data> </EventData> </Event>
Free Windows Admin Tool Kit Click here and download it now
July 30th, 2009 4:47pm
HI,
IN Services console there is services called .NET Runtime Optimization Service.Please start that services and see issuse will happen again.
Regards
Chinthaka
July 30th, 2009 6:43pm
There are two services listed that seem like what you are talking about: Microsoft .NET Framework NGEN v2.0.50727_X64 and Microsoft .NET Framework NGEN v2.0.50727_X32. On all of my DC's, those that have been service packed and those that haven't these services are set to manual and are not running. If I try to start the service, it just starts and stops. I don't get the same error in the app event logs. One note that may or may not be helpful, after I service packed the two DC's I got the error twice in a row on one of the DC's and never saw it again, and then it happened twice in a row on the second DC, then happened twice in a row one more time a few minutes later. After that, I haven't seen the error again. I'm just curious why it would show up at all.
Free Windows Admin Tool Kit Click here and download it now
July 30th, 2009 7:22pm
HI,You must restart compatiablity one with your system.x86 or x64.This error may be happen after .Net upgrades.keep on your eyes on that error if its may happen.Regards
Chinthaka
July 30th, 2009 7:24pm
Chinthaka, I'm not sure if I'm following you correctly, but I tried starting both x86 and x64 and both of the services started then stopped without leaving an error. I am running the 64bit version of windows on these servers. Just an FYI, the same happened on my non-sp2 DC's as well, the service will start then stop right away without leaving an error.
Free Windows Admin Tool Kit Click here and download it now
July 30th, 2009 7:32pm
HI, that is normal behavior of this service. Have you see that error again?RegardsChinthaka
July 30th, 2009 7:43pm
Nope, only after the sp2 install after the first boot. Like I said above on one of the servers it only showed up one (two times in a row) and the other it happened twice (two in a row for each) just minutes apart. I haven't seen it again on either server. I upgraded the first on Tuesday and the Second yesterday, so they've each had over a day without that error.
Free Windows Admin Tool Kit Click here and download it now
July 30th, 2009 7:47pm
Hi jasims,
Thanks for your update.
Based on the detailed information, this is normal behavior after we apply Service Pack 2 on Windows Server 2008 DC. We can just ignore this Event because there is no functionality loss, and this does not cause any issues other than the event error being logged.
Hope it helps.This posting is provided "AS IS" with no warranties, and confers no rights.
July 31st, 2009 9:39am