E2B XML not generating when using URLs in Message DTD & ACK DTD fields (Doc ID 2105216.1)

Last updated on JULY 06, 2017

Applies to:

Oracle Argus Safety - Version 6.0.5 and later
Oracle Argus Interchange - Version 6.0.5 and later
Information in this document applies to any platform.

Symptoms

When trying to transmit a report and generate physical XML file for Agencies which have been configured with URLs as their DTD path, the following error is observed in the E2B Transmit log:

"Unable to encode XML string due to following reason Error has occurred on Line: 0, Source Text: , Error Code: 0"

Examples of URLs that were used are:

http://eudravigilance.ema.europa.eu/dtd/icsr21XML.dtd

http://eudravigilance.ema.europa.eu/dtd/ichicsrack11XML.dtd

http://www.accessdata.fda.gov/xml/icsr-xml-v2.1.dtd

http://www.accessdata.fda.gov/xml/icsrack-xml-v1.1.dtd

NOTE: This is a common error that occurs when DTD files are not accessible during the XML file generation although, in this case, users are able to access the links from their ESM server and able to download the DTD files.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms