Internal Server Error 500

  • Thread starter Thread starter Raj
  • Start date Start date
R

Raj

When I consume a web service I got Internal Server Error 500 and it is in
HTML format though I have placed try catch blocks.

As per one suggestion, How do I add ASP.NET Machine Account to an NTFS
folder running on Windows XP? I don't find any such option!!

Any help would be appreciated

Thank you

Regards
Raj
 
When check the EventLogViewer, I got these two errors:

1.

EventType clr20r3, P1 aspnet_wp.exe, P2 2.0.50727.3053, P3 4889ded7, P4
webservice1, P5 1.0.0.0, P6 4b4d6cd1, P7 13, P8 1, P9
system.stackoverflowexception, P10 NIL.

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

2.

aspnet_wp.exe (PID: 2752) stopped unexpectedly.

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

This is the runtime exception I got:

Client found response content type of 'text/html; charset=utf-8', but
expected '
text/xml'.
The request failed with the error message:
--
<?xml version="1.0" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/
DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
<head>
<title>Server Unavailable
</title>
</head>
<body>
<h1><span style="font-family:Verdana;color: #ff3300">Server
Application Un
available
</span></h1>
<p>
<span style="font-family:Verdana;">
The web application you are attempting to access on this web server
is c
urrently unavailable. Please hit the "Refresh" button in your web browser
to re
try your request.
</span></p>
<p>
<b>Administrator Note:
</b> An error message detailing the cause of this specific request failure
can b
e found in the application event log of the web server. Please review this
log
entry to discover what caused this error to occur.
</p>
</body>
</html>

--.

I have try...catch blocks placed at appropriate locations ... it never
caught StackOverflowException ... seems something else is the problem!

Any help would be appreciated

Thankyou

Regards
Raj
 
I have .net 3.5 got installed on Windows XP

I am not able to find aspnet_regiis, from where can I get it?

Thank you

Regards
Raj
 
I have .net 3.5 got installed on Windows XP

I am not able to find aspnet_regiis, from where can I get it?

Thank you

Regards
Raj
Click to expand...

3.5 adds to 2.0, so use the version in the the 2.0.50727 folder.
 
Patrice said:
Hi,

A stack overflow is in most cases caused by code that calls itself endlessly
i.e. your code calls itself and at some step there is not enough room to
keep track of where execution shoud resume. Check for this.

In such a case it is not that surprising to see the exception is not
handled, as the whole code runtime environment is messed up, keeping running
code would likely fail so I believe that for some of those critical
exceptions the code is just ended.
Click to expand...

That's correct. StackOverflowException is uncatchable. When it
happens, it is not possible for the .NET CLR to ensure that the process
is still stable, and so the whole thing is terminated.

Pete
 
Here's the error i got:
Client found response content type of 'text/html; charset=utf-8', but
expected 'text/xml'.
The request failed with the error message:
--
<?xml version="1.0" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
<head>
<title>Server Unavailable
</title>
</head>
<body>
<h1><span style="font-family:Verdana;color: #ff3300">Server
Application Unavailable
</span></h1>
<p>
<span style="font-family:Verdana;">
The web application you are attempting to access on this web server
is currently unavailable. Please hit the "Refresh" button in your web
browser to retry your request.
</span></p>
<p>
<b>Administrator Note:
</b> An error message detailing the cause of this specific request failure
can be found in the application event log of the web server. Please review
this log entry to discover what caused this error to occur.
</p>
</body>
</html>

--.

the .asmx file is still accessible!
 
Back
Top