Here is the full event log message. Again, the web service is on a
different machine than where our Intranet is so I don't know why its
trying to get the js file from the IntranetComputer when it is located
on another machine. The event log errors do not seem to follow a
pattern for users or time when it happens as far as I can tell.
Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date: 9/4/2007
Time: 7:41:47 AM
User: N/A
Computer: IntranetComputer
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 9/4/2007 7:41:47 AM
Event time (UTC): 9/4/2007 11:41:47 AM
Event ID: fd38e51df3dd4d0b8c30c2e24f3f2f07
Event sequence: 969
Event occurrence: 1
Event detail code: 0
Application information:
Application domain: xxxx
Trust level: Full
Application Virtual Path: /
Application Path: xxxx
Machine name: IntranetComputer
Process information:
Process ID: 3452
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
Exception type: InvalidOperationException
Exception message: No web service found at: /MyWebService.asmx.
Request information:
Request URL:
http://IntranetComputer/MyWebService.asmx/js
Request path: /MyWebService.asmx/js
User host address: xxxx
User: xxxx
Is authenticated: True
Authentication Type: Negotiate
Thread account name: NT AUTHORITY\NETWORK SERVICE
Thread information:
Thread ID: 6
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace: at
System.Web.Script.Services.WebServiceData.GetWebSe rviceData(HttpContext
context, String virtualPath, Boolean failIfNoData, Boolean
pageMethods)
at
System.Web.Script.Services.WebServiceClientProxyGe nerator.GetClientProxyScript(HttpContext
context)
at
System.Web.Script.Services.RestClientProxyHandler. ProcessRequest(HttpContext
context)
at
System.Web.Script.Services.ScriptHandlerFactory.Ha ndlerWrapper.ProcessRequest(HttpContext
context)
at
System.Web.HttpApplication.CallHandlerExecutionSte p.System.Web.HttpApplication.IExecutionStep.Execut e()
at System.Web.HttpApplication.ExecuteStep(IExecutionS tep step,
Boolean& completedSynchronously)