RE: Detailed ASP.Net info not displaying in browser

Sure Kevin.
Both PC's are using the same web config...

<?xml version="1.0" encoding="utf-8"?>
<!-- Note 1 - This file will need to be availalbe to operation staff,
support staff, & VOSE team for modification in all environments
Note 2 - Formatters must exists in %windir%\system32 folder -->
<configuration>
<configSections>
<section name="eventFormatterSettings"
type="Microsoft.ApplicationBlocks.Logging.EventSinks.FormatterConfigHandler,
Microsoft.ApplicationBlocks.Logging.EventSinks, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=da59d79eb5fd8f1a"/>
</configSections>

<eventFormatterSettings>
<!-- Formatters referred to by EnterpriseInstrumentation are listed here
They must exists in %windir%\system32 folder -->
<formatterInfo name="logSinkXslt"
type="Microsoft.ApplicationBlocks.Logging.EventSinks.XsltEventFormatter,
Microsoft.ApplicationBlocks.Logging.EventSinks, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=da59d79eb5fd8f1a"
fullyQualifiedDefaultXsltPath="eventlogtransform.xslt"/>
<formatterInfo name="basiclogSinkXslt"
type="Microsoft.ApplicationBlocks.Logging.EventSinks.XsltEventFormatter,
Microsoft.ApplicationBlocks.Logging.EventSinks, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=da59d79eb5fd8f1a"
fullyQualifiedDefaultXsltPath="eventlogtransform.xslt"/>
<formatterInfo name="sqlSinkXslt"
type="Microsoft.ApplicationBlocks.Logging.EventSinks.XsltEventFormatter,
Microsoft.ApplicationBlocks.Logging.EventSinks, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=da59d79eb5fd8f1a"
fullyQualifiedDefaultXsltPath="eventsqltransform.xslt"/>
</eventFormatterSettings>

<appSettings>
<!-- applicationLogLevel is used to determine if event is logged
The event sink in question (ie, event log, or sqlsink) compares the
eventPublishLogLevel
with the applicationLogLevel. If eventPublishLogLevel is less than or
equal to
applicationLogLevel, the event is logged. Otherwise it is not. To turn
off all logging
for the application, the applicationLogLevel must be set to none. To
turn on all logging,
the applicationLogLevel must be set to debug.
Typically, for production the applicationLogLevel will be set to error.
In development, it will be set to debug.
For GUI & WebServices projects, when the web.config is changed, the change
takes place immediately. For all the rest, the windows service needs
refreshed
in order for the change to be picked up-->
<add key="applicationLogLevel" value="5"/> <!--(possible values are
none,always,error,warning,informational,debug)-->
<add key="instrumentationConfigFile"
value="..\..\EnterpriseInstrumentation.config"/>
<add key="Defaultconnstring" value="data source=113.130.192.177;
database=VOSE_H;user id=voseapp;password=voseapp"/>
<add key="SACCompaniesToProcess" value="S C A N M H "/>
<add key="TPACompaniesToProcess" value="F K I L G"/>
<add key="VOSE.WebServices.RemoteWebServices.WebServices"
value="http://localhost/appl02/WebServices.asmx"/>
<add key="VOSE.WebServices.RemoteEsales.ESales"
value="http://localhost/appl02/Esales.asmx"/>
<add key="VOSE.WebServices.RemoteServiceOrders.ServiceOrders"
value="http://localhost/appl02/ServiceOrders.asmx"/>
<add key="VOSE.WebServices.RemoteSPIDER.SPIDER"
value="http://localhost/appl02/SPIDER.asmx"/>
<add key="VOSE.WebServices.RemoteTPV.TPV"
value="http://localhost/appl02/TPV.asmx"/>
<add key="VOSE.WebServices.RemoteCreditStatus.CreditStatus"
value="http://localhost/appl02/CreditStatus.asmx"/>
<add key="VOSE.WebServices.RemoteRedLightOrderStatus.RedLightOrderStatus"
value="http://localhost/appl02/RedLightOrderStatus.asmx"/>
</appSettings>

<system.net>
<defaultProxy>
<proxy usesystemdefault="false"/>
</defaultProxy>
<connectionManagement>
<add address="*" maxconnection="1000"/>
</connectionManagement>
</system.net>

<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"/>
-->
<sessionState mode="SQLServer"
stateConnectionString="tcpip=113.130.192.177" sqlConnectionString="data
source=113.130.192.177;user id=voseapp;password=voseapp" cookieless="false"
timeout="15"/>
<!-- GLOBALIZATION
This section sets the globalization settings of the application.
-->
<globalization requestEncoding="utf-8" responseEncoding="utf-8"/>
<webServices>
<protocols>
<add name="HttpGet"/>
<add name="HttpPost"/>
</protocols>
</webServices>

</system.web>


</configuration>



"Kevin Yu [MSFT]" wrote:

Hi Tim

Thank your for your explanation. I tried to reproduce it on my machine. But
as far as I can see, I only got the stack trace from a local IE access. The
remote IE access and Console app accesses all returned without the server
side stack trace.

I assume there are some differences between our web.config file. Could you
please post your web.config file here?

Kevin Yu
Microsoft Online Community Support
==================================================

(This posting is provided "AS IS", with no warranties, and confers no
rights.)


.

Relevant Pages

  • Re: HELP Connection error on Release mode
    ... "Off" Always display detailed ASP.NET error information. ... This section sets the authentication policies of the application. ... Set trace enabled="true" to enable application trace logging. ... <!-- SESSION STATE SETTINGS ...
    (microsoft.public.dotnet.languages.csharp)
  • Re:
    ... "Off" Always display detailed ASP.NET error information. ... This section sets the authentication policies of the application. ... Application-level tracing enables trace log output for every page ... <!-- SESSION STATE SETTINGS ...
    (microsoft.public.dotnet.framework)
  • Re: key code dll error
    ... Set compilation debug="true" to enable ASPX debugging. ... This section sets the authentication policies of the ... Set trace enabled="true" to enable application trace logging. ... belong to a particular session. ...
    (microsoft.public.dotnet.framework.aspnet)
  • very frustrated with DAAB asp.net 2v
    ... This section sets the authentication policies of the ... Set trace enabled="true" to enable application trace logging. ... belong to a particular session. ...
    (microsoft.public.vsnet.enterprise.tools)
  • Re: Authentication login screen appears on both frames of the framset
    ... This section sets the authentication policies of the application. ... This section sets the authorization policies of the application. ... Application-level tracing enables trace log output for every page ... folder / file to set ...
    (microsoft.public.dotnet.framework.aspnet)