25 comments
.NET 
This blog post will give you an indication in what kind of trouble you can get when the installation of a service pack fails. I must say it took me a while to get my original development environment up and running again. But the end results are that the IDE is up and running again. J
It all started when I installed the Visual Studio 2005 SP1 Beta and this is where the trouble started. The installation encountered an out of disk space error on a very crucial moment I guess. The installation fist took about half an hour before I got the message that I needed to uninstall the web application projects for ASP.NET. The installer asked me kindly if it should do the removal and so I let it do the removal.
After it removed the web application projects it again took a very long period and I got another message that it ran out of disk space. I know for sure I had more then 1 GB of free space before I applied the service pack, but somehow it must have managed to generate so much more data on disk that it ran out of disk space. The Dialog stated I should free up some space and click retry.
This is the message from the eventlog that is crucial and what helped me find a clue to fix my machine again:
Product: Microsoft Visual Studio 2005 Team Suite – ENU — Error 1307.There is not enough disk space to install this file: C:WINDOWSwinsxsx86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.363_x-ww_691a48fdmsvcp80.dll. Free some disk space and click Retry, or click Cancel to exit.
During the installation I noticed the message box with the same message as in the eventlog and I removed a VPC image of 8 GB and clicked retry. After only a few minutes now the installation totally broke down. I received an error message that the installer encountered and it gave the following message:
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2350
Wow, that is very helpful J
Now the installer started to rollback the things it had done, but this also resulted in several errors. The first one I got was:
Product: Microsoft Visual Studio 2005 Team Explorer – ENU — The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2908. The arguments are: {AF4DBA1F-73E8-499B-A445-B12D4881A8F1}, ,
And after this I received this message about a hundred times more with different GUIDS.
I already thought that I was in serious trouble now and after the installer got closed I tried to start visual studio again to check if it still worked. Well it did not and gave me a great error message
The application failed to initialize properly (0xc0000034). Click on OK to terminate the application.
Ok, now I officially knew that my development environment was toast and I knew I need to start fixing things. The first thing I tried is uninstalling visual studio 2005, but that did not work. Therefore I tried to repair my .NET 2.0 installation, but apparently the .NET framework was affected by the service pack installation as well. When I ran the repair of .NET 2.0 I got the error message :
Product: Microsoft .NET Framework 2.0 — Error 25007.Error occurred while initializing fusion. Setup could not load fusion with LoadLibraryShim(). Error: The handle is invalid.
This message told me something was terribly wrong with the fusion dll that is responsible for loading .NET assemblies. This could explain why all setups are failing, because I know the fusion.dll contains entry points to install assemblies in the GAC or remove them from the GAC. Therefore I took the tool Dependency Walker(http://www.dependencywalker.com/) to have a look at the fusion.dll that you can find in your framework directory.
The tool showed me that the fusion dll tried to load a library called MSVCR80.dll at the location C:WINDOWSWinSxSx86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.363_x-ww_691a48fd
The dll was missing and therefore broke the fusion dll!
As you can see from the previous error message I showed you you can tell this must be caused by the installation. It referred to exactly the dll as the one that failed to install when I ran into disk space troubles.
After searching for the files in my Visual Studio directory I found it in the redistributables folder for the CRT libraries. After copying the file back to the fore mentioned directory, I was able to repair run the.NET 2.0 installation again and repairing the framework setup.
After a reboot of my machine I was able to install Visual Studio 2005 again from the original installation media. Then after reinstall I got all kinds of package load failures. I got messages like:
VSIP: Package 'VsRptDesigner Package' has failed to load ( GUID = {97358C99-E52D-42C7-8B7C-B59CC4425F4B} ).
Please contact package vendor for assistance.
VSIP: Package 'Visual Studio Macros Package' has failed to load ( GUID = {A659F1B3-AD34-11D1-ABAD-0080C7B89C95} ).
Please contact package vendor for assistance.
VSIP: Package 'Visual C++ Language Manager Package' has failed to load ( GUID = {8C2EA640-ABC1-11D0-9D62-00C04FD9DFD9} ).
Please contact package vendor for assistance.
After calling the package vendor for assistance I decided I was on my own and needed to fix the problem myself J
To diagnose this problem further I started Visual Studio with the command line option /log. This will make the IDE log its activities in a file called ActivityLog.xml. After closing the IDE you can open the XML file and then it will show you highlighted what might have gone wrong in the IDE.
I saw entries marked like
LoadLibrary failed for package [Visual Studio Macros Package]
C:Program FilesMicrosoft Visual Studio 8Common7IDEvsmacros.dll
Since this error can be caused by the same problem I encountered previously I decided to load the DLL myself using the dependency walker tool again but now on the vsmacros.dll. And also this time I got the message that the dll could not be loaded, but this time because it could not find the dll MSVCP80.dll. I found that dll at the same location as the first one. I decided to copy over all dll’s from the redistributable folder and then loaded visual studio again.
Now that Finally gave the result I needed and the IDE runs Ok again!
I must say it was quite a journey to get this problem fixed. It took me many hours to find what was broken and causing the error messages. I hope this information can help you as well if you might run into troubles installing the service pack. One thing to keep in mind when applying the SP is to ensure you have lots of disk space available, so you don’t run into the exact same problems as I did. Chances are that the SP will work for you without any problem. It seems I ran into disk space problems on a very crucial part of the installation and that caused my troubles.
I think I will now first install the SP again on a Virtual Machine and have a look how well that will go. 🙂
25 comments
Marcel,
Don’t you know you shouldn’t install beta software on production machines / laptops? 😉
Nice adventure…err…post though! 🙂
bartg
hi marcel
My pc configuration is:
256 ram,80 gb harddisk 2.4 gh processor speed, xp professional sp2 ,
whenever i installed a vs-2005 it gives error the following error
“The ENU is not encountered a problem during setup.The set is failed to installed”.
May u please tell me wat is this error and how i resolve this?
thnx in advance.
abhishek
Abhishek
@Abhishek: The solution to your problem is simple, you do not have enough RAM. Upgrade to at least 1 GB or prefably to 2 GB ram to run VS 2005 properly.
Christian
Thank you!
I had the exact same problem – low disk space (2gb is low?) caused the SP install to fail. Even the Office 2007 beta stopped working after that.
Although I used a different method (the sysinternals filemon application to check why the office applications failed), the Google search for MSVCR80.dll + SP led me right here.
Everything works now so I am going to reinstall VS 2005 and try again 🙂
Stoyan
Thank you!!!!
I experienced the exact same problem you did. I tried to install SP1 Beta for VS 2005 on a machine with 1 GB of free space and ran out of room. I uninstalled the .NET 2.0 framework and tried to reinstall, only to recieve the the fusion.dll error.
The difference in my problem is that the msvcp80.dll did exist on my system, only under a different folder (it was under C:WINDOWSWinSxSx86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd). I decided to rename this folder to match the path you mentioned above, and was then able to install .NET 2.0.
I have since reinstalled my Visual Studio and and back up and running. Again, thanks very much.
Jose
Adding in another chime of thanks!
This problem still exists on the final release of VS 2005 SP1; I ran out of disk space on installation and during the rollback it apparently deleted msvcp80.dll and the related VC80 runtime files from WinSxS. Even uninstalling the .NET Framework 2.0 and reinstalling wouldn’t fix the problem, I guess since some registry setting somewhere was fooling the .NET 2.0 installer into thinking the files were already there, safe and sound, and so they didn’t need to be installed.
Copying the files from the VS.NET 2005 redist directory into their proper location in WinSxS fixed the problem and got the Framework and Visual Studio back up and running.
Timothy Fries
Exactly the same problem here with the final release of SP1. What a bloody cockup! Half the programs on my PC now crash, and I can’t do any development at all.
Hopefully the tips here will help me fix it….
Brian Smith
The problem is that when SP1 setup is doing rollback, it is not cleaning correctly the shared C runtime libraries. The WindowsWinSxS contains set of directories with the various shared installations. In addition there are directories named “Policies” and “Menifests”. These directories contain files which are used to find out the correct version of a given library (DLL) to use with a specific application.
The problem is that SP1 setup remove the shared C runtime (CRT) directory without removing the corresponding data in the Menifest and Policies directory. The result is that loading any software that try to use the version 8 of the C runtime library will fail doing so.
To solve this issue you can do one of two things:
1. Create a directrory with the right name (or use the empty one if this is the case) and copy the runtime DLLs to there. Make sure that you copy the right versions otherwise most things will work, but some may not…
or
2. Remove the orphan policy and menifest entries (that what I did).
Yuval Rakavy
Your solution did fix the devenv.exe crash. Thanks for taking the time and posting it
Arunkumar Viswanathan
Thanks from me as well. It is unbelievable to me that Microsoft can’t be bothered to check disk space and prevent this. Windows has really become a mess lately. DLLs were never as bad as this mess of abstractions has become.
Scott Cantor
Thank you wery much for this solution.
I to can’t bolive that guys at Microsoft put out SP which breaks more things then it fixes…
Chandler Bing
Thank you!
Exactly the same problem with the final release of SP1.
SP1 is destructive!!!
Jakub
pls can u tel….whenever i start my system a message is displayed on the screen is that “the application failed to intialize properly (0xc0000034).” please can u solve my problem….
shiva netha
Happened exactly the same to me. 3 GB wasn’t enough for SP1. Thanks a lot, it helped a lot.
Attila Bleier
Same thing happened to me with release – 3+ GB of space. 2+ months later and still the simple disk-check would’ve saved me a ton of heartache…I wish I saw this ahead of time…
drew
Same thing here, but I guess it was more polite with me and *JUST* waste a couple of hours for watching progress ( lol ) bar going back and forth and after the rollback the VS 2005 Team System is still alive. I just hope it didn’t broke something and hide it somewhere without telling me today :/
How they could release SP without including the checking first if it will fit the hdd free space ? :/
Tom
Thanks Marcel de Vries for the post. I’m installing the final SP1 (not beta) but it gives me the same error – (Not enough space) – but i’ve 3.72 GB. Now i’m stuck in that part where it says not enough disk space. after reading ur post, i’m not sure what to click! anyway… thanks for this post. Might help me in fixing the problems that i’ll encounter in the next few hours. By the way i was thinking about System Restore. Can it be helpful?
Azmath
Hi, i have same error like descibed above. I restore MSVCP80.dll (found using dependecy walker in fusion.dll) But in fusion.dll there is one more file missing – dwmapi.dll. Is this missing file reason of error Product: Microsoft .NET Framework 2.0 — Error 25007.Error occurred while initializing fusion. Setup could not load fusion with LoadLibraryShim(). Error: The handle is invalid.
when I trying to repair .NET 2.0?
Jindrich Brezina
Lucky…. http://www.alexhopmann.com/article%202006-12-26.htm?c=h solved problem of .NET 2.0 repair.
Jindrich Brezina
Yep, happened to me also. I’m getting really tired of constantly doing battle with Microsoft products. Wasted so much time and frustration getting Windows to work again.
A simple disk space check should be a mandatory part of all installations. Microsoft, I hope you’re listening. You owe a lot of people a beer or two.
Rod Weir
Very informative article! Thanks for posting this.
Saved me alot of time as I was going through the same errors. Thanks again.
jv
Thank you! I also was bitten by insufficient space, but this was with a release version of sp1. You’ve saved me a lot of time!
Eric Wasgatt
“Don’t you know you shouldn’t install beta software on production machines / laptops”
This problem still exists. I experienced it on a VPC and the primary VHD ran out of space. It completely destroys the installation and is incapable of rolling back correctly.
I think this sucks how their software doesn’t remove itself correctly and the “repair” installation doesn’t actually repair anything… What’s the point in it!
Cheers for the info in your blog!
Nick
Once again, thank you for posting this. I can see it would have been very unlikely that I would have been able to figure this out on my own!
Tobin Pipkin
Thanks sooo much for your tip Marcel. In my case, right folder name was another (x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_6b128700) i think. Anyway, it could finally install NET Framework 2.0. Finally.
Thanks again.
Luis Alberto Mendieta