Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

it works locally but not remotely

Status
Not open for further replies.

davikokar

Technical User
May 13, 2004
523
IT
Hallo,

my application run completely properly on my local server but as soon as I upload the files to the remote server a get an 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".

I did changed the web.config but I get the same error. Do you know what it could be?

Here is the web.config I'm using:

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

<configuration>
  <system.web>
    <compilation defaultLanguage="visual basic" debug="true" />
    <customErrors mode="Off" />
    <authentication mode="Forms">
      <forms loginUrl="myself_blog.aspx" timeout="30"></forms>
    </authentication>
    <authorization>
      <allow users="?" />
    </authorization>
    <trace enabled="false" requestLimit="10" pageOutput="false" traceMode="SortByTime" localOnly="true" />
    <globalization requestEncoding="utf-8" responseEncoding="utf-8" />
  </system.web>

   <location path="myself_blog_edit.aspx"> 
      <system.web>
         <authorization> 
               <deny users="?"/> 
         </authorization> 
      </system.web>
   </location>

</configuration>
 
Rather than explain it again, have a look at thread855-1044344 as this was for exactly the same problem.

--------------------------------------------------------------------------------------------------------------------------------------------

Need help finding an answer?

Try the search facility ( or read FAQ222-2244 on how to get better results.
 
mmm... I read the long thread but actually the suggestions I found there do not make any difference.
I don't have access to the server, so I cannot see the error from there.
I understand that the error i get is not a real error is only saying there is an error but cannot be displayed. I tried to change my web.config customError to "Off" and then to "On" but I always get the same thing.

The strangest thing is that in my computer everything works fine. Is there a known bug about this?

thanks
 
It's not a known "bug" in the sense that it is actually doing everything it is supposed to do. It may work on your computer but your server may have different settings/configurations.

Can you arrange to get access to the server via a remote connection? Also, when setting the custom errors note that they are case sensitive and here's what Microsoft says about them:

"On" Always display custom (friendly) messages.
"Off" Always display detailed ASP.NET error information.
"RemoteOnly" Display custom (friendly) messages only to users not running
on the local Web server. This setting is recommended for security purposes, so
that you do not display application detail information to remote clients.

--------------------------------------------------------------------------------------------------------------------------------------------

Need help finding an answer?

Try the search facility ( or read FAQ222-2244 on how to get better results.
 
Well, same problem with me, do what i say. (It worked for me; strange but...worked!!!!!)

You have this at web.config:
<?xml version="1.0" encoding="utf-8" ?>


Change it to:
<?xml version="1.1" encoding="utf-8" ?>

You should get this error (after pressing Ctrl+F5): "The version number '1.1' is invalid"


Change Again to:
<?xml version="1.0" encoding="utf-8" ?>

Save it and see that it works (on your pc).
Upload the page(s) and the bin directory to the server.

It should work...
 
I cannot access the server: it's in a webhosting service.
I did respect the case sensitive thing. I was wondering about: by changing the customerror from "On" to "Off" or to "RemoteOnly" should the error page I get be different? Or this does play a role only when browsing locally?
Because in this case at least it would mean that the server is not reading the web.config file (I get always the same errorpage)
 
You should get different error pages when browsing remotely by changing those values so if you have problems you may have to take it up directly with your hosting company.

--------------------------------------------------------------------------------------------------------------------------------------------

Need help finding an answer?

Try the search facility ( or read FAQ222-2244 on how to get better results.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top