Re: Remote Debugging ASP.net 2.0 Web Service (no symbols loaded?)

"Ben Bodien" <ben.bodien@xxxxxxxxx> wrote in message news:1183969392.992947.211660@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Jul 6, 5:46 pm, "John Saunders [MVP]" <john.saunders at
trizetto.com> wrote:
....
>> Try access your web service first, to make sure the service has been
>> loaded
>> into an AppDomain. Either use your client program or else access it
>> through
>> a browser.
>> --
>> John Saunders [MVP]

> Hi John,

> Thanks for the response. I have managed to call the webservice's test
> interface via a browser, addressed as > http://<server/path>/<service>.asmx

> I can invoke my webmethods via this interface, and I get responses
> (either return values or one line error messages - typically exception
> types). What I'd really like to do though is make use of Remote
> Debugging to step into the code and see where these errors are coming
> from, as I have some fairly deep call stacks, and the errors I get via
> this interface are somewhat ambiguous, and don't include call stack
> information.

> Regards,

> --
> Ben

Ben, first try browser, then breakpoints.

--
John Saunders [MVP]

John,

I'm not sure I follow you, so I'll explain what I've done so far.

Ben, Sorry about that,

I actually replied to this four times, and Outlook Express crashed on me four times. It seemed to be dependant on how long I took to enter the reply, so I entered that last one _real fast_ and then sent it. That's why it was so terse.

I have opened the application itself in a browser, but unhandled
exceptions are thrown somewhere during the initial stages of
execution. Javascript AJAX calls to server side web methods are used
extensively, and unfortunately I don't seem to get any exception
information in the HTTP response from these web methods, just an HTTP
500 response; "There was an error processing the request". I've tried
exception handling in the web methods, but no exception messages are
passed back in the HTTP response.

My next step was to call the asmx files directly from a browser, and
try invoking the webmethods through the provided interface. This gave
me the exception messages, but with no call stack information.

So I've been trying to use remote debugging, I've managed to attach to
the worker process (I know it's the right one because this application
is running in its own app pool on the server, running as a unique user
for trusted connections to SQL servers, and I can see w3wp.exe running
as that user. Is this what you mean by App Domain?). The issue I have
is that I can't break execution via Visual Studio on the host, and I'm
not sure if debug symbols are being loaded correctly (nothing loaded
for App_Code.dll, which is where all my web service application code
is located). Do I need to generate a pdb for my App_Code.dll file, and
how would I do this if so?

Ben, yes, if you've got a separate app pool, and if you see w3wp starting in that pool, then you've got the code loaded. That's what I was getting at with the suggestion to use the browser first.

Unfortunately, I don't have any clues beyond this. I don't use the "web site" model, ever. I have no idea how to get symbols for App_Code.

Sorry I couldn't help,
--
John Saunders [MVP]

.

Relevant Pages

  • Re: QueryInterface for interface * failed. (Using COM Interop dll in web application)
    ... // log general exception ... The problem is when I deploy same version on test enviroment (Winwods ... untill next closeing of the browser. ... I can use com obj only first time when I ...
    (microsoft.public.dotnet.framework.interop)
  • Re: HttpWebRequest.GetRequestStream times out
    ... When I encounter this exception, this is printed in the log: ... Stream sendStream = httpReq.GetRequestStream; ... you never read more than 1 kB of the response, ... The request timeout is set to 100 seconds, and the requests that time out ...
    (microsoft.public.dotnet.framework.performance)
  • Re: Remote Debugging ASP.net 2.0 Web Service (no symbols loaded?)
    ... John Saunders [MVP] ... (either return values or one line error messages - typically exception ... this interface are somewhat ambiguous, ... information in the HTTP response from these web methods, ...
    (microsoft.public.vsnet.debugging)
  • Re: WSE 2.0 issue with token expiry
    ... Thank you for your response. ... expiry to 10 min and we will leave it to the default. ... > the 2nd exception is that you're using a derived key token and when the ... The client obtains a SCT providing a username token as the base ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Machine Check Error.
    ... Machine Check Architecture exception. ... exception is sent by the CPU in the computer in response to a computer ... the CPU reports the Machine Check Architecture ...
    (microsoft.public.windows.server.general)