A Practical Guide to SharePoint 2013

A Practical Guide to SharePoint 2013
A Practical Guide to SharePoint 2013 - Book by Saifullah Shafiq

Wednesday, September 16, 2009

Visual Sourcesafe 2005 setup fails

Scenario: To work on an old project, I need to setup SourceSafe 2005 on a machine that already has .NET Framework 3.5 installed. I start the installation but mistakenly unplug the power cable and system shuts down. Next time I start the installation, I get "Setup failed" error message. Setup fails because it cannot find Microsoft Document Explorer 2005 installed on the system. I found following link while searching for the solution: http://social.msdn.microsoft.com/Forums/en-US/vssetup/thread/e59f8083-3ebc-4b90-ae35-c4e3fcd33606 It has some good suggestions but not valid in my case. I knew something went wrong because the computer was unplugged when setup was running. If you go to "Add and Remove Programs" in Control panel, you will see .NET framework installed. In my case, there were different versions installed. From .NET 1.1 to .NET 3.5, all versions were installed. There was one instance that did not have any version number shown next to it. I removed this instance and during uninstallation, it gave message that "Installation of Microsoft Document Explorer 2005 was suspended. Do you want to continue and remove the installation" (I don't remember the exact wording). I clicked YES and this instance was uninstalled. Next, I tried to run the setup again and this time SourceSafe was installed successfully. The reason why I am posting this is because while searching Internet for the solution, I noticed several links/posts that gave miscallaneous solutions but none mentioned uninstallation of the corrupted or incomplete installation of the .NET framework. So this is also a solution, if you have tried all other options and still cannot install SourceSafe because of Document Explorer error, simply uninstall the .NET framework and run the SourceSafe setup again. Be careful if you have Visual Studio and related programs running. Make sure you uninstall the .NET framework version that is causing the problem. In my case, it was the one without any version number.

No comments:

Post a Comment