Server Error in '/' Application.

  • Thread starter Thread starter Joshua Flanagan
  • Start date Start date
J

Joshua Flanagan

I usually get this error if I haven't set up the folder as a vroot in the
IIS Manager yet.
 
Do you have your virtual directory set up correctly and mapped to the
correct dir in IIS?
Is your assembly in a bin folder in the application root? Have you built
your assembly? Is it referencing a start up page? Are your application pools
running? Is IIS running? Answering one of those questions will solve your
problem
 
what do you mean set up the folder as a vroot in IIS manager? The folder was
created by IIS manager when I created a new web application in VS.NET.
And VS.NET will create a new user called ASPNET automatically.
Even I add permission to ASPNET for that application, still not working.

I don't know if the error is IIS permission problem, or SQL permission
problem?
 
what do you mean set up the folder as a vroot in IIS manager? The folder was
created by IIS manager when I created a new web application in VS.NET.
And VS.NET will create a new user called ASPNET automatically.
Even I add permission to ASPNET for that application, still not working.

I don't know if the error is IIS permission problem, or SQL permission
problem?
 
I have no idea what this run-time error about.

There was a thread on this a day or two ago, but I don't remember the
solution.

(i) Is the problem on your development or live hosting platform?

(ii) If the latter, are you sure you uploaded the dll containing all the
compiled code-behind code (a basic question I know, but sometimes worth
checking)

HTH

Lauchlan M
 
I have no idea what this run-time error about. Any ideas? I already change
the web.config file for the attribute <customErrors mode="Off"/> but still
not work.


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>
 
Back
Top