Null object ref at VaultServiceAPISystem.GetOpenSqlConn

futura · Post by **futura** » Sun Apr 02, 2006 8:34 pm

Hi,

I recently migrated the Vault web service to a new web server, in the process upgrading from 3.1.2 to 3.1.8.

Everything with the conversion went fine, the entire installation process was flawless. (BTW, congrats on a smooth, intuitive installation process!)

Once on the new server, it defaulted to .NET 1.1 and I switched in IIS 6.0 configuration settings to run on 2.0.

I'm now getting the following warning message in my event log on the web server.

1. Is this something I should be worried about? I'm not receiving errors at my client, and I can't really see what may or may not be happening here.

2. Are there any corrective actions I can take to make this not warn?

Thanks in advance for any advice or help.

-Aaron

------------------------------------------
Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date: 4/2/2006
Time: 9:19:44 PM
User: N/A
Computer: (blah blah)
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 4/2/2006 9:19:44 PM
Event time (UTC): 4/3/2006 2:19:44 AM
Event ID: 57f4cb16f70b49f4831a9f6ca5db323b
Event sequence: 75
Event occurrence: 3
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/7899blah118/Root/VaultService-1-1278850blah31743
Trust level: Full
Application Virtual Path: /VaultService
Application Path: (blahblahblah)httpd\sites\VaultServer\
Machine name: (blah blah)

Process information:
Process ID: 3148
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: (blah: impersonated domain user)

Thread information:
Thread ID: 6
Thread account name: (blah: impersonated domain user)
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.

lbauer · Post by **lbauer** » Mon Apr 03, 2006 7:57 am

Do these warnings correspond to any particular operation in Vault, such as a login or logout?

Check the Vault server log (sgvault.log in %windir%\temp\sgvault) to see if the server reports any errors.

lbauer · Post by **lbauer** » Mon Apr 03, 2006 8:35 am

Update: This is a known issue that has been fixed for Vault 3.5. The Event Viewer message is not harmful. It is related to a clean up thread that may not be notifying the database properly.

Another report here:
http://support.sourcegear.com/viewtopic.php?p=20953

futura · Post by **futura** » Mon Apr 03, 2006 9:08 am

Thanks for the update. What is the anticipated release date for 3.5?

lbauer wrote:Update: This is a known issue that has been fixed for Vault 3.5. The Event Viewer message is not harmful. It is related to a clean up thread that may not be notifying the database properly.

Another report here:
http://support.sourcegear.com/viewtopic.php?p=20953

lbauer · Post by **lbauer** » Mon Apr 03, 2006 9:10 am

Vault 3.5 is scheduled for release sometime in May.

futura · Post by **futura** » Mon Apr 03, 2006 9:11 am

Thanks.

lbauer wrote:Vault 3.5 is scheduled for release sometime in May.

SourceGear Support

Null object ref at VaultServiceAPISystem.GetOpenSqlConn

Null object ref at VaultServiceAPISystem.GetOpenSqlConn

ASP.NET 2.0 benign error message. Thanks.

thanks