470,602 Members | 1,423 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 470,602 developers. It's quick & easy.

Parser Error Message: Exception in configuration section handler.


Developing a new we application. Everything okay on my local WIN XP
PROFESSIONAL, IIS 5.0 running locally. The website is running smoothly.

Now, the same code I am copying over to a WINDOWS 2003 SERVER, I
created a new website, allocated port number 6000. Created a release
version on my local machine and copied the WEB project from my local to

As soon as I run website on this new server I get the following error

Server Error in '/' 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 19: </commonservices.navigationcontrol.controller>
Line 20:
Line 21: <commonservices.navigationcontrol.httphandler>
Line 22: <security
principalFactory="CommonServices.Security.Principa lFactory,
CommonServices.Security" />
Line 23: <userState
stateManager="CommonServices.StateManagement.State ManagerInstance,
CommonServices.StateManagement" />
Source File: D:\inetpub\GTTP\web.config Line: 21
Version Information: Microsoft .NET Framework Version:1.1.4322.573;
ASP.NET Version:1.1.4322.1085

When the whole website runs perfectly on a XP PROFESSIONAL machine.

What am I doing wrong here? I have spent a whole day scratching my

Any help would be appreciated, but please remember this code works just
fine on a local xp professioal machine with the IIS server runnning
locally only the problem comes when I want to host the website on
WINDOWS 2003 server running IIS 6.0.

Following is my web. config file.


<?xml version="1.0" encoding="utf-8"?>
<section name="commonservices.exceptionmanagement"
type="CommonServices.ExceptionManagement.Configura tion.ExceptionManagementSectionHandler,
CommonServices.ExceptionManagement" />
<section name="commonservices.messaging"
type="CommonServices.Messaging.Configuration.Messa gingSectionHandler,
<section name="commonservices.navigationcontrol.controller"
type="CommonServices.NavigationControl.Configurati on.ControllerSectionHandler,
<section name="commonservices.navigationcontrol.httphandler "
type="CommonServices.NavigationControl.Configurati on.ControllerHttpHandlerSectionHandler,
CommonServices.NavigationControl" />
<section name="commonservices.dataaccess"
type="CommonServices.DataAccess.Configuration.Data AccessSectionHandler,
CommonServices.DataAccess" />
<section name="commonservices.security"
type="CommonServices.Security.Configuration.Securi tySectionHandler,
CommonServices.Security" />
<section name="smartcustomcontrols"
type="SmartCustomControls.SmartCustomControlsSecti onHandler,
SmartCustomControls" />

principalFactory="CommonServices.Security.Principa lFactory,
CommonServices.Security" />
exceptionManager="CommonServices.ExceptionManageme nt.ExceptionManager,
CommonServices.ExceptionManagement" />
stateManager="CommonServices.StateManagement.State ManagerInstance,
CommonServices.StateManagement" />
<debug sendXml="false" />
<stateMachine file="StateMachine.config" />

principalFactory="CommonServices.Security.Principa lFactory,
CommonServices.Security" />
stateManager="CommonServices.StateManagement.State ManagerInstance,
CommonServices.StateManagement" />

<messageTypes default="noreader">
<messageType name="noreader"
replacer="CommonServices.Messaging.MessageReplacer ,
CommonServices.Messaging" message="CommonServices.Messaging.Message,
CommonServices.Messaging" />

<publisherGroups default="GTTP">
<publisherGroup name="GTTP">
<add key="ApplicationVersion" value="1.0" />
<add key="ApplicationName" value="GTTP" />
type="CommonServices.ExceptionManagement.DefaultPu blisher,
CommonServices.ExceptionManagement" logName="Application"
eventSource="GTTP" />
type="CommonServices.ExceptionManagement.FilePubli sher,
CommonServices.ExceptionManagement" filename="C:\GTTP.exception.log" />

errorHandler="CommonServices.DataAccess.SimpleData AccessErrorHandler,
<database connectionKey="GTTPDB" commandTimeout="0"
errorHandler="CommonServices.DataAccess.SimpleData AccessErrorHandler,
CommonServices.DataAccess" connectionString="Server=ACTYD003;Initial
Catalog=GroupTraining;User Id=<HIDDEN>;Password=<HIDDEN>;Network
Library=dbmssocn" />

<applications default="GTTP"
<application name="GTTP" directoryName="GTTP" />

type="GTTP.Common.SmartCustomControlsCustomSetting s, GTTP.Common"
jscriptSrcUrl="JavaScript/SmartCustomControls.js" />
<state type="GTTP.Common.SmartCustomControlsState, GTTP.Common" />
<toolTips type="GTTP.Common.SmartCustomControlsToolTips,
GTTP.Common" designTimeTableName="tblToolTips"
designTimeConnectionString="" />
<message type="GTTP.Common.SmartCustomControlsMessage, GTTP.Common"

<identity impersonate="true" />
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" />
Set customError mode values to control the display of
error messages to users instead of error details (including a
stack trace):

"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" />
This section sets the authentication policies of the
application. Possible modes are "Windows", "Forms",
"Passport" and "None"
<authentication mode="None" />
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
<trace enabled="false" requestLimit="10" pageOutput="false"
traceMode="SortByTime" localOnly="true" />
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=" sqlConnectionString="data
source=;user id=sa;password=" cookieless="false" timeout="20"
This section sets the globalization settings of the
<globalization requestEncoding="utf-8" responseEncoding="utf-8" />
<add verb="*" path="Controller.aspx"
type="CommonServices.NavigationControl.HttpHandler .ControllerHttpHandler,
<add name="BasicAuthenticationModule"
type="CommonServices.Security.Web.BasicAuthenticat ionHandler,CommonServices.Security"

Nov 19 '05 #1
1 2665
Okay, Solved!!!

Uninstalling the front page server extension did the trick.


Nov 19 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by helpful sql | last post: by
3 posts views Thread by Pritam Bhat | last post: by
6 posts views Thread by Josť Joye | last post: by
2 posts views Thread by Peter D. Dunlap | last post: by
reply views Thread by psilu | last post: by
2 posts views Thread by Jim Duffie | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.