Server Error in '/PrecompiledWeb2' 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: Unrecognized configuration section 'connectionStrings'

Source Error:

Line 10: <configuration>
Line 11: <appSettings/>
Line 12: <connectionStrings/>
Line 13: <system.web>
Line 14: <!--

Source File: F:\9july\project\Solution\PrecompiledWeb1\WebUI\web.config Line: 12
Version Information: Microsoft .NET Framework Version:1.1.4322.2032; ASP.NET Version:1.1.4322.2032


<?xml version="1.0"?>
Note: As an alternative to hand editing this file you can use the
web admin tool to configure settings for your application. Use
the Website->Asp.Net Configuration option in Visual Studio.
A full list of settings and comments can be found in
machine.config.comments usually located in
Set compilation debug="true" to insert debugging
symbols into the compiled page. Because this
affects performance, set this value to true only
during development.
<compilation debug="true"/>
The <authentication> section enables configuration
of the security authentication mode used by
ASP.NET to identify an incoming user.
<authentication mode="Windows"/>
The <customErrors> section enables configuration
of what to do if/when an unhandled error occurs
during the execution of a request. Specifically,
it enables developers to configure html error pages
to be displayed in place of a error stack trace.

<customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
<error statusCode="403" redirect="NoAccess.htm" />
<error statusCode="404" redirect="FileNotFound.htm" />

7 Years
Discussion Span
Last Post by Lusiphur

I'm going to go out on a limb here and assume that the reason you've posted this is because you're looking for a solution for the error at the top...

It's pretty explicitly telling you the problem is with the following line:
>>Line 12: <connectionStrings/>

That being said, as there are no connection strings defined in your web.config file, you could easily delete that line entirely with no effect on your project (other than eliminating the error).

Generally, any section of a web.config file that serves no purpose doesn't even need to exist in the file. In your case that would include:
>> <appSettings/>
>> <connectionStrings/>

Hope this helps :) Please remember to mark this thread solved once the issue is resolved.

This question has already been answered. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.