Vault service throws exception when client logs out

[gsmalter]

In the Application Event Log on the Windows Server that is hosting the Vault Service, ASP logs the following event when I close the Vault GUI Client on a computer that is accessing the server remotely.

Everything seems to work normally from the user's perspective. Am I in danger of losing data or having anything else bad happen?

Thanks.

Greg

Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 1/2/2006 11:22:31 PM
Event time (UTC): 1/3/2006 4:22:31 AM
Event ID: cf908084a08943febfbd7117d16b87ae
Event sequence: 148
Event occurrence: 5
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/1/Root/VaultService-1-127807323743906250
Trust level: Full
Application Virtual Path: /VaultService
Application Path: C:\Inetpub\wwwroot\VaultService\
Machine name: SWINGLINE

Process information:
Process ID: 3832
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE

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: NT AUTHORITY\NETWORK SERVICE

Thread information:
Thread ID: 8
Thread account name: NT AUTHORITY\NETWORK SERVICE
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)


Custom event details:

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

[gsmalter]

I should mention we're using the newest 3.1.6 version of the client and server.

Greg

[gsmalter]

I think this is the same issue that jlhsd brought up in the support forum. I guess that means everything is okay.

[jclausius]

Yes.

There is a clean up thread on the session's ending. It will not cause any problems. As mentioned in the other thread, since the exception has no real bearing, this exception will be cleaned up in the Vault 4.0 release.