[opencms-dev] Critical error during OpenCms initialization: Unable to read the OpenCms XML configuration.

[Claus Priisholm]

I've used log4j.logger.org.opencms=DEBUG to get a report on which of the 
  XML config files that was causing the problem.

Maybe you don't need it as Michael explained, though I don't see the 
name of the actual XML file causing the problem in his example. The SAX 
parse exception may give you sufficient information if the error relates 
to a certain node or attribute that only appear in one XML file.

When I had a problem it was due to a class that was used by a scheduler 
definition but no longer was available - in that case there were no 
problems with the XML itself.

Michael Moossen wrote:
> Hi, Daniel!
> 
>   this is a FAQ with a very simple answer.
>   if you see an Exception like this in the console:
> --------------------
> The following critical error occured:
> Critical error during OpenCms initialization: Unable to read the OpenCms XML
> configuration.
> Giving up, unable to start OpenCms.
> --------------------
> SEVERE: Exception Processing ErrorPage[errorCode=500,
> location=/opencms/system/handler/handle500.html]
> org.opencms.main.CmsInitException: Critical error during OpenCms
> initialization:
> Unable to read the OpenCms XML configuration.
>         at org.opencms.main.OpenCmsCore.getInstance(OpenCmsCore.java:268)
>         at org.opencms.main.OpenCmsServlet.doGet(OpenCmsServlet.java:120)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>         at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
> ....
> 
>   in general no debug option is needed. if you want to find out what the problem
> is just look in your opencms.log:
>   normally you will find 6 errors in the opencms.log file:
> 17 Okt 2005 15:27:48,322 ERROR [  org.opencms.main.OpenCmsCore: 296] Critical
> error during OpenCms initialization: Unable to read the OpenCms XML
> configuration.
> 17 Okt 2005 15:27:48,322 ERROR [g.opencms.main.OpenCmsListener:  91]
> org.opencms.main.CmsInitException: Critical error during OpenCms
> initialization: Unable to read the OpenCms XML configuration.
> 17 Okt 2005 15:28:56,854 ERROR [lina.core.StandardWrapperValve: 276]
> Servlet.service() for servlet OpenCmsServlet threw exception
> 17 Okt 2005 15:28:56,870 ERROR [ina.core.ApplicationDispatcher: 726]
> Servlet.service() for servlet OpenCmsServlet threw exception
> 17 Okt 2005 15:27:48,322 ERROR [opencms.xml.CmsXmlErrorHandler:  63] Error
> parsing XML resource
> org.xml.sax.SAXParseException: Attribute "enabled" with value "xxx" must have a
> value from the list "TRUE true FALSE false ".
> 17 Okt 2005 15:27:48,306 ERROR [ache.commons.digester.Digester:1538] Parse Error
> at line 49 column 33: Attribute "enabled" with value "xxx" must have a value
> from the list "TRUE true FALSE false ".
> 
> th first 5 errors will be always the same (or something like that, depending on
> the OpenCms version) and the originating (the real one) Exception is the first
> generated in the log file (the last in the list above) so you have just to
> scroll a little bit in the opencms.log file to find the source of your
> troubles. 
>  
> HTH

-- 
Claus Priisholm, CodeDroids ApS
Phone: +45 48 22 46 46
cpr (you know what) codedroids.com - http://www.codedroids.com
cpr (you know what) interlet.dk - http://www.interlet.dk
--
Javadocs and other OpenCms stuff: 
http://www.codedroids.com/community/opencms