Getting xxorg.xml.sax.SAXException; Additional msg - object name:

Hi,

I have a dossier type of document (virtual document) in webtop. When I try to edit / checkout /export the document I get the following error message:

xxorg.xml.sax.SAXException; Additional msg - object name:

org.xml.sax.SAXException; Additional msg - object name:

We are using webtop 5.3.0.135 SP1 version. and DFC Version is 5.3.0.124 SP1.

Please help.

Thanks and Regards,

Krishna

Find more posts tagged with

Comments

mpothen

Any luck resolving this? I'm getting the same error under similar circumstances..

Thanks,

Mitch

Francois Dauberlieu

Any customization ?

If yes, then you could try to recompile it to see if it compiles

What version of JRE on the client machine ?

Can you give us the full error message ?

ambadipudi.rama

No, customization.

We are using JRE 1.5 version. I am getting the same error message as shown below:

Error

We're sorry, there was a problem with your request.

xxorg.xml.sax.SAXException; Additional msg - object name: <Name of the component>
org.xml.sax.SAXException; Additional msg - object name: <Name of the component>

To my knowledge, we will get SAXs exceptions, when there is any error in the xml file and the parser is trying to parse the xml file. But to check for the errors, I am not able to edit / export / checkout the component.

Please suggest as how should I proceed to resolve the issue.

Thanks and Regards,

Krishna

mszurap

Is it an XML file which you are trying to export? Is it working for other, non-xml files?

If you have access to content server, then you can get the physical location of the file on the content server. Use Documentum Administrator: Administration/Job Management/Administrative Methods, there select the GET_PATH administrative method. You can then check if the file is well-formed or not (it should be well-formed, because as far as I know DFC enforces well-formedness, and you cannot check-in bad xml files - this was not enforced before 5.3).

Francois Dauberlieu

Any chance you can share the XML file with us so we can test it ?

mpothen

Well, although I couldn't identify the root cause, I was able to find some type of resolution.

Basically my virtual document (a book) referenced many other virtual docs (sections in the book). One of the sections was somehow corrupted on the last check-in. So by checking it out and back in again, it apparently fixed the issue.

The way I identified the bas section was to start over, and insert references (sections) into the book one at a time. Check out the book, ad a reference, check it back in. Kept doing this until it broke on the bad section.

Then I checked out/in the bad section and it apparently resolved the issue. Again, no idea how or why.. I could also have deleted the most recent version I suspect.

Anyways, this is how I got it to work.

Francois Dauberlieu

Thanx for letting us know