mscorsvw.exe
When installing Visual Studio 2005 Beta 2 (and when install has finished) a process named "mscorsvw.exe" runs, and takes up 95/100% CPU. I've no idea why this is.
That, and when trying to start Visual Studio 2005 - It opens, then immediately exits. I've done the un-install of previous versions in perfect order, and yet the problem continues
Can anyone shed any light?
 Compound_G wrote: |
| When installing Visual Studio 2005 Beta 2 (and when install has finished) a process named "mscorsvw.exe" runs, and takes up 95/100% CPU. I've no idea why this is. That, and when trying to start Visual Studio 2005 - It opens, then immediately exits. I've done the un-install of previous versions in perfect order, and yet the problem continues Can anyone shed any light?
|
|
Are you installing VS 2005 Beta 2 on the same node as the server?
If so, this is probably the be SQL Analysis Services task reported by Buck Hodges. Follow the instructions in the link to reduce the frequency of warehouse processing from every two minutes to once an hour.
Negative.
a) There is no web service running and ergo "http://localhost:8080/Warehouse/warehousecontroller.asmx" is not available
b) This wouldn't solve my IDE from crashing constantly when opening; and
c) This is on a v. high spec machine running Windows XP SP2 and yet the problem continues.
This process is used to generate the native images of the assemblies, used extensively during installations. For example if you install the SQL 2005 April CTP, during each step of the installation (each service, i.e. analysis, notifiction,workstation,...) an instance is started to generate the appropriate installed dll
i now have the same problem under the same situation, has any one found an answer yet?
mscorsvw.exe can be the ngen service (see
http://msdn.microsoft.com/msdnmag/issues/05/04/NGen/default.aspx) or an ngen or ngen service worker. Typically, an install of the .NET Framework will leave the service doing compilation work in the background. Some assemblies get compiled immediately (although in low priority to try not to impact the user). Once these assemblies get compiled the service will wait for the machine to be idle to finish its work. Once this happens the service will shutdown and won't come back (until somebody queues up more work to the service, which will typically only happen after you install a managed app)
I'll write an entry in my blog tonight to clarify.
David
I am also running into the same problem. How do I disable this service?
Hi to all,
I have this problem too... the ngen.exe don't works...:
C:\>ngen.exe executequeueditems
Microsoft (R) CLR Native Image Generator - Version 1.1.4322.573
Copyright (C) Microsoft Corporation 1998-2002. All rights reserved.
Error compiling executequeueditems: The system couldn't find the specified file.
the mscorsvw.exe get all CPU(97 to 100%) in normal priority in the initializing of the os
I break the process and he back.
How to stop him?
Thanks
Very interesting article. Didn't help.
My cpu is an AMD FX-53. It is rather fast.
This mscorsvw thing has been running for two hours now. It won't stop.
Tried running the ngen.exe executequeueditems.
It tells me "no such interface supported".
Since my other machines didn't have this problem, I am going to reinstall Windows and try installing express again.
I obtain success deletin all entries in register related with mscorsvw.exe... no more problems.
Tks,
Ton
i JUST WANTED TO ADD ...THANKS FOR CLARIFYING WHY IT EATS UP ALL OUR CPU GBUT CLARIFYING IT DOESN'T STOP IT AND IT NEEDS TO STOP...ANY IDEA ON HOW TO MAKE IT STOP? IT DOESN'T GO AWAY AS YOU SAY AND AS SOMEONE ELSE POINTED OUT ITS NEEDED FOR INSTALLS SO CAN WE DISABLE IT UNTIL NEEDED?
If you want to follow this workaround, do it at your own risk. I cannot guarantee anything!
I traced the behavior of mscorsvw.exe to find that it was looping while it was enumerating the subkeys of the registry key: HKLM\Software\Microsoft\.NETFramework\v2.0.50215\NGENService\Roots
Among its subkeys, "C:/Program Files\Common Files\Microsoft Shared/Help 8/Microsoft.VisualStudio.Designer.Interfaces.dll" was in inconsistent state.
Stop ".NET Runtime Optimiztion Service v2.0.50215_X86" and get into this key with regedit.exe, and you may get an error "Cannot read the registry key".
The workaround for me was to change the service startup type to "Manual start", reboot the machine, delete the inconsistent registry key (once the service has been started once, that key is not accessible), and start the service.
Then the service will not loop anymore. It will take some cpus for a while to do queued jobs. And it will be okay.
You may have to re-register the above assembly again later with ngen.exe.
I haven't registered that assembly yet. :-)
Hope that this workaround might help.
Anyhow, I hope that Microsoft fix this bug soon.
i had a pb with mscorsvw : it was taking 95% of the CPU and had been running for hours. actually, the pb was due to an issue in the installation of MSVS2005-beta2 on W2k3 Server : Microsoft lists this issue in vs\readme.html file on the install disk. And they tell to repair .NET Fwk 2.0 beta2 with Add/remove programs, and it worked... So try it : repair fwk 2.0 or repair VS2005 (it also repairs the fwk). And mscrorsvw made its job quickly afterwards, as it should (a few minutes)
Hope this will work for everyone having the same pb as mine, at least, it's a clean way
