Error while opening report in Infoview

[Former Member]

I am getting following error while opening report in Infoview.

Following is error generated in tomcat,

com.businessobjects.rebean.wi.ServerException: Cannot open document. Error during import. (DX0005)

at com.businessobjects.rebean.fc.internal.platformspecific.xml.ras21.SAXHandlerERRORS$SAXHandlerERROR.initElement(SAXHandlerERRORS.java:108)

at com.businessobjects.rebean.fc.internal.platformspecific.xml.SXMLHandling$StructuredSAXHandler.startElement(SXMLHandling.java:187)

at com.businessobjects.rebean.fc.internal.platformspecific.xml.SXMLHandling$StructuredSAXHandler.startElement(SXMLHandling.java:202)

at com.businessobjects.rebean.fc.internal.platformspecific.xml.SXMLHandling$StructuredSAXHandler.startElement(SXMLHandling.java:202)

at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)

at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source)

at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)

at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)

at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)

at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)

at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)

at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)

at javax.xml.parsers.SAXParser.parse(Unknown Source)

at com.businessobjects.rebean.fc.internal.ras21.XMLviaRAS21Decode.openDocument(XMLviaRAS21Decode.java:537)

at com.businessobjects.rebean.fc.internal.ras21.RAS21DocumentComAdapter.openDocument(RAS21DocumentComAdapter.java:69)

at com.businessobjects.rebean.fc.internal.ras21.RAS21ReportEngineComAdapter.openDocument(RAS21ReportEngineComAdapter.java:100)

at com.businessobjects.rebean.fc.internal.ReportEngineImpl.openDocument(ReportEngineImpl.java:249)

at org.apache.jsp.viewers.cdz_005fadv.viewCDZDocument_jsp._jspService(viewCDZDocument_jsp.java:267)

at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)

at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)

at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)

at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)

at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)

at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)

at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)

at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)

at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)

at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)

at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)

at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)

at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)

at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)

at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)

at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)

at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)

at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)

at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)

at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)

at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)

at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)

at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)

at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)

at java.lang.Thread.run(Thread.java:534)

Caused by: java.lang.Exception: Cannot open document. Error during import. (DX0005) (80043746)

at com.businessobjects.rebean.fc.internal.platformspecific.xml.ras21.SAXHandlerERRORS$SAXHandlerERROR.initElement(SAXHandlerERRORS.java:100)

Please help me to resolve the above problem

Reagrds,

Ramesh

[Former Member]

Ramesh,

Were you able to figure out the cause of your problem.? could you please post it here

Thanks

parsi

[Former Member]

Hi,

If it is a deski report then try to open it using Desktop Intelligence if u have installed. If you can view itin deski then some problem while exporting the report to repository as a result not able to view that report.

If it is awebi Doc and you are using BOXI R3 then try to open it with Rich client and find out hteproblem.

Cheers,

Suresh Aluri.

[MariannevL]

Hi Ramesh,

It may seem like a lot of information, but from a debugging perspective it doesn't tell us much.

You need to give some more info and even then it would probably be a good idea to call support.

Can you tell us;

Which version are you on?

Can you open de document from another desktop intelligence machine, not only the one that it was built on?

- This checks ; you can import the document; the structure of the document is fine (not corrupted).

Can you refresh the document on that other machine?

- This check ; the link to the universe is fine, the universe can be imported, the connection to the database is fine.

What is your preference as a BOE user to view Deski documents?

- Try a few others, so you know if the problem is with one type only (and which).

Now you will have a few more pointers more as to where the problem lies.

Even then it can be sheer size of the document, complexity of it, etc.

Good luck,

Marianne