The functions in this library will not be treated as trusted.įor more information, see Help and Support Center at. The configuration information of the performance library "C:\WINDOWS\system32\infoctrs.dll" for the "InetInfo" service does not match the trusted performance library information stored in the registry. I am getting following errors in Application event log: It displays "-" in min,max and avg value. net 2.0 what else should I try? Performance counters are there but it is not recording any data. I checked IIS_WPG permission and it is OK. Performance counters are working for 1.0 and 1.1 but for 2.0 it is not recording anydata. Assuming this is the problem, why should it make a difference? This process was running fine for months on the physical server - why should it be causing problems on the VM.?Īnyone have any ideas, suggestions or solutions.I am having a very strange problem. The functions in this library will not be treated as trusted. The configuration information of the performance library 'C:WindowsSystem32perfts.dll' for the 'TermService' service does not match the trusted performance library information stored in the registry. I'll find out tomorrow morning after the nightly builds have run in anger so hopefully I have some good news waiting for me. The functions in this library will not be treated as trusted. Finally I tried deploying the application using files built via a 'Release' build (as opposed to 'Debug') and this appears to have resolved the problem - but I don't know why. NET 2.0 & 3.0 (3.5 is not needed!) but the problem persisted. The functions in this library will not be treated as trusted.' and 'The configuration information of the performance library 'C:WINDOWSsystem32infoctrs. : I've been kicking this around for a little while now and still don't really know why it is happening. 'MSFtpsvc' service does not match the trusted performance library information stored in the registry. Now the quick fix is to run aspnet_regiis as part of the build script but frankly that just smells to bad. If I manually delete the old files and copy across the new ones then once again the Compiler Error is displayed in the browser. While these may be for a different version of SQL server the steps and commentary on these may be helpful. build) then access the site another identical event appears and the compilation error is displayed (running aspnet_regiis fix it though). If I then run either of the publish scripts (.bat or. The configuration information of the performance library C:WINNTsystem32infoctrs.dll for the InetInfo service does not match the trusted performance library information stored in the registry. The functions in this library will not be treated as trusted.īut the site does still load without any problems. The functions in this library will not be treated as trusted. The trusted performance library information stored in the registry. "C:\WINDOWS\system32\infoctrs.dll" for the "InetInfo" service does not match But the site does still load without any problems. If I run the above command, clear out the events logs and then access the site a new event appears: The configuration information of the performance library The configuration information of the performance library 'C:WINDOWSsystem32infoctrs.dll' for the 'InetInfo' service does not match the trusted performance library information stored in the registry. I've reviewed the publish stage of the build process and moved from the good old-fashioned batch script to a 'cleaner' nAnt script but the problem remains. Running aspnet_regiis -i will get the site back online but I'm baffled as to why IIS seems to have forgotten all about. Now, whenever the nightly build publishes to IIS we get an error in the browser stating The compiler failed with error code 128. Type lodctr IniFile, and then press ENTER. Note Servicename represents the name of the affected service. Type unlodctr ServiceName, and then press ENTER. We have a CruiseControl.NET server that performs nightly builds on or applications and then publishes the resulting output to the IIS instance on the same box - this acts as out test deployment for QA.Įverything has been running fine for months until we moved to a new server (Win2003 R2 SP1) - actually a VM. To reregister the performance counter libraries of the affected service, follow these steps: Click Start, click Run, type cmd, and then click OK. Not sure if this belongs here or in SO but here goes anyway.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |