File version not updating?

sh1rp · Post by **sh1rp** » Thu May 25, 2006 10:04 am

Hi. I am using Vault 3.1.7 with VisualStudio 2005 and am having a problem. It seems that when checking out a file with VisualStudio, editing it and checking it back in, Vault does not always update the file information. It will act as though no changes were made. Does anyone know why this might be?

lbauer · Post by **lbauer** » Thu May 25, 2006 12:18 pm

What indicates that the file has not changed?

If you use the Vault GUI Client to see the file history, is there evidence of the checkin?

Do you see any kind of pattern to this? Are there particular kinds of files that don't get checked in?

Are there any errors in the Vault Server log (sgvault.log in %windir%\temp\sgvault) that coincide with the time(s) of the checkins?

We could enable more logging to see if we can capture what is going on. Enable debug logging in the Vault Admin Tool->Server Options->Logging.

Also enable IDE logging:

http://support.sourcegear.com/viewtopic.php?t=2898

Hopefully, this will provide additional information.

sh1rp · Post by **sh1rp** » Thu May 25, 2006 12:25 pm

The problem is that it has happened, and there is no particular pattern to it. The history does not show that a file was checked in, but it was checked in from one PC and the modified file was even checked out from another, but no sign of this check-in was shown in the GUI client.

I'm not sure if any errors occur when it happens, because as I said, it has only happened at random times, which have only now been realized. I do know, however, that whenever the GUI client or VisualStudio with source control enabled is closed, the following warning is put into the Windows event log.

Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date: 5/25/2006
Time: 9:02:00 AM
User: N/A
Computer: HSDEV2
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 5/25/2006 9:02:00 AM
Event time (UTC): 5/25/2006 2:02:00 PM
Event ID: 2f0f9659bb5a49a2907cd6900e047881
Event sequence: 3350
Event occurrence: 55
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/4/Root/VaultService-2-127919305282138773
Trust level: Full
Application Virtual Path: /VaultService
Application Path: E:\WebData\Vault\
Machine name: HSDEV2
This error shows up in the event log whenever someone disconnects from Vault.

Process information:
Process ID: 1836
Process name: aspnet_wp.exe
Account name: HSDEV2\ASPNET

Exception information:
Exception type: NullReferenceException
Exception message: Object reference not set to an instance of an object.

Request information:
Request URL:
Request path:
User host address:
User:
Is authenticated: False
Authentication Type:
Thread account name: HSDEV2\ASPNET

Thread information:
Thread ID: 10
Thread account name: HSDEV2\ASPNET
Is impersonating: False
Stack trace: at VaultServiceAPILib.VaultServiceAPISystem.GetOpenSqlConn(HttpApplicationState has, VaultLoginInfo vli, VaultSqlConn& conn)
at VaultServiceAPILib.VaultServiceAPI.Logout(HttpApplicationState has, HttpSessionState hss)
at VaultService.Global.Session_End(Object sender, EventArgs e)

sh1rp · Post by **sh1rp** » Thu May 25, 2006 1:24 pm

Actually, looking through the Vault logfiles, I believe I may have found an error that occured when the files in question were checked in. The lines in the file look like this around the check that I think was the problem.

----4/4/2006 4:48:03 PM eCAPSHost--mysite.org(myIPaddress)--SSL Disabled System.Data.SqlClient.SqlException: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ThrowExceptionAndWarning()
at System.Data.SqlClient.TdsParserStateObject.WriteSni()
at System.Data.SqlClient.TdsParserStateObject.WritePacket(Byte flushMode)
at System.Data.SqlClient.TdsParserStateObject.ExecuteFlush()
at System.Data.SqlClient.TdsParser.TdsExecuteRPC(_SqlRPC[] rpcArray, Int32 timeout, Boolean inSchema, SqlNotificationRequest notificationRequest, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteScalar()
at VaultServiceSQL.VaultSqlSCC.GetUserRepositoryLastChange(VaultSqlConn conn, Int32 nRepID, DateTime& dtLastChg) at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ThrowExceptionAndWarning()
at System.Data.SqlClient.TdsParserStateObject.WriteSni()
at System.Data.SqlClient.TdsParserStateObject.WritePacket(Byte flushMode)
at System.Data.SqlClient.TdsParserStateObject.ExecuteFlush()
at System.Data.SqlClient.TdsParser.TdsExecuteRPC(_SqlRPC[] rpcArray, Int32 timeout, Boolean inSchema, SqlNotificationRequest notificationRequest, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteScalar()
at VaultServiceSQL.VaultSqlSCC.GetUserRepositoryLastChange(VaultSqlConn conn, Int32 nRepID, DateTime& dtLastChg)

lbauer · Post by **lbauer** » Thu May 25, 2006 1:44 pm

Looks like it might be a connectivity issue.

What version of SQL Server are you using? What type of connection do you have -- are you on the LAN, using a cable modem, dial-up, etc?

sh1rp · Post by **sh1rp** » Thu May 25, 2006 1:56 pm

I'm using MS SQL Server 2000 and it's on the LAN.

sh1rp · Post by **sh1rp** » Tue May 30, 2006 12:50 pm

I think this problem could be avoided if there were some way to configure the client to display an error message when check-ins don't go through. Is there any way to do that?

Or, is there perhaps some way to have the server send out an email or do something to notify the user when an error occurs?

lbauer · Post by **lbauer** » Thu Jun 01, 2006 6:38 am

Generally, if a checkin fails, there's a message in the Messages pane of the GUI Client, but VS 2005 might not give a message. Vault 4.0 will have better integration with Visual Studio, so we can provide better feedback from the IDE Client if something goes wrong.