[JIRA] Updated: (SSPCPP-498) Hardcoded path in XMLTooling is invalid on localized WinXP/2003
Scott Cantor (JIRA)
noreply at shibboleth.net
Wed Sep 5 14:40:22 EDT 2012
[ https://issues.shibboleth.net/jira/browse/SSPCPP-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Cantor updated SSPCPP-498:
--------------------------------
Remaining Estimate: 2 days
Original Estimate: 2 days
> Hardcoded path in XMLTooling is invalid on localized WinXP/2003
> ---------------------------------------------------------------
>
> Key: SSPCPP-498
> URL: https://issues.shibboleth.net/jira/browse/SSPCPP-498
> Project: Shibboleth SP - C++
> Issue Type: Bug
> Components: Configuration, Installation / Packaging
> Affects Versions: 2.5.0
> Environment: Windows 2003 R2 SP2 (Standard Edition, Czech version)
> Reporter: pavelxkrejci at idp.protectnetwork.org
> Assignee: Scott Cantor
> Attachments: catalog.xml
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> The 2.5.0 installer puts the xml catalogs used by XMLTooling library in this folder:
> "c:\Documents and Settings\All Users\Data aplikací\Shibboleth\SP\xml"
> "c:\Documents and Settings\All Users" is value of ALLUSERSPROFILE env. variable.
> "Data aplikací" is localized "Application Data"
> This results in the following errors when trying to start shibd service:
> 2012-09-05 14:52:37 ERROR XMLTooling.ParserPool : fatal error on line 0, column 0, message: unable to open primary document entity 'C:\Documents and Settings\All Users/Application Data/Shibboleth/SP/xml/xmltooling/catalog.xml'
> 2012-09-05 14:52:37 ERROR XMLTooling.ParserPool : catalog loader caught exception: XML error(s) during parsing, check log for specifics
> 2012-09-05 14:52:37 ERROR XMLTooling.ParserPool : fatal error on line 0, column 0, message: unable to open primary document entity 'C:\Documents and Settings\All Users/Application Data/Shibboleth/SP/xml/opensaml/saml20-catalog.xml'
> 2012-09-05 14:52:37 ERROR XMLTooling.ParserPool : catalog loader caught exception: XML error(s) during parsing, check log for specifics
> 2012-09-05 14:52:37 ERROR XMLTooling.ParserPool : fatal error on line 0, column 0, message: unable to open primary document entity 'C:\Documents and Settings\All Users/Application Data/Shibboleth/SP/xml/opensaml/saml11-catalog.xml'
> 2012-09-05 14:52:37 ERROR XMLTooling.ParserPool : catalog loader caught exception: XML error(s) during parsing, check log for specifics
> 2012-09-05 14:52:37 ERROR XMLTooling.ParserPool : fatal error on line 0, column 0, message: unable to open primary document entity 'C:\Documents and Settings\All Users/Application Data/Shibboleth/SP/xml/shibboleth/catalog.xml'
> 2012-09-05 14:52:37 ERROR XMLTooling.ParserPool : catalog loader caught exception: XML error(s) during parsing, check log for specifics
> I tried to relocate the xml files into the folder
> "c:\Documents and Settings\All Users\Application Data\Shibboleth\SP\xml"
> but it resulted in yet another error:
> 2012-09-05 14:56:31 ERROR XMLTooling.ParserPool : fatal error on line 1, column 39, message: invalid byte '\' at position 2 of a 3-byte sequence
> 2012-09-05 14:56:31 ERROR XMLTooling.ParserPool : catalog loader caught exception: XML error(s) during parsing, check log for specifics
> 2012-09-05 14:56:31 ERROR XMLTooling.ParserPool : fatal error on line 1, column 39, message: invalid byte '\' at position 2 of a 3-byte sequence
> 2012-09-05 14:56:31 ERROR XMLTooling.ParserPool : catalog loader caught exception: XML error(s) during parsing, check log for specifics
> 2012-09-05 14:56:31 ERROR XMLTooling.ParserPool : fatal error on line 1, column 39, message: invalid byte '\' at position 2 of a 3-byte sequence
> 2012-09-05 14:56:31 ERROR XMLTooling.ParserPool : catalog loader caught exception: XML error(s) during parsing, check log for specifics
> 2012-09-05 14:56:31 ERROR XMLTooling.ParserPool : fatal error on line 1, column 39, message: invalid byte '\' at position 2 of a 3-byte sequence
> 2012-09-05 14:56:31 ERROR XMLTooling.ParserPool : catalog loader caught exception: XML error(s) during parsing, check log for specifics
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the commits
mailing list