Visual Source Safe installation problem on Windows 2003 server   

When I tried to install Visual Source Safe installation problem on 
Windows 2003 server, "Microsoft Visual SourceSafe 2005 - ENU has 
encountered a problem during setup. Set up did not complete correctly".

I followed the links on the setup form and did as much as I can to stop 
services, deleting temp files etc. But I am still having the same 
problem after did things as suggested by the web page.

Here is a copy of the log

[08/21/07,12:59:23] setup.exe: [2] ISetupComponent::Pre/Post/Install() 
failed in ISetupManager::InstallManagerHelper() with HRESULT -2147023278.
[08/21/07,12:59:23] setup.exe: [2] Component error string not specified 
in ISetupManager::AddToActionResultCollection()
[08/21/07,12:59:25] VS70pgui: [2] DepCheck indicates Microsoft Visual 
SourceSafe 2005 - ENU is not installed.
[08/21/07,13:01:09] setup.exe: [2] ISetupComponent::Pre/Post/Install() 
failed in ISetupManager::InstallManagerHelper() with HRESULT -2147023278.
[08/21/07,13:01:09] setup.exe: [2] Component error string not specified 
in ISetupManager::AddToActionResultCollection()
[08/21/07,13:01:10] VS70pgui: [2] DepCheck indicates Microsoft Visual 
SourceSafe 2005 - ENU is not installed.
[08/21/07,13:44:36] setup.exe: [2] ISetupComponent::Pre/Post/Install() 
failed in ISetupManager::InstallManagerHelper() with HRESULT -2147023278.
[08/21/07,13:44:36] setup.exe: [2] Component error string not specified 
in ISetupManager::AddToActionResultCollection()
[08/21/07,13:44:37] VS70pgui: [2] DepCheck indicates Microsoft Visual 
SourceSafe 2005 - ENU is not installed.
[08/21/07,13:46:12] setup.exe: [2] ISetupComponent::Pre/Post/Install() 
failed in ISetupManager::InstallManagerHelper() with HRESULT -2147023278.
[08/21/07,13:46:12] setup.exe: [2] Component error string not specified 
in ISetupManager::AddToActionResultCollection()
[08/21/07,13:46:13] VS70pgui: [2] DepCheck indicates Microsoft Visual 
SourceSafe 2005 - ENU is not installed.


Thanks

Charles Zhang

date: Tue, 21 Aug 2007 14:22:23 -0700   author:   Charles Zhang am

RE: Visual Source Safe installation problem on Windows 2003 server   

Hello Charles,

According to your description, you cannot install Microsoft Visual 
SourceSafe 2005 on Windows 2003 server. Please correct me if I 
misunderstood anything.

I'm pretty sure this issue is not related to Windows 2003. I have installed 
VSS 2005 on Windows 2003 before.

For such installation issue, would you please check the following points at 
first?
1)	Have you installed VSS on this machine before? If true, please uninstall 
it.
2)	Have you tried to install VSS 2008 on another machine by this disk? This 
could help us to check if Visual SourceSafe 2005 disk is damaged.

Please try the above method and let me know the result. I'm waiting for 
your reply.
Have a great day.
Best regards,

Wen Yuan
Microsoft Online Community Support 
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

date: Wed, 22 Aug 2007 10:53:49 GMT   author:   (WenYuan Wang [MSFT])

RE: Visual Source Safe installation problem on Windows 2003 server   

> Have you tried to install *VSS 2008* on another machine by this disk? 
This could help us to check if Visual SourceSafe 2005 disk is damaged.

What I mean is VSS 2005 (Visual SourceSafe 2005). Sorry for that. 

Wen Yuan
Microsoft Online Community Support 
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

date: Thu, 23 Aug 2007 12:54:01 GMT   author:   (WenYuan Wang [MSFT])

RE: Visual Source Safe installation problem on Windows 2003 server   

Hello Charles,

-2147023278
means
ERROR_INSTALL_ALREADY_RUNNING

I have performed further research on this issue today.

I suspect that there is another user (by Remote Desk) who is installing VSS 
2005 on your Windows 2003 when you are going to install VSS 2005 on this 
machine.
Because there is already another Install running, 
ERROR_INSTALL_ALREADY_RUNNING will be thrown.

I have reproduced this behavior on my side.

If the issue still persists, I'd like to suggest you check if there is 
another user connects to your Windows 2003 machine. 
1)	Press "Ctrl+ALT+DEL" ("CTRL+ALT+END" for remote desk) to open Task 
manager.
2)	Select User Page.
3)	Check if there is another user is connecting to this machine?

Hope this helps.
Wen Yuan
Microsoft Online Community Support 
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

date: Thu, 23 Aug 2007 13:33:26 GMT   author:   (WenYuan Wang [MSFT])