Hardcoded path in XMLTooling is invalid on localized WinXP/2003

Description

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

Environment

Windows 2003 R2 SP2 (Standard Edition, Czech version)

Attachments

4
  • 09 Sep 2012, 09:05 AM
  • 07 Sep 2012, 02:41 PM
  • 07 Sep 2012, 10:04 AM
  • 05 Sep 2012, 05:19 PM

Activity

Scott Cantor September 10, 2012 at 5:03 PM

Marking fixed with updated installers published.

Pavel Krejci September 10, 2012 at 8:51 AM

I've tested it on 2003 as well. The original problem is solved as the daemon works ok.
I will make another ticket for the other problem with %PATH%.

Scott Cantor September 9, 2012 at 10:51 PM

A fresh install on 32-bit Std Edition 2003 Czech Edition worked without any problems. Install completed, reboot prompt, then it came up clean. Added XMLTooling.ParserPool category on DEBUG and logged succesful path resolution to the localized directory.

Will release the update this week after I check a couple of things and test on 2008.

Scott Cantor September 9, 2012 at 9:32 PM

The PATH change is already handled by the installer. If that didn't work, it wouldn't work for anybody, ever.

I guess I'll try an install myself on this CZ version, but it sounds like the fix worked.

Pavel Krejci September 9, 2012 at 9:05 AM

The installation failed because shibd.exe couldnt find shibsp1_5.dll (used Filemon to troubleshoot). After adding "C:\Program Files\Shibboleth\SP\lib" to %PATH% the daemon started and installation completed.

After installation the stdout and stderr files are with size 0. The catalog files still contain the:
uri="%PROGRAMDATA%\Shibboleth\SP\xml\shibboleth\shibboleth-metadata-1.0.xsd"

shibd.log attached

Fixed

Details

Assignee

Reporter

Original estimate

Components

Fix versions

Affects versions

Created September 5, 2012 at 2:06 PM
Updated September 10, 2012 at 5:03 PM
Resolved September 10, 2012 at 5:03 PM