Handoff Log

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

Moderator: SourceGear

Post Reply
aprole
Posts: 25
Joined: Wed Sep 29, 2010 12:24 pm

Handoff Log

Post by aprole » Thu Oct 07, 2010 7:32 am

Hello,

Is there a log that displays the status of a hand off? I did a hand off and would like to see if there were any errors.

Thanks,
Alex

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

Re: Handoff Log

Post by Beth » Thu Oct 07, 2010 7:36 am

The hand-off logs to the Vault server log found at %windir%\temp\sgvault\sgvault.log. Go get more details than logins, logouts, and errors, you will need to place the log into debug mode. That is changed in the admin web page under the logging link. It creates much larger logs, so it might also be good to switch your log archiving to daily at the same time to keep your log files smaller. That setting is located in the logging link as well.
Beth Kieler
SourceGear Technical Support

aprole
Posts: 25
Joined: Wed Sep 29, 2010 12:24 pm

Re: Handoff Log

Post by aprole » Thu Oct 07, 2010 7:49 am

There was no information about the handoff, just logins and logouts. There is a an exception "Vault Failed to establish a connection to the database", and this is like ten hours after I started the handoff, at 3:20am. I don't know if it's related to the handoff. Unfortunately I did not set the log to debug mode. Could this exception possibly be related to the handoff?

Here is the part of the log I was referring to.
I logged in at 5:34:40 login to do the handoff.

----10/6/2010 5:34:40 PM admin--localhost(127.0.0.1)--SSL Disabled Login
----10/7/2010 3:20:39 AM --()-- Vault Failed to establish a connection to the database.
----10/7/2010 3:20:40 AM --()-- System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
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.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
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 VaultServiceSQL.VaultSqlConn.OpenConn()
at VaultServiceAPILib.VaultServiceAPISystem.GetOpenSqlConn(VaultSqlConn& conn) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
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.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
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 VaultServiceSQL.VaultSqlConn.OpenConn()
at VaultServiceAPILib.VaultServiceAPISystem.GetOpenSqlConn(VaultSqlConn& conn)
----10/7/2010 3:20:40 AM --()-- The connection to the database failed for VaultServiceAPI.Logout: FailDBConn
----10/7/2010 7:59:33 AM sgvaultsystem--()--
System Started
Version 5.0.4.18845
Cache Level = 1
DataBase Buffer Size (KB) = 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 = 10080
SGVault Working Directory = C:\WINDOWS\Temp
SGVault Server URL =
Identity = DEVSERVER\ASPNET
----10/7/2010 7:59:45 AM admin--localhost(127.0.0.1)--SSL Disabled Login


Thanks for your help,
Alex Prole

aprole
Posts: 25
Joined: Wed Sep 29, 2010 12:24 pm

Re: Handoff Log

Post by aprole » Thu Oct 07, 2010 8:43 am

According to the event log, the system shut down automatically to install windows updates at the same time this exception occurred. Still not sure if this interrupted the handoff. We decided to delete the repository and try the hand off again.

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

Re: Handoff Log

Post by Beth » Thu Oct 07, 2010 9:14 am

I think the route you are taking is the best way to go. Set the logging to debug mode before starting. Also, if hand-off is taking a long time, you might get better results by handing off smaller chunks at a time rather than an entire VSS database.
Beth Kieler
SourceGear Technical Support

Post Reply