B
B Wagner
This message was posted (not by me) in July and never saw any
responses...I'm having the same exact issue and then some...first the
original post (can also be seen here:
http://groups.google.com/[email protected]&rnum=15)
-----------------------------------------------------------------------
Ever since I started working with .NET Framework 1.1, everytime I
start debugging my ASP.NET project when the browser launches I get the
following error. However, when I refresh, this immediately goes away
and doesn't come back until the next time I restart the app. Also,
another developer on another project gets the same behavior. I have
also noticed this in deployment - always happens the first time any
page in the project is opened after deployment and then never again.
Of course, there are NO errors in the web.config file, this is a
misleading error message. But why does this occur and how can we get
rid of it forever?
Server Error in '/tips' Application.
Configuration Error
Description: An error occurred during the processing of a
configuration file required to service this request. Please review the
specific error details below and modify your configuration file
appropriately.
Parser Error Message: Exception in configuration section handler.
Source Error:
Line 24:
Line 25: <!-- if you get a configuration exception then make sure
the folder exists for the logs -->
Line 26: <system.diagnostics>
Line 27: <switches>
Line 28: <add name="PageEntryAndExit" value="4" /> <!--
Verbose=4 -->
Source File: C:\Inetpub\wwwroot\tips\web.config Line: 26
-----------------------------------------------------------------------
Now, I also have an additional problem, and I'm unsure if it's
related, but I should mention it. My application is set up with a
splash screen and a redirect (via Javascript) to a login page.
Regardless of receiving the above error, my login page takes an
abnormally long time to load and is finally displayed as having no
source, not one line, not one HTML tag.
CONFIG:
WinXP Pro
..NET Framework 1.1
VS.NET 2003 (oooh, is that it?)
TIA for any help. I've tried many of the standard solutions, to no
avail.
BW
responses...I'm having the same exact issue and then some...first the
original post (can also be seen here:
http://groups.google.com/[email protected]&rnum=15)
-----------------------------------------------------------------------
Ever since I started working with .NET Framework 1.1, everytime I
start debugging my ASP.NET project when the browser launches I get the
following error. However, when I refresh, this immediately goes away
and doesn't come back until the next time I restart the app. Also,
another developer on another project gets the same behavior. I have
also noticed this in deployment - always happens the first time any
page in the project is opened after deployment and then never again.
Of course, there are NO errors in the web.config file, this is a
misleading error message. But why does this occur and how can we get
rid of it forever?
Server Error in '/tips' Application.
Configuration Error
Description: An error occurred during the processing of a
configuration file required to service this request. Please review the
specific error details below and modify your configuration file
appropriately.
Parser Error Message: Exception in configuration section handler.
Source Error:
Line 24:
Line 25: <!-- if you get a configuration exception then make sure
the folder exists for the logs -->
Line 26: <system.diagnostics>
Line 27: <switches>
Line 28: <add name="PageEntryAndExit" value="4" /> <!--
Verbose=4 -->
Source File: C:\Inetpub\wwwroot\tips\web.config Line: 26
-----------------------------------------------------------------------
Now, I also have an additional problem, and I'm unsure if it's
related, but I should mention it. My application is set up with a
splash screen and a redirect (via Javascript) to a login page.
Regardless of receiving the above error, my login page takes an
abnormally long time to load and is finally displayed as having no
source, not one line, not one HTML tag.
CONFIG:
WinXP Pro
..NET Framework 1.1
VS.NET 2003 (oooh, is that it?)
TIA for any help. I've tried many of the standard solutions, to no
avail.
BW