RE: IIS 6.0,ASP.NET 1.1 and confiig error



Here is the config file.
I have changed the application name from Default Application to something
else. Still not working...

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<appSettings>
<add key="CONN" value="packet size=4096;user id=test;password=;data
source=CHRISWORK;persist security info=False;initial catalog=HelpDesk"/>
<add key="SMTP" value="smtp.saix.net"></add>
<add key="ADMINEMAIL" value="admin@xxxxxxxxxxxxx"></add>
<add key="ERROREMAIL" value="chrismorton@xxxxxxxxxxxxx"></add>

</appSettings>
<system.web>

<!-- DYNAMIC DEBUG COMPILATION
Set compilation debug="true" to enable ASPX debugging. Otherwise,
setting this value to
false will improve runtime performance of this application.
Set compilation debug="true" to insert debugging symbols (.pdb
information)
into the compiled page. Because this creates a larger file that
executes
more slowly, you should set this value to true only when debugging
and to
false at all other times. For more information, refer to the
documentation about
debugging ASP.NET files.
-->
<compilation
defaultLanguage="c#"
debug="true"
/>

<!-- CUSTOM ERROR MESSAGES
Set customErrors mode="On" or "RemoteOnly" to enable custom error
messages, "Off" to disable.
Add <error> tags for each of the errors you want to handle.

"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.
-->
<customErrors
mode="Off"
/>

<!-- AUTHENTICATION
This section sets the authentication policies of the application.
Possible modes are "Windows",
"Forms", "Passport" and "None"

"None" No authentication is performed.
"Windows" IIS performs authentication (Basic, Digest, or
Integrated Windows) according to
its settings for the application. Anonymous access must be
disabled in IIS.
"Forms" You provide a custom form (Web page) for users to enter
their credentials, and then
you authenticate them in your application. A user credential
token is stored in a cookie.
"Passport" Authentication is performed via a centralized
authentication service provided
by Microsoft that offers a single logon and core profile services
for member sites.
-->
<authentication mode="Windows" />

<!-- AUTHORIZATION
This section sets the authorization policies of the application.
You can allow or deny access
to application resources by user or role. Wildcards: "*" mean
everyone, "?" means anonymous
(unauthenticated) users.
-->

<authorization>
<allow users="*" /> <!-- Allow all users -->
<!-- <allow users="[comma separated list of users]"
roles="[comma separated list of roles]"/>
<deny users="[comma separated list of users]"
roles="[comma separated list of roles]"/>
-->
</authorization>

<!-- APPLICATION-LEVEL TRACE LOGGING
Application-level tracing enables trace log output for every page
within an application.
Set trace enabled="true" to enable application trace logging. If
pageOutput="true", the
trace information will be displayed at the bottom of each page.
Otherwise, you can view the
application trace log by browsing the "trace.axd" page from your
web application
root.
-->
<trace
enabled="false"
requestLimit="10"
pageOutput="false"
traceMode="SortByTime"
localOnly="true"
/>

<!-- SESSION STATE SETTINGS
By default ASP.NET uses cookies to identify which requests belong
to a particular session.
If cookies are not available, a session can be tracked by adding a
session identifier to the URL.
To disable cookies, set sessionState cookieless="true".
-->
<sessionState
mode="InProc"
stateConnectionString="tcpip=127.0.0.1:42424"
sqlConnectionString="data source=127.0.0.1;Trusted_Connection=yes"
cookieless="false"
timeout="20"
/>

<!-- GLOBALIZATION
This section sets the globalization settings of the application.
-->
<globalization
requestEncoding="utf-8"
responseEncoding="utf-8"
/>

</system.web>

</configuration>

--
Microsoft Application Developer


"Jagdish Yadav" wrote:

Can you post the content of your web.config file.

By the meantime just check whether in IIS, you have given an 'application
name' to your virtual directory (This may not be applicable since it is able
to server htm & asp pages)

"codrakon" wrote:

Hi

I am an ASP.NET developer and we have recently installed Windows 2003 Server
Web Edition to run our companys apps. For some reason though i cannot seem to
get ASP.NET applications to run properly.

This is the situation.

I have installed VS 2003 on the web server as it is my dev box as well, so
all the framework requirements are taken care of. I installed ASP.NET from
the windows components dialog. I can run my applications locally (on the box)
successfully with no errors....BUT when i try to access them via our intranet
or via the internet the following error is produced:

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>

now i am familiar with this error...BUT when i set the custom errors mode to
"Off" it still shows me the same error. It does not give me the error i need
to see. but anyway that is besides the point.

What i really want to know is how come i can run my asp.net apps locally
just fine but when i access over a remote pc it gives me this error?

by the way IIS serves plain .htm pages and .asp pages just fine remotely
this is only occuring with asp.net pages!

I have applied SP1, VS 2003, the latest SDK for Windows Server 2003, it gets
updates from microsoft every couple of days. I have looked for virus and
trojans etc - nothing but a clean box.

I am running software called DynDns that provides internet connectivity
interms of providing a static ip address. This is running on several of our
XP boxes successfully.

Please help me.

Thanks in Advance

Chris Morton

--
Microsoft Application Developer
.



Relevant Pages

  • Re: Outlook -> remote exchange -> always wants a password
    ... I have my server set to use Integrated Windows authentication over SSL. ... almost certainly "break" your existing users if the client setup does not ... Close out of these configuration dialogs, ...
    (microsoft.public.windows.server.sbs)
  • Cannot Access Sharepoint Central Administrator
    ... An application error occurred on the server. ... "web.config" configuration file located in the root directory of the current ... The current error page you are seeing can be replaced by a custom ... Thread account name: NT AUTHORITY\NETWORK SERVICE Is impersonating: ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Help on SMTP setting, loosing my hairs
    ... to email server and I type in the mail server as: ... Thats it for the configuration of CEICW that I have done ... which is a different account as my ISP which give the outside line. ... you authentication. ...
    (microsoft.public.windows.server.sbs)
  • Re: Companyweb unable to access
    ... An application error occurred on the server. ... "web.config" configuration file located in the root directory of the ... install right out of the box on a virgin HDD, ...
    (microsoft.public.windows.server.sbs)
  • Cannot open .aspx page
    ... Server Error in '/' Application. ... error settings for this application prevent the details of the application ... configuration file located in the root directory of the current web ... The current error page you are seeing can be replaced by a custom ...
    (microsoft.public.dotnet.general)

Loading