SBS 2003 Install Fails with "Vault Setup is exiting due

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
mwharton
Posts: 3
Joined: Thu Apr 01, 2004 7:21 pm
Location: Winston Salem, NC
Contact:

SBS 2003 Install Fails with "Vault Setup is exiting due

Post by mwharton » Thu Apr 01, 2004 10:14 pm

I am running SBS 2003. The installation gets all the way to the end and the following is displayed.

....(partial listing)
Found website - 'OptimistTest'
Found website - 'companyweb'
Item has already been added. Key in dictionary: "Default Web Site" Key being added: "Default Web Site"
Vault Setup is exiting due to a failure or cancellation. Error Code = 0

I click EXIT button, then I get a message that I must manual install Virtual Directory. Tthe installation starts rolling back the installation, and then I get a SUCCESSFUL installation dialog book.

I did configure the Virtual directory as VaultService, but the executing the http://localhost/vaultservice/VaultService.asmx fails with resource not available

The SBS has ISA running as a proxy.

mwharton
Posts: 3
Joined: Thu Apr 01, 2004 7:21 pm
Location: Winston Salem, NC
Contact:

Was Not a Rollback

Post by mwharton » Thu Apr 01, 2004 10:28 pm

I review the installation and I thought I saw a rollback, but it was cleaning up files and removing installation files.

I do have the ASPNET config as domainName\ASPNET and all my other web sites are running.

Here is log file

----4/1/2004 11:01:24 PM sgvaultsystem--()--
System Started
Version 2.0.1.2137
Cache Level = 1
DataBase Buffer Size = 256
LogFile Path = C:\WINDOWS\Temp\sgvault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 4320
SGVault Working Directory = C:\WINDOWS\Temp
----4/1/2004 11:17:09 PM sgvaultsystem--()--
System Started
Version 2.0.1.2137
Cache Level = 1
DataBase Buffer Size = 256
LogFile Path = C:\WINDOWS\Temp\sgvault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 4320
SGVault Working Directory = C:\WINDOWS\Temp

mwharton
Posts: 3
Joined: Thu Apr 01, 2004 7:21 pm
Location: Winston Salem, NC
Contact:

Version Information

Post by mwharton » Thu Apr 01, 2004 10:31 pm

SourceGear 2.1

Windows Server 2003
IIS 6.0
SQL Server 2000 / SP3
.NET Framework 1.1

mskrobul
Posts: 490
Joined: Wed Jan 14, 2004 10:22 am
Location: SourceGear
Contact:

Post by mskrobul » Fri Apr 02, 2004 9:52 am

If you look at the web.config file in the VaultService directory under appsettings do the connectstring and configpath keys have valid values or things like Server=SSSSSSSS; Database=DDDDDDDD;?

If valid values are listed in the web.config file then check the following:

I saw multiple websites listed on your vaultinstall.log snippet. What website did you create the VaultService virtual directory under? If VaultService isn't created under the default website and port (80) connecting as localhost will not work. You would need to connect to that website (websitename:port.domain).

Also verify that VaultService is running as an application in IIS and that it has anonymous access enabled.

If you connect to http://website/vaultservice do you see the Vault Server home page?

If you try to connect with a Client what error do you get? Is there any more information logged to the sgvault.log when you connect with a Vault Client?
Mary Jo Skrobul
SourceGear

Guest

WebConfig Settings

Post by Guest » Fri Apr 02, 2004 10:32 am

Last year I downloaded a demo version of SourceGear, but never got it working through the firewall, so I abandoned. The VaultService virtual directory is enable for Anonymous access and Integrated WIndows authentication.

The web config settings

<appSettings>
<add key="ConfigPath" value="C:\Inetpub\wwwroot\VaultService\Vault.config" />
<!-- SQLSERVERMODE-add key="ConnectString" value="Application Name='SourceGear Vault Server'; Connection Reset='false'; Server=(local); Database=sgvault; User ID=UUUUUUUU; pwd=PPPPPPPP" />SQLSERVERMODE- -->
<add key="ConnectString" value="Application Name='SourceGear Vault Server'; Connection Reset='false'; Server=(local); Database=sgvault; Integrated Security='true'" />
</appSettings>

mskrobul
Posts: 490
Joined: Wed Jan 14, 2004 10:22 am
Location: SourceGear
Contact:

Post by mskrobul » Fri Apr 02, 2004 10:50 am

What is the exact error you are getting when you try to connect to the .aspx page?

Did you get an error message in the sgvault.log file when you connected with a client?

This may be easier to troubleshoot over the phone. If you email me your phone number, someone here will call you and hopfully get this resolved.
Mary Jo Skrobul
SourceGear

Guest

Error Message from VaultService.asmx

Post by Guest » Fri Apr 02, 2004 12:39 pm

http://localhost/VaultService/VaultService.asmx


The page cannot be displayed
You have attempted to execute a CGI, ISAPI, or other executable program from a directory that does not allow programs to be executed.
--------------------------------------------------------------------------------

Please try the following:

Contact the Web site administrator if you believe this directory should allow execute access.
HTTP Error 403.1 - Forbidden: Execute access is denied.
Internet Information Services (IIS)

--------------------------------------------------------------------------------

Technical Information (for support personnel)

Go to Microsoft Product Support Services and perform a title search for the words HTTP and 403.
Open IIS Help, which is accessible in IIS Manager (inetmgr), and search for topics titled Configuring ISAPI Extensions, Configuring CGI Applications, Securing Your Site with Web Site Permissions, and About Custom Error Messages.
In the IIS Software Development Kit (SDK) or at the MSDN Online Library, search for topics titled Developing ISAPI Extensions, ISAPI and CGI, and Debugging ISAPI Extensions and Filters.

mskrobul
Posts: 490
Joined: Wed Jan 14, 2004 10:22 am
Location: SourceGear
Contact:

Post by mskrobul » Fri Apr 02, 2004 2:42 pm

Do you have any other applications running in IIS on the Vault Server that could be causing conflicts, like SharePoint?

Can you verify that other .aspx files can be viewed from a web browser on that server (other than the Vault ones)?

That error message usually means execute permissions aren't set for the virtual directory. However, the VaultService virtual directory shouldn't need execute permissions.

Are you by any chance running IIS in lockdown mode? If so, delete the msseclib.dll file from the vaultservice directory (it is only used for installation purposes). That file causes problems when IIS is in "lockdown mode".
Mary Jo Skrobul
SourceGear

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Post by jeremy_sg » Sat Apr 03, 2004 10:13 am

After contacting mwharton offline, we figured out the reason for the install failure. Windows 2003 Small Business Server ships with SQL Report Tools, which creates a second web site named Default Web Site. Having two web sites with the same name exposed a bug in our installer that we hope to have fixed in an upcoming 2.0.x release.

Post Reply