Unhandled Exception Has Occurred

[cs]

In the server Application event log we have multiple instances of:

I can't track down exactly what is causing this.

Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date: 05/03/2008
Time: 11:12:49
User: N/A
Computer: SERVERNAME
Description:
Event code: 3005 Event message: An unhandled exception has occurred. Event time: 05/03/2008 11:12:49 Event time (UTC): 05/03/2008 11:12:49

Event ID: a5eaa3528e024ff9ace90af434151b98 Event sequence: 787 Event occurrence: 25 Event detail code: 0 Application information: Application domain: /LM/W3SVC/1/Root/Fortress-5-128491115109648240 Trust level: Full Application Virtual Path: /Fortress Application Path: C:\Inetpub\wwwroot\Fortress\ Machine name: SERVERNAME Process information: Process ID: 5112
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: 10 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)
Custom event details:

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

[Beth]

I'm still looking into this one. I have a test server that does the same thing. Most likely just some function in .NET needs a repair.

Have you tried rerunning your 2.0 .NET installation using the repair option?

[cs]

No, sorry, are you asking me to?

[Beth]

That's a good place to start. Please do and let me know the results.

[Beth]

While I'm thinking of it, which version of Fortress are you on?

Does the time of the error correspond with closing either the browser to Fortress or the Fortress client?

[cs]

This was never resolved.

Since we upgraded to 1.1.3 yesterday we have not seen this error.

[Beth]

That's wonderful news! Thanks for the update.

[RFunke]

Sorry guys, this error is still in version 1.1.4. It happened after I had to do a restore and move the system over to a new server.

Any tips?

Thanks in advanced. - Richard

[RFunke]

I solved it myself, it was missing access rights on the network service account. I gave it dbo rights and it works fine again.

[Beth]

Thanks for the update. I'm happy to hear you are working again.

[kha]

I am having exact same problem. It worked fine before, and for all users. Now it stops working for some users while it is no problem for other users. I am doing "get latest" ok on the same folder in same repository (mine is admin account), while other developer has problem "get latest" on the same folder and repository, the download % stays at 0 forever on his Vault Client.

[Beth]

Kha, your case might be more client-side related. Have one of the users that is having the problem rename his Client Side Cache. Instructions for that is posted here: Clear Client Side Cache. I would suggest renaming instead of deleting for now.