Vault has stopped logging in after Windows Update

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

Moderator: SourceGear

Post Reply
kenoyer130
Posts: 7
Joined: Thu Jul 26, 2007 9:17 am

Vault has stopped logging in after Windows Update

Post by kenoyer130 » Thu Jul 26, 2007 9:27 am

Whenever we try to log into our vault web service, we get the following error:

The Vault Server could not establish a connection to the database. Please check the server's log for detailed information. (FailDBConn)

The log file has the following entry

7/26/2007 5:41:31 AM --()-- System.Data.SqlClient.SqlException: SSL Security error.
at System.Data.SqlClient.ConnectionPool.CreateConnection()
at System.Data.SqlClient.ConnectionPool.UserCreateRequest()
at System.Data.SqlClient.ConnectionPool.GetConnection(Boolean& isInTransaction)
at System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction)
at System.Data.SqlClient.SqlConnection.Open()
at VaultServiceSQL.VaultSqlConn.OpenConn()
at VaultServiceAPILib.VaultServiceAPISystem.GetOpenSqlConn(HttpApplicationState has, VaultLoginInfo vli, VaultSqlConn& conn) at System.Data.SqlClient.ConnectionPool.CreateConnection()
at System.Data.SqlClient.ConnectionPool.UserCreateRequest()
at System.Data.SqlClient.ConnectionPool.GetConnection(Boolean& isInTransaction)
at System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction)
at System.Data.SqlClient.SqlConnection.Open()
at VaultServiceSQL.VaultSqlConn.OpenConn()
at VaultServiceAPILib.VaultServiceAPISystem.GetOpenSqlConn(HttpApplicationState has, VaultLoginInfo vli, VaultSqlConn& conn)

Trying to log into the same sqlserver with SqlServer Studio Management Express generates the following error:

===================================

Cannot connect to MACHINE.

===================================

A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: Shared Memory Provider, error: 1 - I/O Error detected in read/write operation) (.Net SqlClient Data Provider)

------------------------------
For help, click: http://go.microsoft.com/fwlink?ProdName ... nkId=20476

------------------------------
Server Name: Machine
Error Number: 4
Severity: 20
State: 0


------------------------------
Program Location:

at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.ConsumePreLoginHandshake(Boolean encrypt, Boolean trustServerCert, Boolean& marsCapable)
at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

Nothing on the server has been changed except for automatic updates installed on the 12th. I've rolled back every update but the problem persists. ISSReset and rebooted and all that also.

Help!

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Thu Jul 26, 2007 9:54 am

If you can't log in to SQL Server with SQL Server Management Express, then Vault is probably running into the same issue.

Here are some results of Internet searches on the error that might be helpful:

http://forums.asp.net/p/1110955/1710730.aspx

http://www.derkeiler.com/Newsgroups/mic ... /0051.html
Linda Bauer
SourceGear
Technical Support Manager

kenoyer130
Posts: 7
Joined: Thu Jul 26, 2007 9:17 am

Post by kenoyer130 » Thu Jul 26, 2007 12:10 pm

Woot I uninstalled and reinstalled IIS and that seems to have fixed the issue. However, when I repaired the Source Gear installation to install the service in IIS, it now has the machine name instead of the website name for the URL. How do I fix that?

jclausius
Posts: 3706
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Mon Jul 30, 2007 2:28 pm

What URL are you referring to?
Jeff Clausius
SourceGear

Terence
Posts: 164
Joined: Thu Feb 02, 2006 2:43 pm
Location: SourceGear

Post by Terence » Mon Jul 30, 2007 2:54 pm

Which version of Vault are you running?

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Post by Beth » Tue Jul 31, 2007 2:07 pm

User called. .NET had to be reinstalled after IIS was reinstalled. I think things are fixed now.

Post Reply