I am using VaultPro v5.1.2 64 bit. The server has been working fine, but today, following a reboot (but without us making any changes or windows updates) it doesn't work - in the sgvault.log it reported several hrs ago that:
"The connection to the database failed for VaultServiceAPI.Logout: FailDBConn
Could not load connect string. There is probably an error with the encrypted password for the sgvaultuser database user. Contact technical support at http://support.sourcegear.com "
No new logs have been generated since then, the web page fails to load (no error code) and the vault client reports:
"Unable to connect to https://xxMyServerxx/VaultService. No server was found at the specified URL. Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client. Web Exception: The underlying connection was closed: An unexpected error occurred on a send."
I have tried running a repair but this hasn't helped. Any ideas on how to fix it?
FailDBConn
Re: FailDBConn
In the Vault website are web.config files that have SQL connection strings, which create the connection to the database. It's unlikely, but possible to have had the correct connection information sitting in memory, but then a change in the web.config that is waiting to be reloaded. I say unlikely because the default IIS setup is to have an application pool recycle as soon as a related web.config file changes.
Another possibility is that the SQL Server didn't come back online.
Here are some of your options.
1) Look in your Administrative Tools - Services and make sure the SQL Server service is started. If it is not, then that is the root cause of the problem, and you can skip any of the other options.
Try to start the service. If it won't start, check which logon is used for the service. You might be able to change it to a local service login to run the service.
2) Look at the SQL Connect strings in the web.config files in the Vault website. The default location is C:\inetpub\wwwroot\vaultservice, but it's possible to have been installed somewhere else. If SQL authentication is used, then there will be an encrypted password in the connect string. There are multiple databases to authenticate to, so check each to see if their encrypted passwords match. If they don't, make copies of the passwords and try replacing the one for the sgvault database to see if it works. After replacing the encrypted password, you will need to perform an IIS reset, by running iisreset at an administrator command prompt. If there are other websites that can't be reset, then you can alternatively recycle each of the Vault application pools instead.
3) Another option you have is to allow Vault to completely reset the connection during a reinstall. Backup the databases. Then uninstall Vault and choose the option to keep the databases. Then install and choose the option to reuse the same databases.
If you don't know what options were chosen during the last install, you can post or send me your Vault_install.log from the server.
Another possibility is that the SQL Server didn't come back online.
Here are some of your options.
1) Look in your Administrative Tools - Services and make sure the SQL Server service is started. If it is not, then that is the root cause of the problem, and you can skip any of the other options.
Try to start the service. If it won't start, check which logon is used for the service. You might be able to change it to a local service login to run the service.
2) Look at the SQL Connect strings in the web.config files in the Vault website. The default location is C:\inetpub\wwwroot\vaultservice, but it's possible to have been installed somewhere else. If SQL authentication is used, then there will be an encrypted password in the connect string. There are multiple databases to authenticate to, so check each to see if their encrypted passwords match. If they don't, make copies of the passwords and try replacing the one for the sgvault database to see if it works. After replacing the encrypted password, you will need to perform an IIS reset, by running iisreset at an administrator command prompt. If there are other websites that can't be reset, then you can alternatively recycle each of the Vault application pools instead.
3) Another option you have is to allow Vault to completely reset the connection during a reinstall. Backup the databases. Then uninstall Vault and choose the option to keep the databases. Then install and choose the option to reuse the same databases.
If you don't know what options were chosen during the last install, you can post or send me your Vault_install.log from the server.
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support