ASP.NET error on client disconnect

[mbainbridge]

Every time a client (normal Vault Pro client) disconnects, our server throws an ASP.NET error:

Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date: 09/11/2011
Time: 13:29:21
User: N/A
Computer: NCLTW-APP0002
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 11/9/2011 1:29:21 PM
Event time (UTC): 11/9/2011 1:29:21 PM
Event ID: a0be2858920540979ff077d60d0db5d2
Event sequence: 71
Event occurrence: 13
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/1/Root/VaultPro-1-129652964961992583
Trust level: Full
Application Virtual Path: /VaultPro
Application Path: C:\inetpub\wwwroot\VaultPro\
Machine name: NCLTW-APP0002

Process information:
Process ID: 1880
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: 7
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace: at MantisServiceLib.Helpers.LogMessage(DNLogEntryType let, String strMsg)
at MantisServiceLib.Helpers.DeleteSession(HttpSessionState hss, Boolean signOut)
at MantisServiceLib.Helpers.DeleteSession(HttpSessionState hss)
at Mantis.Global.Session_End(Object sender, EventArgs e)

No errors are logged in sgvault.log:

----11/9/2011 1:29:21 PM User.Name--PC-NAME(ip.add.re.ss)--SSL Disabled ASMX: Logout started.
----11/9/2011 1:29:21 PM User.Name--PC-NAME(ip.add.re.ss)--SSL Disabled Logout
----11/9/2011 1:29:21 PM User.Name--PC-NAME(ip.add.re.ss)--SSL Disabled ASMX: Logout finished.
----11/9/2011 1:29:21 PM --()-- Beginning SQL transaction 2200785
----11/9/2011 1:29:21 PM --()-- DB: DeleteSession started.
----11/9/2011 1:29:21 PM --()-- DB: DeleteSession finished.
----11/9/2011 1:29:21 PM --()-- SQL transaction 2200785 successfully committed.
----11/9/2011 1:29:21 PM --()-- Beginning SQL transaction 23123322
----11/9/2011 1:29:21 PM --()-- DB: DeleteSession started.
----11/9/2011 1:29:21 PM --()-- DB: DeleteSession finished.
----11/9/2011 1:29:21 PM --()-- SQL transaction 23123322 successfully committed.

I'm used to these messages popping up occasionally with Fortress 2.0.4, but since we upgraded to Vault Pro 5.1.2 they're far more frequent - dozens a day instead of a few a week.

Clients are running 32-bit XP Pro, the server is running Win2k3+SQL2005, sadly also both 32-bit.

[Beth]

Do you have any errors occurring at the same time in the Vault Server Log found at %windir%\temp\sgvault\sgvault.log?

[mbainbridge]

Sorry, I didn't make it clear - the sgvault.log snippet was extracted from the server log file. The timestamp coincides with the ASP.NET error in the server's Application Event log

I also can't see anything in the client log file which looks like an error (set enableLogging to "true" and classesToLog to "all" in VaultGUIClient.exe.config). It's a bit large to post here - about 2.9MB just to start and stop the client...

[Beth]

I think we should first make sure that all the 2.0 errors are disconnects, and taking a closer look might help. Could you send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread?

Have the users noticed any problems?

[Beth]

I've received the email and we will discuss this further offline.
HS: 224348

[Beth]

I've reproduced the issue and have logged a bug.

F: 16004