SourceGear Support

That is really wierd... Just a clarification, the Server was sucessfully installed and now you are trying to install the Client using the Client installer on a different machine than the server or the same machine? Are you installing the 2.03 client as an upgrade or a fresh install? Are you running ...

Thanks for the report.

We have been able to reproduce this behavoir with the IDE client and have logged a bug accordingly.

This only happens in the IDE client though. If you do a checkin with added and modified files in the GUI client, FogBugz does get updated with both changes.

It is difficult to say what is going on without some additional information. What version of Vault are you installing? Are you upgrading from a previous version of Vault or is this a fresh install? If upgrading from a previous version what version? Also, it would be helpful if you could email me the...

Please email me your vault server log (sgvault.log in the sgvault folder located in your windows temp directory) and the shadowfolder.log file (in the shadow folder directory). This may be easier to troubleshoot this over the phone. Please include your phone number in the email message and we will c...

*Usually* when a shadow folder isn't getting updated after a commit from the Client it is a permisson problem. Verify that DOMAIN\someuser has full permission to the shadow folder cache in DOMAIN\someuser's application data folder: C:\Documents and Settings\someuser\ApplicationData\SourceGear\Vault_...

It is difficult to determine what is going on without additional information. What installer are you using (Server, Client, etc)? Are you upgrading or is this a fresh install? If you are installing the server there should be a vault_install.log file located in the %temp% directory. If that is the ca...

That is really weird. The code used in the installer to detect the IIS version hasn't changed at all in version 2.02. At what point during the Server install do you get this error message? Have you changed anything in IIS since you installed 2.01? Did 2.01 install and work without incident? Was IIS ...

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 f...

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 ...

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...

Reliability VSS is well known for corrupting its database. Vault was designed from the beginning with reliability as the number one priority. All repository data is stored in a Microsoft SQL Server database, providing the Vault server with a robust and trusted data store. We also have an extensive ...

Try uninstalling the 2.01 Server (and keep your database) then re-install the 2.01 server. You shouldn't need to re-install the clients. From your log file it looks like the installer didn't have permissions to write to severinstall.html file. Verify that you are logged in as an admin user on the ma...

What version is your Server?

That message usually means the Server and Client are different versions. The current version of the Server and Clients is 2.01.

It looks like for some reason the server home page didn't get written. It is difficult to say why this happened without looking at the server log file. The server *should* still work even if it couldn't write the server home page. Can you send the error specific parts of vault_install.log file locat...

Verify that the URL for the fogbugz server is entered into the Vault Admin Tool correctly. In the Admin Tool, on the Repository Options tab the Bug Tracking Integration URL field should have the URL for the Fogbugz server. This URL should be the same URL you type into a browser when you connect to t...