Error parsing configuration file

User-77749254 posted
  • Remove From My Forums
  • Question

  • User-77749254 posted

    Dear All,

    I have converted by VS-2003 web application to VS-2005 with SP1. When I try to debug my application it pops up an error message box stating that

    «Error parsing application configuration file at line 220. Type ‘{http://www.microsoft.com/practices/enterpriselibrary/08-31-2004/configuration}ReadOnlyConfigurationSectionData’ is not found in Schema.»

    The web.config file is as bellow:

    </appSettings>
    <enterpriselibrary.configurationSettings xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" applicationName="Application1" xmlns="http://www.microsoft.com/practices/enterpriselibrary/08-31-2004/configuration">
    <configurationSections>
    <configurationSection xsi:type="ReadOnlyConfigurationSectionData" name="dataConfiguration" encrypt="false">
    <storageProvider xsi:type="XmlFileStorageProviderData" name="XML File Storage Provider" path="dataConfiguration.config" />
    <dataTransformer xsi:type="XmlSerializerTransformerData" name="Xml Serializer Transformer">
    <includeTypes />
    </dataTransformer>
    </configurationSection>
    </configurationSections>
    <keyAlgorithmStorageProvider xsi:nil="true" />
    <includeTypes />
    </enterpriselibrary.configurationSettings>
    </configuration>
    I need your help.
     
    Kind regards,
     
     

     

Answers

  • User-2017008401 posted

    Hi Suan Ngaihte,

    Based on my research on this error message, I suggest you to move the config section in to enterpriseLibrary.config, and then add the following section in web.config:

    <appSettings>
       <add key=»entLibConfigFile»
          value=»ConfigenterpriseLibrary.config»/>
    </appSettings>

     
    You can see detailed information from the following links.

    Error parsing application configuration file» in June 2005 Application Blocks with VS 2005
    http://thetechnophile.blogspot.com/2006/03/error-parsing-application.html

    In addition, please check if the following thread is helpful to you.

    ReadOnlyConfigurationSectionData is not found in Schema
    http://community.codesmithtools.com/forums/p/2909/12035.aspx

    By the way, I recommend posting Enterprise Library related issues in the Microsoft Application Blocks forum which is more appropriate. Thanks for your cooperation.

    Microsoft Application Blocks
    http://forums.asp.net/122.aspx

    • Marked as answer by

      Thursday, October 7, 2021 12:00 AM

In the case of of a hybrid graphics system ( using either bumblebee or optimus ) the xorg.conf generated will not work.
In the case of an nvidia only system you have a monolithic xorg containing options that X will ignore or will be provided by autodetection and the useful configuration options could be provided by a smaller conf snippet.
For instance if you remove your systems /etc/Xorg.conf do you notice any difference?
Or to analyze the Xorg.conf from post #1

Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "0"
EndSection

Unneeded autodection will provide the same result

Section "Files"
EndSection

Empty section serves no purpoice.

Section "InputDevice"
#generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/pasux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4" "5"
EndSection

Section "InputDevice"
#generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection

X will skip you should see a message to that effect in the system’s xorg.log

Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Samsung s22f350"
HorizSync 30.0 - 81.0
VertRefresh 50.0 - 75.0
Option "DPMS"
Endsection

Section needed if autodetection fails ( if you switch monitors having X set to a different set of values than the monitor supports will cause issues)

Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTX 1060 3GB"
EndSection

Unneeded in a system with only a single GPU

Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaulttDepth 24
Option "Stereo" "0"
Option "nvidiaXineramaInfoOrder" "DFP-1"
Option "metamodes" "720x480 +0+0"
Option "SLI" "Off"
Option "MultiGPU" "Off"
Option "BaseMosaic" "Off"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Screen"

Some of section needed if autodetection fails.

Symptoms

Upon trying to startup JIRA, your browser shows a 404 error.

The following appears in the tomcat server logs:

2012-12-28 09:54:47 Commons Daemon procrun stdout initialized2012-12-28 09:55:10,636 main INFO      [jira.config.database.SystemTenantDatabaseConfigurationLoader] Reading database configuration from C:Program FilesAtlassianApplication DataJIRAdbconfig.xml
2012-12-28 09:55:11,948 main ERROR      [atlassian.jira.startup.LauncherContextListener] Unable to start JIRA.
java.lang.RuntimeException: Error parsing database configuration file.
	at com.atlassian.jira.config.database.AbstractJiraHomeDatabaseConfigurationLoader.loadDatabaseConfiguration(AbstractJiraHomeDatabaseConfigurationLoader.java:61)
	at com.atlassian.jira.startup.SystemTenantProvider.getSystemDatabaseConfig(SystemTenantProvider.java:52)
	at com.atlassian.jira.startup.SystemTenantProvider.getSystemTenant(SystemTenantProvider.java:36)
	at com.atlassian.multitenant.MultiTenantContext.getSystemTenant(MultiTenantContext.java:473)
	at com.atlassian.multitenant.MultiTenantContext.defaultInit(MultiTenantContext.java:112)
	at com.atlassian.jira.startup.LauncherContextListener.initMultiTenantSystem(LauncherContextListener.java:129)
	at com.atlassian.jira.startup.LauncherContextListener.contextInitialized(LauncherContextListener.java:59)
	at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4205)
	at org.apache.catalina.core.StandardContext.start(StandardContext.java:4704)
	at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
	at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
	at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
	at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
	at org.apache.catalina.core.StandardService.start(StandardService.java:525)
	at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
	at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
	at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
Caused by: org.dom4j.DocumentException: Error on line 1 of document  : Content is not allowed in prolog. Nested exception: Content is not allowed in prolog.
	at org.dom4j.io.SAXReader.read(SAXReader.java:355)
	at org.dom4j.io.SAXReader.read(SAXReader.java:271)
	at com.atlassian.jira.config.database.AbstractJiraHomeDatabaseConfigurationLoader.loadDatabaseConfiguration(AbstractJiraHomeDatabaseConfigurationLoader.java:56)
	... 21 more

Cause

JIRA is unable to properly read/parse the database configuration file.  This is either due to file corruption or modification to the file.

Resolution

  • Shutdown JIRA
  • Navigate to the location of the database configuration (dbconfig.xml)
    • In the above stacktrace, we see the path as C:Program FilesAtlassianApplication DataJIRAdbconfig.xml
  • Open the file within a text editor and check for any odd characters
    • Sample of a proper file can be found here:
      • Connecting JIRA to a Database
      • Follow the link to the appropriate database

Last modified on Mar 30, 2016

Related content

  • No related content found

Понравилась статья? Поделить с друзьями:
  • Error parsing bundle asset no such file
  • Error parsererror 200
  • Error log empty
  • Error log apache2 debian
  • Error log apache где находится