Microsoft Webservices - Web Config Problem

Author

Web Config Problem

Savas Ates

2005-04-30, 4:01 pm

I created i simple web service.. It runs well in my local Pc..

But when i copied it into my server it fails... it is about web config
custom errors i turned it off but it still doesnt work..(<customErrors
mode="Off" /> ) Can anyone help me ?

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

------------------------------ THIS IS MY WEB.CONFIG
FILE-------------------------------------------

<?xml version="1.0" encoding="utf-8" ?>

<configuration>

<system.web>

<compilation defaultLanguage="vb" debug="true" />

<customErrors mode="Off" />

<authentication mode="None" />

<authorization>

<allow users="*" /> 

</authorization>

<trace enabled="false" requestLimit="10" pageOutput="false"
traceMode="SortByTime" localOnly="true" />

<sessionState

mode="InProc"

stateConnectionString="tcpip=127.0.0.1:42424"

sqlConnectionString="data source=127.0.0.1Trusted_Connection=yes"

cookieless="false"

timeout="20"

/>

<globalization requestEncoding="utf-8" responseEncoding="utf-8" />

</system.web>

</configuration>

GCeaser@aol.com

2005-05-06, 4:02 pm

HMMMM This looks correct. Mine shows like this:

<customErrors mode="Off" />

If you have access to the server, one possible solution is to launch
the site in a browser on the actual server. Since you would be local
at that point, the error message should display. If this does not
help, I would try restarting IIS. I have had some interesting
situations where changes were not picked up until I restarted IIS,
though this should not be necessary from what I understand. I hope
this helps.

Sponsored Links