ASP.NET 2.0 Unhandled Exception
Moderator: SourceGear
ASP.NET 2.0 Unhandled Exception
I just installed Vault 3.15 onto a new website (not the default) in IIS.
Things seem to work ok, except when I exit the Admin tool the following event shows up in Win2K event log. I also included the Vault log at the end.
Any ideas?
Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date: 12/27/2005
Time: 4:42:27 PM
User: N/A
Computer: HSDEV2
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 12/27/2005 4:42:27 PM
Event time (UTC): 12/27/2005 10:42:27 PM
Event ID: c5c02ba09d0c4d8094993d0e7be3d78a
Event sequence: 28
Event occurrence: 2
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/4/Root/VaultService-1-127801947331908750
Trust level: Full
Application Virtual Path: /VaultService
Application Path: E:\WebData\Vault\
Machine name: HSDEV2
Process information:
Process ID: 3392
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: 7
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)
Custom event details:
==========================================
# SourceGear Vault Server
----12/27/2005 4:05:35 PM sgvaultsystem--()--
System Started
Version 3.1.5.3546
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = E:\Program Files\SourceGear\VaultLogs\sgvault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 4320
Active Directory Domain =
SGVault Working Directory = E:\Program Files\SourceGear\VaultLogs
SGVault Server URL = http://hsdev2:8020/VaultService
Identity = HSDEV2\ASPNET
----12/27/2005 4:05:46 PM admin--hsdev2()--SSL Disabled Login
----12/27/2005 4:06:24 PM admin--hsdev2()--SSL Disabled Logout
----12/27/2005 4:42:13 PM admin--hsdev2()--SSL Disabled Login
----12/27/2005 4:42:27 PM admin--hsdev2()--SSL Disabled Logout
Things seem to work ok, except when I exit the Admin tool the following event shows up in Win2K event log. I also included the Vault log at the end.
Any ideas?
Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date: 12/27/2005
Time: 4:42:27 PM
User: N/A
Computer: HSDEV2
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 12/27/2005 4:42:27 PM
Event time (UTC): 12/27/2005 10:42:27 PM
Event ID: c5c02ba09d0c4d8094993d0e7be3d78a
Event sequence: 28
Event occurrence: 2
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/4/Root/VaultService-1-127801947331908750
Trust level: Full
Application Virtual Path: /VaultService
Application Path: E:\WebData\Vault\
Machine name: HSDEV2
Process information:
Process ID: 3392
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: 7
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)
Custom event details:
==========================================
# SourceGear Vault Server
----12/27/2005 4:05:35 PM sgvaultsystem--()--
System Started
Version 3.1.5.3546
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = E:\Program Files\SourceGear\VaultLogs\sgvault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 4320
Active Directory Domain =
SGVault Working Directory = E:\Program Files\SourceGear\VaultLogs
SGVault Server URL = http://hsdev2:8020/VaultService
Identity = HSDEV2\ASPNET
----12/27/2005 4:05:46 PM admin--hsdev2()--SSL Disabled Login
----12/27/2005 4:06:24 PM admin--hsdev2()--SSL Disabled Logout
----12/27/2005 4:42:13 PM admin--hsdev2()--SSL Disabled Login
----12/27/2005 4:42:27 PM admin--hsdev2()--SSL Disabled Logout
client
I'm running Vault Admin on the Vault server.
The Vault client is running on my pc. It does not produce any errors on my pc, but does create the same event log entry on the Vault server when I exit.
I do have FrontPage Server Extensions installed on the default website in IIS. I've read in these forums that the Extensions cause problems, so I installed Vault on a new website. I also re-registered .Net 2.0 framework (another suggestion I found in the forums).
Could this be a problem with .Net 2.0 framework? I still have 1.1 framework on the server and could change the site to use 1.1.
The Vault client is running on my pc. It does not produce any errors on my pc, but does create the same event log entry on the Vault server when I exit.
I do have FrontPage Server Extensions installed on the default website in IIS. I've read in these forums that the Extensions cause problems, so I installed Vault on a new website. I also re-registered .Net 2.0 framework (another suggestion I found in the forums).
Could this be a problem with .Net 2.0 framework? I still have 1.1 framework on the server and could change the site to use 1.1.
Before closing this issue, you may want to thoroughly check your Vault Server log.
You have a snipet above, but is there anything related to any type of error in the current or previous log files?
You have a snipet above, but is there anything related to any type of error in the current or previous log files?
Jeff Clausius
SourceGear
SourceGear
vault log in debug mode
Nothing really shows up in the Vault log, only in the Windows event log.
The vault log in my original post was not a snippet, it was the whole log.
I changed Vault logging to debug, exited Vault Admin (4:54pm), restarted IIS (4:55pm), went back into Vault Admin (4:56pm), then exited Vault Admin (4:57). Nothing extra showed up.
Here is the new Vault log (with domain names and IP addresses removed)...
# SourceGear Vault Server
----12/27/2005 4:05:35 PM sgvaultsystem--()--
System Started
Version 3.1.5.3546
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = E:\Program Files\SourceGear\VaultLogs\sgvault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 4320
Active Directory Domain =
SGVault Working Directory = E:\Program Files\SourceGear\VaultLogs
SGVault Server URL = http://hsdev2:8020/VaultService
Identity = HSDEV2\ASPNET
----12/27/2005 4:05:46 PM admin--hsdev2()--SSL Disabled Login
----12/27/2005 4:06:24 PM admin--hsdev2()--SSL Disabled Logout
----12/27/2005 4:42:13 PM admin--hsdev2()--SSL Disabled Login
----12/27/2005 4:42:27 PM admin--hsdev2()--SSL Disabled Logout
----12/28/2005 8:38:37 AM admin--rsc3381xp()--SSL Disabled Login
----12/28/2005 8:39:23 AM admin--rsc3381xp()--SSL Disabled Logout
----12/28/2005 8:41:28 AM admin--hsdev2()--SSL Disabled Login
----12/28/2005 8:42:03 AM admin--hsdev2()--SSL Disabled Logout
----12/28/2005 8:43:27 AM admin--hsdev2()--SSL Disabled Login failed: FailInvalidPassword
----12/28/2005 8:43:40 AM admin--hsdev2()--SSL Disabled Login
----12/28/2005 8:43:56 AM admin--hsdev2()--SSL Disabled Logout
----12/28/2005 8:44:06 AM JLUTHER--rsc3381xp()--SSL Disabled Login
----12/28/2005 8:45:45 AM JLUTHER--rsc3381xp()--SSL Disabled Logout
----12/28/2005 11:16:53 AM JLUTHER--rsc3381xp()--SSL Disabled Login
----12/28/2005 11:17:21 AM JLUTHER--rsc3381xp()--SSL Disabled Logout
----12/28/2005 4:53:39 PM sgvaultsystem--()--
System Started
Version 3.1.5.3546
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = E:\Program Files\SourceGear\VaultLogs\sgvault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 4320
Active Directory Domain =
SGVault Working Directory = E:\Program Files\SourceGear\VaultLogs
SGVault Server URL = http://hsdev2:8020/VaultService
Identity = HSDEV2\ASPNET
----12/28/2005 4:53:50 PM admin--hsdev2()--SSL Disabled Login
----12/28/2005 4:54:09 PM admin--hsdev2()--SSL Disabled Logout
----12/28/2005 4:56:35 PM sgvaultsystem--()--
System Started
Version 3.1.5.3546
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = E:\Program Files\SourceGear\VaultLogs\sgvault
Log Level = Debug
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 4320
Active Directory Domain =
SGVault Working Directory = E:\Program Files\SourceGear\VaultLogs
SGVault Server URL = http://hsdev2:8020/VaultService
Identity = HSDEV2\ASPNET
----12/28/2005 4:56:46 PM admin--hsdev2()--SSL Disabled Login
----12/28/2005 4:56:46 PM admin--hsdev2()--SSL Disabled GetUserOptions returned: Success
----12/28/2005 4:56:47 PM admin--hsdev2()--SSL Disabled GetRepositories returned: Success
----12/28/2005 4:57:18 PM admin--hsdev2()--SSL Disabled Logout
The vault log in my original post was not a snippet, it was the whole log.
I changed Vault logging to debug, exited Vault Admin (4:54pm), restarted IIS (4:55pm), went back into Vault Admin (4:56pm), then exited Vault Admin (4:57). Nothing extra showed up.
Here is the new Vault log (with domain names and IP addresses removed)...
# SourceGear Vault Server
----12/27/2005 4:05:35 PM sgvaultsystem--()--
System Started
Version 3.1.5.3546
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = E:\Program Files\SourceGear\VaultLogs\sgvault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 4320
Active Directory Domain =
SGVault Working Directory = E:\Program Files\SourceGear\VaultLogs
SGVault Server URL = http://hsdev2:8020/VaultService
Identity = HSDEV2\ASPNET
----12/27/2005 4:05:46 PM admin--hsdev2()--SSL Disabled Login
----12/27/2005 4:06:24 PM admin--hsdev2()--SSL Disabled Logout
----12/27/2005 4:42:13 PM admin--hsdev2()--SSL Disabled Login
----12/27/2005 4:42:27 PM admin--hsdev2()--SSL Disabled Logout
----12/28/2005 8:38:37 AM admin--rsc3381xp()--SSL Disabled Login
----12/28/2005 8:39:23 AM admin--rsc3381xp()--SSL Disabled Logout
----12/28/2005 8:41:28 AM admin--hsdev2()--SSL Disabled Login
----12/28/2005 8:42:03 AM admin--hsdev2()--SSL Disabled Logout
----12/28/2005 8:43:27 AM admin--hsdev2()--SSL Disabled Login failed: FailInvalidPassword
----12/28/2005 8:43:40 AM admin--hsdev2()--SSL Disabled Login
----12/28/2005 8:43:56 AM admin--hsdev2()--SSL Disabled Logout
----12/28/2005 8:44:06 AM JLUTHER--rsc3381xp()--SSL Disabled Login
----12/28/2005 8:45:45 AM JLUTHER--rsc3381xp()--SSL Disabled Logout
----12/28/2005 11:16:53 AM JLUTHER--rsc3381xp()--SSL Disabled Login
----12/28/2005 11:17:21 AM JLUTHER--rsc3381xp()--SSL Disabled Logout
----12/28/2005 4:53:39 PM sgvaultsystem--()--
System Started
Version 3.1.5.3546
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = E:\Program Files\SourceGear\VaultLogs\sgvault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 4320
Active Directory Domain =
SGVault Working Directory = E:\Program Files\SourceGear\VaultLogs
SGVault Server URL = http://hsdev2:8020/VaultService
Identity = HSDEV2\ASPNET
----12/28/2005 4:53:50 PM admin--hsdev2()--SSL Disabled Login
----12/28/2005 4:54:09 PM admin--hsdev2()--SSL Disabled Logout
----12/28/2005 4:56:35 PM sgvaultsystem--()--
System Started
Version 3.1.5.3546
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = E:\Program Files\SourceGear\VaultLogs\sgvault
Log Level = Debug
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 4320
Active Directory Domain =
SGVault Working Directory = E:\Program Files\SourceGear\VaultLogs
SGVault Server URL = http://hsdev2:8020/VaultService
Identity = HSDEV2\ASPNET
----12/28/2005 4:56:46 PM admin--hsdev2()--SSL Disabled Login
----12/28/2005 4:56:46 PM admin--hsdev2()--SSL Disabled GetUserOptions returned: Success
----12/28/2005 4:56:47 PM admin--hsdev2()--SSL Disabled GetRepositories returned: Success
----12/28/2005 4:57:18 PM admin--hsdev2()--SSL Disabled Logout
Are you by chance restarting IIS quite often? If not, that is what I was afraid the Windows Event messages may mean the Vault Service is restarting.
Have you tried uninstalling (keeping the database), and reinstalling the Vault Server? - Keep the database on installation as well.
Something is not quite right here.
Have you tried uninstalling (keeping the database), and reinstalling the Vault Server? - Keep the database on installation as well.
Something is not quite right here.
Jeff Clausius
SourceGear
SourceGear
We've did some more digging here.
The Event Viewer messages is not harmful. It is related to a clean up thread, but as long as client connection is calling the Logout() method there is nothing to worry about. This message will go away in Vault 4.0
I'm more concerned about the number of restarts. Something else is causing the Vault server to restart. The number of occurrences should be reduced for optimal server performance.
The Event Viewer messages is not harmful. It is related to a clean up thread, but as long as client connection is calling the Logout() method there is nothing to worry about. This message will go away in Vault 4.0
I'm more concerned about the number of restarts. Something else is causing the Vault server to restart. The number of occurrences should be reduced for optimal server performance.
Jeff Clausius
SourceGear
SourceGear
restarting, reinstalling
I may have restarted the website, but don't remember.
I will attempt a reinstall.
I don't have anything in the database so I will go ahead and get rid of it also.
I will attempt a reinstall.
I don't have anything in the database so I will go ahead and get rid of it also.
vault 3.16
I uninstalled Vault Server 3.15 and installed 3.16.
I still get the warning in the Event Log when I exit Vault Admin Tool.
The Vault log and the event warning are below.
In referrence to the previous log I posted: I did restart IIS, because I changed the location of the log folder from C:\winnt\temp. That's why it shows Vault restarting.
Thanks for your input!
==============================================
# SourceGear Vault Server
----1/6/2006 11:30:37 AM sgvaultsystem--()--
System Started
Version 3.1.6.3658
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = C:\WINNT\Temp\sgvault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 4320
Active Directory Domain =
SGVault Working Directory = C:\WINNT\Temp
SGVault Server URL = http://hsdev2.cou.goRacine.org:8020/VaultService
Identity = HSDEV2\ASPNET
----1/6/2006 11:30:54 AM admin--hsdev2()--SSL Disabled Login
----1/6/2006 11:31:41 AM admin--hsdev2()--SSL Disabled Logout
==============================================
Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date: 1/6/2006
Time: 11:31:41 AM
User: N/A
Computer: HSDEV2
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 1/6/2006 11:31:41 AM
Event time (UTC): 1/6/2006 5:31:41 PM
Event ID: 123791c86d424d12a9746d4c238d2ae0
Event sequence: 20
Event occurrence: 1
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/4/Root/VaultService-1-127810422172578125
Trust level: Full
Application Virtual Path: /VaultService
Application Path: E:\WebData\Vault\
Machine name: HSDEV2
Process information:
Process ID: 3212
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: 6
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)
Custom event details:
I still get the warning in the Event Log when I exit Vault Admin Tool.
The Vault log and the event warning are below.
In referrence to the previous log I posted: I did restart IIS, because I changed the location of the log folder from C:\winnt\temp. That's why it shows Vault restarting.
Thanks for your input!
==============================================
# SourceGear Vault Server
----1/6/2006 11:30:37 AM sgvaultsystem--()--
System Started
Version 3.1.6.3658
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = C:\WINNT\Temp\sgvault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 4320
Active Directory Domain =
SGVault Working Directory = C:\WINNT\Temp
SGVault Server URL = http://hsdev2.cou.goRacine.org:8020/VaultService
Identity = HSDEV2\ASPNET
----1/6/2006 11:30:54 AM admin--hsdev2()--SSL Disabled Login
----1/6/2006 11:31:41 AM admin--hsdev2()--SSL Disabled Logout
==============================================
Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date: 1/6/2006
Time: 11:31:41 AM
User: N/A
Computer: HSDEV2
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 1/6/2006 11:31:41 AM
Event time (UTC): 1/6/2006 5:31:41 PM
Event ID: 123791c86d424d12a9746d4c238d2ae0
Event sequence: 20
Event occurrence: 1
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/4/Root/VaultService-1-127810422172578125
Trust level: Full
Application Virtual Path: /VaultService
Application Path: E:\WebData\Vault\
Machine name: HSDEV2
Process information:
Process ID: 3212
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: 6
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)
Custom event details:
As long as you do not have any unexplained restarts that is fine.
If the Event Viewer errors are bugging you, you can disable Web Event health monitoring by modifying the Vault server's web.config's <system.web> elements.
See Security Practices: ASP.NET 2.0 Security Practices at a Glance for more information on modifying Vault's web.config. A word of caution - make a backup of web.config before making any changes in case something goes awry.
If the Event Viewer errors are bugging you, you can disable Web Event health monitoring by modifying the Vault server's web.config's <system.web> elements.
See Security Practices: ASP.NET 2.0 Security Practices at a Glance for more information on modifying Vault's web.config. A word of caution - make a backup of web.config before making any changes in case something goes awry.
Jeff Clausius
SourceGear
SourceGear
User status in Admin tool remains logged in
I think this might be related, so I'm hoping it might help trigger an idea.
The user status in the Admin Tool remains "Logged In" even though I'm logged out of the client and the sgvault.log shows that I'm logged out. I created a performance counter to view the "Current Anonymous Users" and "Current Connections" on the Vault website and it shows there are zero users connected.
It seems that whatever is causing the "Object reference..." error in ASP.NET is also preventing Vault Client from cleanly disconnecting from the server.
SGVAULT.LOG snippet:
----1/12/2006 8:31:08 AM JLUTHER--rsc3381xp()--SSL Disabled Login
----1/12/2006 8:31:16 AM JLUTHER--rsc3381xp()--SSL Disabled Logout
The user status in the Admin Tool remains "Logged In" even though I'm logged out of the client and the sgvault.log shows that I'm logged out. I created a performance counter to view the "Current Anonymous Users" and "Current Connections" on the Vault website and it shows there are zero users connected.
It seems that whatever is causing the "Object reference..." error in ASP.NET is also preventing Vault Client from cleanly disconnecting from the server.
SGVAULT.LOG snippet:
----1/12/2006 8:31:08 AM JLUTHER--rsc3381xp()--SSL Disabled Login
----1/12/2006 8:31:16 AM JLUTHER--rsc3381xp()--SSL Disabled Logout