Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
2 replies Latest Post - ‏2013-02-27T08:48:23Z by Tony_Goodman
Tony_Goodman
Tony_Goodman
26 Posts
ACCEPTED ANSWER

Pinned topic UTF-8 Error reading specification file.

‏2013-02-26T15:51:50Z |
I am getting an error:

CRRPE1054E Cannot open: file:/U:/RPE_Data/generated.dsx
Invalid byte 1 of 1-byte UTF-8 sequence.

This file (attached) is created using DXL from DOORS and is then handed to launcher.

The XML file is plain text and does not contain any encoding instruction.
I cannot see any special characters in the XML.

This only happens with one module.

I am stuck. Any help much appreciated!

Tony Goodman, www.smartdxl.com
Updated on 2013-02-27T08:48:23Z at 2013-02-27T08:48:23Z by Tony_Goodman
  • Dragos.Cojocari
    Dragos.Cojocari
    1608 Posts
    ACCEPTED ANSWER

    Re: UTF-8 Error reading specification file.

    ‏2013-02-26T18:44:39Z  in response to Tony_Goodman
    Hey Tony,

    dsx files are XMLs and so the error that you see is reported by the XML parser RPE uses to load the file. So to identify the error you need to open the file in an XML editor/reader. Most web browsers are enough to identify this type of errors. Renaming the file to XML and openning in Firefox shows the following:

    
    XML Parsing Error: not well-formed Location: file:
    ///.... Line Number 1, Column 5930:
    


    Opening the file in text editor and going at that column shows that the culprit is: value="P4792 – MSRS Replacement Nicelog" which contains and invalid XML character. This character is the "-" like character.

    Regards,
    Dragos

    RPE Actual
    • Tony_Goodman
      Tony_Goodman
      26 Posts
      ACCEPTED ANSWER

      Re: UTF-8 Error reading specification file.

      ‏2013-02-27T08:48:23Z  in response to Dragos.Cojocari
      Thank you Dragos.

      I already did exactly what you said, but I failed to spot the character!

      Two heads are always better than one.

      Tony Goodman, www.smartdxl.com