csla 3 Problem getting ProjectTracker running - ConfigurationErrorsException occurredcsla 3 Problem getting ProjectTracker running - ConfigurationErrorsException occurred
Old forum URL: forums.lhotka.net/forums/t/3324.aspx
Jimbo posted on Friday, August 03, 2007
The following exception occurs in csla
System.Configuration.ConfigurationErrorsException occurred
BareMessage="Configuration system failed to initialize"
Line=0
Message="Configuration system failed to initialize"
Source="System.Configuration"
StackTrace:
at System.Configuration.ClientConfigurationSystem.EnsureInit(String configKey)
at
System.Configuration.ClientConfigurationSystem.System.Configuration.Internal.IInternalConfigSystem.GetSection(String
sectionName)
at System.Configuration.ConfigurationManager.GetSection(String sectionName)
at System.Configuration.ConfigurationManager.get_AppSettings()
at
Csla.ApplicationContext.get_AuthenticationType() in
D:\Working\Download\cslavb-3.0.2-070727\cslavb\Csla\DataPortal\ApplicationContext.vb:line
268
.......................
Running in Debug mode
ProjectTracker is configured to use remoting with csla authentication.
NET20 directive is applied to both csla and also the ProjectTracker projects.
.NET 3 assembly references are removed in Web.Config
To avoid other annoyances that prevent compilation, the following
unneeded projects are removed from the ProjectTracker solution:
PTWeb, PTWebService, wcfHost, WebServicesHost.
Jimbo
RockfordLhotka replied on Saturday, August 04, 2007
I've never encountered that issue. System.Configuration is obviously a key part of .NET itself (starting at 2.0), so if it is failing to initialize then that seems bad...
I don't know what would cause that. Corrupt .NET install? Corrupt app.config file? File security/permissions issues?
Jimbo replied on Saturday, August 04, 2007
Rocky,
yes the PTWin app.config file is the issue.
You cant ignore the "Informational" messages in VS ....
Message 1 Could not find schema
information for the element 'system.serviceModel'.
D:\Working\csla\cslavb\ProjectTrackervb\PTWin\app.config
27 4 PTWin
Message 2 Could not find schema
information for the element 'client'.
D:\Working\csla\cslavb\ProjectTrackervb\PTWin\app.config
29 6 PTWin
Message 3 Could not find schema
information for the element 'endpoint'.
D:\Working\csla\cslavb\ProjectTrackervb\PTWin\app.config
30 8 PTWin
Message 4 Could not find schema
information for the attribute 'name'.
D:\Working\csla\cslavb\ProjectTrackervb\PTWin\app.config
30 17 PTWin
Message 5 Could not find schema
information for the attribute 'address'.
D:\Working\csla\cslavb\ProjectTrackervb\PTWin\app.config
31 17 PTWin
Message 6 Could not find schema
information for the attribute 'binding'.
D:\Working\csla\cslavb\ProjectTrackervb\PTWin\app.config
32 17 PTWin
Message 7 Could not find schema
information for the attribute 'contract'.
D:\Working\csla\cslavb\ProjectTrackervb\PTWin\app.config
33 17 PTWin
remming out this tag solves the problem
<!--<system.serviceModel>
<client>
<endpoint name="WcfDataPortal"
address="http://localhost:4216/WcfHost/WcfPortal.svc"
binding="wsHttpBinding"
contract="Csla.Server.Hosts.IWcfPortal" />
</client>
</system.serviceModel>-->
Maybe there needs to be a note
Thanks
Jimbo
Copyright (c) Marimer LLC