Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

ASP.Net errors in Application log

Created: 28 Jun 2010 | 6 comments
biosphere's picture

Hi all,

Seeing some of these lately:

-----------------------------------------------------------------------------------------------------------------------------------------------------------------

Event Type: Warning

Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event 
Event ID: 1309
Date: 28.06.2010
Time: 11:30:07
User: N/A
Computer: xxxxxxxxxxxx
Description:
Event code: 3005 
Event message: An unhandled exception has occurred. 
Event time: 28.06.2010 11:30:07 
Event time (UTC): 28.06.2010 09:30:07 
Event ID: 69a7c39aa5564457a3b96ff7fd6cbc74 
Event sequence: 5148 
Event occurrence: 9 
Event detail code: 0 
 
Application information: 
    Application domain: /LM/W3SVC/1/ROOT/EnterpriseVault-1-129220951480346144 
    Trust level: Full 
    Application Virtual Path: /EnterpriseVault 
    Application Path: C:\Program Files\Enterprise Vault\webapp\ 
    Machine name: xxxxxxxxxxxx 
 
Process information: 
    Process ID: 264 
    Process name: w3wp.exe 
    Account name: NT AUTHORITY\SYSTEM 
 
Exception information: 
    Exception type: ArgumentOutOfRangeException 
    Exception message: Specified argument was out of the range of valid values.
Parameter name: value 
 
Request information: 
    Request URL: http://xxx.xxx.xxx/enterprisevault/GetIncrSlotWithServer.aspx?x=evoutlookext&evhost=http://xxx.xxx.xxx/EVAnon 
    Request path: /enterprisevault/GetIncrSlotWithServer.aspx 
    User host address: xx.xx.xx.xx 
    User: xxx\xxx 
    Is authenticated: True 
    Authentication Type: NTLM 
    Thread account name: NT AUTHORITY\SYSTEM 
 
Thread information: 
    Thread ID: 5 
    Thread account name: NT AUTHORITY\SYSTEM 
    Is impersonating: False 
    Stack trace:    at System.Web.HttpResponse.set_StatusDescription(String value)
   at DesktopClientCacheWeb.GetIncrSlotWithServer.Page_Load(Object sender, EventArgs args)
   at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)
   at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
   at System.Web.UI.Control.OnLoad(EventArgs e)
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
 
 
Custom event details: 
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

----------------------------------------------------------------------------------------------------------------------------------------------------------------- 

There are a few references to similar errors on the KB, but none with the same exception type and message.

From what I can see, it is related to EVAnon virtualdir somehow. I've checked the Evanon config and verified that the Evanon user is operational.

Any tips?

Discussion Filed Under:

Comments 6 CommentsJump to latest comment

Liam Finn's picture

What have you changed on your server recently?

biosphere's picture

OS/IIS/patch/whatnot-wise - nothing.

Seeing below that this may be VV/VC-related, I did disable and then re-enable VV/VC for relevant provisioning groups due to frequent event viewer messages stating that the EV cache is full no matter how high i set the threshold, prior to this error occuring.

JesusWept3's picture

what version of EV are you on? i'm pretty sure something similar to this was resolved in 8 SP4, and that is VC/VV causing that error

RahulG's picture

Try uninstalling and resintalling .net refer document http://support.microsoft.com/kb/908077
Reinstall ev binaries to recreate the IIS virtual directories
Downtime would be required to perform the above steps

RichardG's picture

What is the version of the EV client and the EV server.

biosphere's picture

Sorry for not including this in original post.

EV server is 8.0 SP4. EV client varies, but is anything from 8.0 vanilla through 8.0 SP4 (lots of mobile users that are off the SW distribution grid for long periods of time, so SW updating is tricky in general).