SQL Server does not exist or access denied.

Tom.Wells · Post by **Tom.Wells** » Fri Feb 10, 2006 1:27 pm

Perhaps you missed my followup question. Will upgrading to your latest version solve the problem?

Post by **jclausius** » Fri Feb 10, 2006 1:45 pm

Sorry, I didn't notice your follow up questions

Tom.Wells wrote:How do we force the Vault service to restart?

If Vault is the only Web Application on your server, choose Start-> Run -> iisreset.exe

Tom.Wells wrote:Why does it start working on its own after a period of time?

The connection pool has its own manager after a period of inactivity (10 minutes I believe), it will release pooled database objects, and new ones can be obtained.

Tom.Wells wrote:Will upgrading to the latest version of Vault get us to the 2.0 framework and solve the problem?

Moving from Vault 2, Vault 3.1.7 has a number of improvements for better concurrency for multi-user installations, support for .Net 2.0 framework, and other fixes. See What's new in 3.0 and 3.1.0 Release Notes for more specific information.

As for SQL Server restarts, to my knowledge, if SQL Server is shutdown while the Vault Server has active connections to the database, you must still restart the Vault server.