runtime error trying to access webservice

owoade · August 16th, 2007, 11:05 PM

I get a runtime error trying to browse to a webservice i uploaded to the server. the webservice runs well on the local test machine. the error message is reproduced below:

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".

<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.

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

I did modify the web.config file as suggested, i.e setting customerrors mode to "off" but the error remains unchanged. What could be causing this and pls help suggest remedy. what does the authentication tag do - presently set to "windows". thank you

ayo

planoie · August 20th, 2007, 02:54 PM

Auth mode of windows expects the browser to provide windows credentials that are meaningful to the web server. Generally this is completely useless for a web app because the app is for the internet. However, this doesn't sound like it's causing the problem. If it is a security issue you should be prompted for a login (the browser prompt, not something in a page) or you would get a message on the page that access is not permitted.

-Peter