≡ Menu

PDF Preview fails in Workspace

Switching to PDF Preview in Workspace on a report generated by Financial Reporting fails with the message “Unable to process request.”

tested through PSU
Unable to process request occurs with some but not all FR reports.


For each FR server, update to TRACE:32 the logging levels in


for three loggers:

<logger name=’oracle.EPMFR’ level=’TRACE:32′ useParentHandlers=’false’>
<handler name=’epmfr-handler’/>
<logger name=’oracle.EPMFR.access’ level=’TRACE:32′ useParentHandlers=’false’>
<handler name=’epmfr.access-handler’/>
<logger name=’oracle.EPMFR.jsp’ level=’TRACE:32′ useParentHandlers=’false’>
<handler name=’epmfr-handler-jsp’/>

Restart the FR servers
Replicate the issue
Check these logs for details of the problem:



This error in the sysout log:

at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:323)
at oracle.xml.parser.v2.NonValidatingParser.parseEndTag(NonValidatingParser.java:1604)
at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1549)
at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:409)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:355)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:319)
at oracle.xdo.common.config.ConfigReader.read(ConfigReader.java:463)
at oracle.xdo.common.config.ConfigReader.read(ConfigReader.java:442)
at oracle.xdo.template.PropertyManager.getProperties(PropertyManager.java:279)
at oracle.xdo.template.PropertyManager.getRuntimeProperties(PropertyManager.java:194)
at oracle.xdo.template.FOProcessor.generate(FOProcessor.java:955)
at com.hyperion.reporting.printengine.PrintEngine.printFormattedReportXml(Unknown Source)
at com.hyperion.reporting.printengine.PrintEngine.generateFormattedReportXml(Unknown Source)
at com.hyperion.reporting.printengine.PrintEngine.printReport(Unknown Source)
at com.hyperion.reporting.printserver.PrintEngineInstanceThread.processInstance(Unknown Source)
at com.hyperion.reporting.printserver.PrintEngineInstanceThread.generateInstanceOutput(Unknown Source)
at com.hyperion.reporting.printserver.PrintEngineInstanceThread.run(Unknown Source)

indicates that the xdo.cfg file is corrupted/improperly formatted.

In addition to specifying a temp location “c:\temp” (which may not be a valid location in your environment, the attached xdo.cfg file also appears to have a misplaced comment tag (–>) at line 24 and an extra tag at line 27. As currently defined the file is not a valid xml document and does not open/parse correctly in a browser. I have uploaded a revised/corrected xdo.cfg file to the SR (xdo_rev.cfg) if you want to compare it to a properly formatted file. Note, the revised file still has the “c:\temp” line active. You can edit this line to refer to refer to the valid system directory. Alternatively, you can also simply comment out this line; FR Web will use the System Temp directory defined by the %TEMP% environment variable.

xdo.cfg compare

xdo.cfg fix tags comparison

None at this time

external links

None at this time

{ 0 comments… add one }

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.