Server Error in '/' Application.

[Guest]

Hi there,

I have a webfarm which contains several ii6 web servers. A .net web
application is running fine on all servers except one where I will
occasionally get the error below;

If I restart web service it will work again.

Both my machine.config file and the web.config files have customErrors
mode="Off" so that I can get a better indication of the error. As you can see
below the error message is ignoring my customError settings so the problem
might be deeper than the machine.config??

It does not leave any logs in the Event viewer.

I have not posted any code as this is definately NOT a code issue otherwise
the error would appear on the other webservers in the farm. My question is
why is it returning this generic message when i have explicitly set
customError messages to Off.

Any help in troubleshooting this appreciated.

P.S Looking at NTFILEMON it comes up with a TOO MANY COMMANDS statement that
may be something to do with it. I do not know what TOO MANY COMMANDS relates
to in NTFILEMON.

Happens on 10.0.0.10, spasmodically. Affected
http://electus.vividcluster.global.net.au/admin/index.aspx

Server Error in '/' Application.
--------------------------------------------------------------------------------

Runtime Error
Description: An application error occurred on the server. The current custom
error settings for this application prevent the details of the application
error from being viewed remotely (for security reasons). It could, however,
be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable
on remote machines, please create a <customErrors> tag within a "web.config"
configuration file located in the root directory of the current web
application. This <customErrors> tag should then have its "mode" attribute
set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>



Notes: The current error page you are seeing can be replaced by a custom
error page by modifying the "defaultRedirect" attribute of the application's
<customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>

 

[Morten Wennevik]

Hi Matt,

As the error page says, the real error message can only be seen using a web browser on the server.
I don't remember. It's not really a generic error message, but a secure error message not revealing the underlying code to the anonymous user.

There is a way to access the error message using a custom url and header or something, but I'm not sure how to do it.

 

[Morten Wennevik]

Disregard my previous message. I was thinking of trace logs.

I'm not sure why you don't get the full error message, but there may be other configuration files that overrides the web.config you changed.

 

[Guest]

Hi Morten,

thank you for your response.

As the error page says, the real error message can only be seen using a web browser on the server.

this is not the case as I have viewed the page from a browser directly on
the webserver and received the same error message.
There is something wrong with the .net configuration or something on this
server. If I restart the www service it resolves the problem.