Solved .NET v2x Optimzation Event Log Error 1111

[Jody Thornton]

Hi Folks:

Recently I began seeing some errors upon startup in Event Viewer. It shows an Event ID of 1111 and here's what the error says:

.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Service reached limit of transient errors. and a second error shows .NET Runtime Optimization Service (clr_optimization_v2.0.50727_64) - Service reached limit of transient errors.

When I start both ngen services, they start and then stop almost immediately. Then the errors show again.

Now when you Google this stuff, mostly the solution offered is that you need to reinstall Windows Vista, because .NET v2x and 3x are integrated with the OS. However, I can't believe that there's not a way to repair .NET by grabbing files from install.wim off the installation DVD-ROM. I tried that, for what it's worth. I took ownership of the v2.0.50727 folder, zapped it, and copied a fresh one from my Vista installation DVD. No go.


I have attempted removing about four or five recent .NET v2x updates, and reinstalling them. I figured that might re-register something. But no go.

 

[Jody Thornton]

Hmmm - surprised I didn't hear anything. Nonetheless, I took ownership of the complete Microsoft.NET folder tree inside C:\Windows, and obliterated it. Then I grabbed my Vista DVD and mounted the install.wim file with 7-Zip. I copied everything from the \Windows\Microsoft.NET folder and populated the same folder under C:\Windows.

Now .NET apps seem to work, and I no longer get the Event Viewer messages. Mind you, the .NET Optimization services do NOT appear in Services. Hmmmmmmmm.

 

[Jody Thornton]

That's OK I fixed it myself.