Welcome Guest Search | Active Topics | Sign In | Register

eo_web.ashx Options
Laura
Posted: Monday, November 17, 2008 6:13:22 AM
Rank: Newbie
Groups: Member

Joined: 8/2/2007
Posts: 2
We continue to get the following errors in our applications and don't know what this is:

Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date: 11/17/2008
Time: 8:21:39 AM
User: N/A
Computer: DCLFINAPP
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 11/17/2008 8:21:39 AM
Event time (UTC): 11/17/2008 1:21:39 PM
Event ID: c35caeaf3eac4300970da418b82d9f80
Event sequence: 4
Event occurrence: 1
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/1/Root/CustomApps/eExpense-1-128714016990984101
Trust level: Full
Application Virtual Path: /CustomApps/eExpense
Application Path: E:\CustomApps\eExpense\
Machine name: DCLFINAPP

Process information:
Process ID: 5084
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE

Exception information:
Exception type: HttpException
Exception message: Virtual Url 502239ae-ff60-4a3c-bcd6-173c86da65da not registered.

Request information:
Request URL: http://dfms.dillon.ca/CustomApps/eExpense/eo_web.ashx?id=502239ae-ff60-4a3c-bcd6-173c86da65da
Request path: /CustomApps/eExpense/eo_web.ashx
User host address: 10.32.5.66
User: DILLON\32mli
Is authenticated: True
Authentication Type: Negotiate
Thread account name: NT AUTHORITY\NETWORK SERVICE

Thread information:
Thread ID: 1
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace: at EO.Web.Internal.ak.a(ct A_0)
at EO.Web.Internal.ak.a(HttpApplication A_0)
at EO.Web.Internal.ei.a(HttpContext A_0)
at EO.Web.Runtime.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)


Custom event details:

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

On eInitition:

Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date: 11/17/2008
Time: 7:35:26 AM
User: N/A
Computer: DCLFINAPP
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 11/17/2008 7:35:26 AM
Event time (UTC): 11/17/2008 12:35:26 PM
Event ID: 1c569d3b6c8b42ff804df5bc61221df0
Event sequence: 4
Event occurrence: 1
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/1/Root/CustomApps/eInitiation-1-128713989257033681
Trust level: Full
Application Virtual Path: /CustomApps/eInitiation
Application Path: E:\CustomApps\eInitiation\
Machine name: DCLFINAPP

Process information:
Process ID: 5400
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE

Exception information:
Exception type: HttpException
Exception message: Virtual Url 3aa8774e-1d5f-4693-89cc-b87f6b36d0a7 not registered.

Request information:
Request URL: http://dfms.dillon.ca/CustomApps/eInitiation/eo_web.ashx?id=3aa8774e-1d5f-4693-89cc-b87f6b36d0a7
Request path: /CustomApps/eInitiation/eo_web.ashx
User host address: 142.68.238.245
User: DILLON\50ajb
Is authenticated: True
Authentication Type: Negotiate
Thread account name: NT AUTHORITY\NETWORK SERVICE

Thread information:
Thread ID: 1
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace: at EO.Web.Internal.ak.a(ct A_0)
at EO.Web.Internal.ak.a(HttpApplication A_0)
at EO.Web.Internal.d4.a(HttpContext A_0)
at EO.Web.Runtime.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)


eo_support
Posted: Monday, November 17, 2008 6:29:38 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,088
Hi,

This is normal and you can safely ignore it. A "virtual Url xxxx not registered" with our DLL is very much the same as "404, page not found" with IIS. It usually occurs when user has a cached old version of the page. But it can happen on other situations such as crawlers.

Thanks


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.