#1 2009-06-18 15:56:53

**_jlok22_**

Help with org.xml.sax.SAXParseException

I think my sco_info.xsl file is corrupted as I get this error on Connect startup
[06-18 15:19:50]#### Starting user interface...
[06-18 15:19:50] brze (c) Exception occurred in startup.
[06-18 15:19:50] brze (c) org.xml.sax.SAXParseException: character not allowed
[06-18 15:19:50] brze (c) org.xml.sax.SAXParseException: character not allowed
[06-18 15:19:50] brze (c)     at com.jclark.xsl.sax.XSLProcessorImpl.handleXSLException(XSLProcessorImpl.java:263)
[06-18 15:19:50] brze (c)     at com.jclark.xsl.sax.XSLProcessorImpl.loadStylesheet(XSLProcessorImpl.java:182)
[06-18 15:19:50] brze (c)     at com.macromedia.airspeed.servlet.ui.XSLT.getStylesheetProcessor(XSLT.java:142)
[06-18 15:19:50] brze (c)     at com.macromedia.airspeed.servlet.ui.ConfigReader.parse(ConfigReader.java:205)
[06-18 15:19:50] brze (c)     at com.macromedia.airspeed.servlet.ui.ConfigReader.parse(ConfigReader.java:324)
[06-18 15:19:50] brze (c)     at com.macromedia.airspeed.servlet.ui.ConfigReader.parse(ConfigReader.java:324)
[06-18 15:19:50] brze (c)     at com.macromedia.airspeed.servlet.ui.ConfigReader.parse(ConfigReader.java:324)
[06-18 15:19:50] brze (c)     at com.macromedia.airspeed.servlet.ui.ConfigReader.parse(ConfigReader.java:324)
[06-18 15:19:50] brze (c)     at com.macromedia.airspeed.servlet.ui.ConfigReader.initialize(ConfigReader.java:128)
[06-18 15:19:50] brze (c)     at com.macromedia.airspeed.servlet.HTMLHandler.initialize(HTMLHandler.java:104)
[06-18 15:19:50] brze (c)     at com.macromedia.airspeed.servlet.BaseServlet.initializePhaseTwo(BaseServlet.java:75)
[06-18 15:19:50] brze (c)     at com.macromedia.airspeed.main.Main.run(Main.java:415)

Has anyone run into this problem or perhaps can send me their \appserv\apps\content\sco_info.xsl?

Thanks,

**_tlchurch_**

Re: Help with org.xml.sax.SAXParseException

Looks like an XML parsing error. Have you tried opening the file up in IE? That will help identify where the error is.

**_jlok22_**

Re: Help with org.xml.sax.SAXParseException

Thanks. I went back to review the edited files and looked for the offending character in IE's XML parser. It's back online now.