Error in PDF generation

Hi,
I have created a Adobe interactive form to fetch and edit details.. It was working fine.
But now when i am trying to test the application or trying to preview the forms in form builder, a ERROR pop ups..
Means.. with a error symbol and a OK button. No other message is there.. I ddnot change anything after it started working. But now i am facing this error.. Can anyone help me on this to solve the problem..?
regards,
Surya

Hi Surya,
Does other applications that are working fine include applications that are using Adobe forms? If not you need to check whether your ADS is installed properly or not? Also please check in your source code that in which method this is happening? Try to debug your code...
Gurmat

Similar Messages

FM 12: How do I create a .ps file of a book? (errors prevent PDF generation)

FM 12: How do I create a .ps file of a book? (errors prevent PDF generation)

There's probably a graphic on one of your pages that is causing a postscript division error (i.e. divide by zero?) See also: PostScript error offending command div
As Jeff suggests, track down the errant graphic to see what's wrong. If you print to file, you should get an idea of roughly where in the docs the error occurs by watching the print thermometer display.

Error with PDF Generation

I have been working on avery design and print online and i keep getting an error message because the pdf to be able to print is unable to be generated

Reader can't generate PDF files. You must be using something else to do that, so the problem is not with Reader...

Error whit PDF Generation Processing exception during a "UsageRights" opera

Hi experts,
I have a problem when I wanna generate a PDF Form in a WebDynpro application. The log error is:
 
com.sap.tc.adobe.pdfdocument.base.core.PDFDocumentRuntimeException: Interactive Form Operation Failed
at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:700)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.afterApplicationModification(ClientApplication.java:1041)
at com.sap.tc.webdynpro.clientserver.phases.RespondPhase.execute(RespondPhase.java:60)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseLoop(WindowPhaseModel.java:101)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processPhaseLoop(WebDynproWindow.java:547)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:66)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1547)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1361)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDoProcessing(AbstractExecutionContextDispatcher.java:154)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppProcessing.doService(DispatchHandlerForAppProcessing.java:35)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToApplicationDoProcessing(ExecutionContextDispatcher.java:114)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:80)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:571)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:602)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:523)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:270)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:729)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:256)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:258)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:202)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:140)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:92)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:104)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:61)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:466)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:291)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:240)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:425)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:250)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Caused by: com.sap.tc.adobe.pdfdocument.base.core.PDFDocumentRuntimeException: PDFDocument Processor failed to process RenderRequest Due to the following Reason
Processing exception during a "UsageRights" operation.
Request start time: Tue Jan 10 11:31:14 COT 2012
com.adobe.ProcessingException: com.adobe.ProcessingException: Credential login error while applying usage rights to PDF: /usr/sap/CND/J02/j2ee/cluster/server0/temp/adobewa_CND_27241950/DM3888098661083088935.dir/DM5190493105499627278.tmp
 
Specific error information:
error while logging into credential ^0
GeneralError: Operation failed.
SecurityHandler.login:-1:
Could not create temporary file
 
but in other application webdynpro I can generate the PDF without error. So, I read many forums in the SDN but my system its Ok with the ADS Configuration.
 
Please help me, I don't know how solved this problem and is very urgent.
 
NetWeaver CE 7.1 Ehp 1
 
Thank you,
Jim Gledward

There can be several reasons for getting this Error.
1.ADS problem.
2. Binding problem.
3. Value node, Cardinality problem(1-n)
4. Not mapping PDF Source problem
5.PDFSource - type-Binary
Please check it once. If you can post the total error it would be better.

Create RFx PDF - PDF Generation error

All,
We are getting an error while generating a PDF for the RFx using the option "Create RFx PDF" under the Action tab in Frictionless SRM 2005.
fpa_20090604_00000.log:2009-06-05 16:19:02.779 ERROR local4 CachePDF queueGeneratePDF RequestHandler.RqThread: genpdf Kp9Ld6BvcZnJrGlQXQlx1vXFQGYpwmDdJnqSsK8BrTG7cfG0q5hm!-988702725!1244233035001 nehkumar com.frictionless.api.common.exception.ApplicationException: error generating pdf. Detail: java.lang.NullPointerException, null. Session: Kp9Ld6BvcZnJrGlQXQlx1vXFQGYpwmDdJnqSsK8BrTG7cfG0q5hm!-988702725!1244233035001. User: -2147474347:104:Neha Kumar. Submitted at: Fri Jun 05 16:18:55 EDT 2009 com.frictionless.api.common.exception.ApplicationException: error generating pdf. Detail: java.lang.NullPointerException, null. Session: Kp9Ld6BvcZnJrGlQXQlx1vXFQGYpwmDdJnqSsK8BrTG7cfG0q5hm!-988702725!1244233035001. User: -2147474347:104:Neha Kumar. Submitted at: Fri Jun 05 16:18:55 EDT 2009| at com.frictionless.doc.display.util.CachePDF.queueGeneratePDF(CachePDF.java:478)| at com.frictionless.doc.display.util.CachePDF.processRequestHook(CachePDF.java:150)| at com.frictionless.doc.display.util.AbsDocRQ.processRequest(AbsDocRQ.java:187)| at com.frictionless.doc.display.util.AbsRQ.run(AbsRQ.java:105)| at java.lang.Thread.run(Thread.java:534)|java.lang.RuntimeException: error generating pdf. Detail: java.lang.NullPointerException, null. Session: Kp9Ld6BvcZnJrGlQXQlx1vXFQGYpwmDdJnqSsK8BrTG7cfG0q5hm!-988702725!1244233035001. User: -2147474347:104:Neha Kumar. Submitted at: Fri Jun 05 16:18:55 EDT 2009| at com.frictionless.doc.display.util.CachePDF.queueGeneratePDF(CachePDF.java:478)| at com.frictionless.doc.display.util.CachePDF.processRequestHook(CachePDF.java:150)| at com.frictionless.doc.display.util.AbsDocRQ.processRequest(AbsDocRQ.java:187)| at com.frictionless.doc.display.util.AbsRQ.run(AbsRQ.java:105)| at java.lang.Thread.run(Thread.java:534) error generating pdf. Detail: java.lang.NullPointerException, null. Session: Kp9Ld6BvcZnJrGlQXQlx1vXFQGYpwmDdJnqSsK8BrTG7cfG0q5hm!-988702725!1244233035001. User: -2147474347:104:Neha Kumar. Submitted at: Fri Jun 05 16:18:55 EDT 2009
fpa_20090604_00000.log:2009-06-05 16:19:02.83 ERROR local4 CachePDF processRequestHook() RequestHandler.RqThread: genpdf Kp9Ld6BvcZnJrGlQXQlx1vXFQGYpwmDdJnqSsK8BrTG7cfG0q5hm!-988702725!1244233035001 nehkumar com.frictionless.api.common.exception.ApplicationException: error generating pdf. Detail: java.lang.NullPointerException, null. Session: Kp9Ld6BvcZnJrGlQXQlx1vXFQGYpwmDdJnqSsK8BrTG7cfG0q5hm!-988702725!1244233035001. User: -2147474347:104:Neha Kumar. Submitted at: Fri Jun 05 16:18:55 EDT 2009 com.frictionless.api.common.exception.ApplicationException: error generating pdf. Detail: java.lang.NullPointerException, null. Session: Kp9Ld6BvcZnJrGlQXQlx1vXFQGYpwmDdJnqSsK8BrTG7cfG0q5hm!-988702725!1244233035001. User: -2147474347:104:Neha Kumar. Submitted at: Fri Jun 05 16:18:55 EDT 2009| at com.frictionless.doc.display.util.CachePDF.queueGeneratePDF(CachePDF.java:478)| at com.frictionless.doc.display.util.CachePDF.processRequestHook(CachePDF.java:150)| at com.frictionless.doc.display.util.AbsDocRQ.processRequest(AbsDocRQ.java:187)| at com.frictionless.doc.display.util.AbsRQ.run(AbsRQ.java:105)| at java.lang.Thread.run(Thread.java:534)|java.lang.RuntimeException: error generating pdf. Detail: java.lang.NullPointerException, null. Session: Kp9Ld6BvcZnJrGlQXQlx1vXFQGYpwmDdJnqSsK8BrTG7cfG0q5hm!-988702725!1244233035001. User: -2147474347:104:Neha Kumar. Submitted at: Fri Jun 05 16:18:55 EDT 2009| at com.frictionless.doc.display.util.CachePDF.queueGeneratePDF(CachePDF.java:478)| at com.frictionless.doc.display.util.CachePDF.processRequestHook(CachePDF.java:150)| at com.frictionless.doc.display.util.AbsDocRQ.processRequest(AbsDocRQ.java:187)| at com.frictionless.doc.display.util.AbsRQ.run(AbsRQ.java:105)| at java.lang.Thread.run(Thread.java:534) Error generating PDF
Any help resolving this issue is greatly appreciated.
Thanks
Narasing
Edited by: Narasing Mukkavilli on Jun 10, 2009 7:37 PM

Looks like a PDF rendering issue. Please raise OSS message to SAP to get you a fix.
Good Luck

Error during context generation

Dear Friends,
In interactiveForm UI, when i put adobe form name in Templatesource and try to generate context automatically,
i get an error message ' Error during context generation ' and an empty context node is created.
i manually create attributes under that node and populate them in wddoinit method.
but i dont get those values on PDF output.
What may be the error ??
Kindly suggest.

Hi Otto,
I want to display data of an internal table in adobr form using web dynpro abap and adobe interactive form.
my web dynpro abap application is ready and adobe form is also ready.
when i integrate adobe interactive form on WDA and put form name in TEMPLATESOURCE and press enter
it throws an error message - 'Error in context generation' and an empty node is generated in WDA.
on running the application adobe form is displayed but no data is displayed.
what may be the error ?
i maintained attributes of node manually but then also no data is displayed.
that means data binding is not successful.
what may be the case ???
kindly suggest

Help: PDF Generation Problems in Reports 3.0

Hi Techies,
We are generating PDFs from Oracle Reports 3.0
The PDF generation is fine in some datbases.
But in some database,when the records are more, during PDF
generation, Dr.Watson error is encountered, saying access
violation.
Can any one please clarify whether the error is due to memory
constraints on the system or if it has something to do with
Oracle Reports setting, while generating PDFs.
Do note that the reports are running fine, when the report has
less number of records.
Any suggestion/tip is awaited at the earliest.
Thanks in advance,
Geoff
null

Hi!
Remove cache from output dir from time time.
(i.e. from virtual dir where report server puts output)
let me know ...
later
Geoff (guest) wrote:
: Hi Techies,
: We are generating PDFs from Oracle Reports 3.0
: The PDF generation is fine in some datbases.
: But in some database,when the records are more, during PDF
: generation, Dr.Watson error is encountered, saying access
: violation.
: Can any one please clarify whether the error is due to memory
: constraints on the system or if it has something to do with
: Oracle Reports setting, while generating PDFs.
: Do note that the reports are running fine, when the report has
: less number of records.
: Any suggestion/tip is awaited at the earliest.
: Thanks in advance,
: Geoff
null

PDF Generation problems in Reports 3.0

Hi,
I am generating PDFs from Oracle Reports 3.0
The PDF generation is fine in some datbases.
But in some database,when the records are more, during PDF
generation, Dr.Watson error is encountered, saying access
violation.
Can any one please clarify whether the error is due to memory
constraints on the system or if it has something to do with
Oracle Reports setting, while generating PDFs.
Do note that the reports are running fine, when the report has
less number of records.
Any help in this matter is appreciated.
Regards,
PRAKASH
null

Hi!
Remove cache from output dir from time time.
(i.e. from virtual dir where report server puts output)
let me know ...
later
Geoff (guest) wrote:
: Hi Techies,
: We are generating PDFs from Oracle Reports 3.0
: The PDF generation is fine in some datbases.
: But in some database,when the records are more, during PDF
: generation, Dr.Watson error is encountered, saying access
: violation.
: Can any one please clarify whether the error is due to memory
: constraints on the system or if it has something to do with
: Oracle Reports setting, while generating PDFs.
: Do note that the reports are running fine, when the report has
: less number of records.
: Any suggestion/tip is awaited at the earliest.
: Thanks in advance,
: Geoff
null

APEX 4.1 - APACHE FOP PDF generation problem.

Hi all,
I'm having problem with PDF generation using APACH FOP on OC4J.
When I test my print server as described here:
http://marcsewtz.blogspot.com/2008/06/heres-another-posting-on-pdf-printing.html
everything works without problem. But when I upload my Layout to APEX and try to generate PDF from apex I'm getting error:
oracle.xml.parser.v2.XMLParseException: Unexpected EOF.
 at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:320)
 at oracle.xml.parser.v2.XMLReader.popXMLReader(XMLReader.java:549)
 at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1375)
 at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:362)
 at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:308)
 at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:337)
 at oracle.xml.xslt.XSLProcessor.newXSLStylesheet(XSLProcessor.java:714)
 at oracle.xml.xslt.XSLStylesheet.<init>(XSLStylesheet.java:322)
 at oracle.xml.parser.v2.XSLStylesheet.<init>(XSLStylesheet.java:114)
 at apex_fop._jspService(_apex__fop.java:71)
 [SRC:/apex_fop.jsp:21]
I could see similar post here:
Handling Special characters in call to apex_util.download_print_document
But it doesn't explain my case as it's crashing even when I generate empty pdf(no data so no special characters, only empty XML file with no data should be sent to print server)
Is there any way to see what xml is sent do print server for processing? That could eventually show where is a problem.
Palo

My mistake, there was really an "&" character in my template. now when I replaced it with %26 it works.
However I would be still interested if there is a way to see what data is APEX engine sending to print server cause it will help me to find this kind of errors.
Palo

PDF generation with FOP throws NPE

Hi,
Stack trace
at oracle.xml.jaxp.JXTransformer.reportXSLException(JXTransformer.java:769)
at oracle.xml.jaxp.JXTransformer.transform(JXTransformer.java:342)
I'm using standard Java 1.4 API calls to create a PDF document from a DOM with Apache FOP 0.20.5.
The servlet is deployed to Oracle 10g Application Server 9.0.4.0.0. With Tomcat 4.1.30 the same code executes without exceptions
Because I have to port our web application to Oracle for a new customer it is important for me to get this fixed soon.
Thank you
Eckard

Light at the end of the tunnel: It seems to work when FO and PDF generation are separated. Until now the DOM was piped into FOP who internally created the FO from SAX events and then seems to parse it again to create PDF.
I separated the two steps: There is no problem in FO generation, but due to a namespace problem subsequent parsing fails
("org.apache.fop.apps.FOPException: null:2:10 Root element is missing the namespace declaration: http://www.w3.org/1999/XSL/Format")
Now the correct exception comes up. Whether FOP SAX event listener is buggy or XML parser's error handling has a problem, I don't know
Thank you anyway
Eckard

CFDOCUMENT PDF generation peformance on Linux running CF server 8 or 9 is horrible

Can anyone help me understand how I can get the <cfdocument> tag to generate PDFs in reasonable time (and without throwing timeout errors) when running on CF 8 on Linux? Running on CF 9 doesn't make a difference, either. I can run the same code that generates a PDF on a Win 7 system and it completes the 1-2 page PDF in seconds. Do the same thing in CF8/9 on Linux and it takes so long (minutes) and then throws a timeout error. When we tried using Railo instead of CF8/9 it ran fine as well.

Our apps guy figured out the problem after googling the error log message. To put this in context, the deployed app is running in a Tomcat container on Linux.
The root cause is Java's AWT thinking there should be an Xserver available to talk to. Somehow in the code interactions during the PDF generation, calls are made to an Xserver that doesn't exist, with an absurdly long timeout. Adding the line "-Djava.awt.headless=true" to the catalina.sh script has solved the issue.
Hope this helps others!
Tea man

Internal memory error during SQL generation. (QP0002)

Post Author: Rajesh Kumar
CA Forum: WebIntelligence Reporting
Hi,
I developed one Report in BO 5.1 version (Report size à 13 MB) and I Migrated this Report to BO XIR2,
After I Migrated this Report to BO XI R2 this Report was worked perfectly in DESKI & also in WEBI
But now for the past few Days (nearly 1 week) this Report is not working in WEBI, but itu2019s perfectly working in DESKI. In WEBI itu2019s showing error message à u201CInternal memory error during SQL generation. (QP0002)u201D
Iu2019m having one PDF documentation for BO Error Messages Listing, in that Documentation I have found the below à
Internal memory error during SQL generation. (QP0002)
Cause This error occurs when there is no longer enough memory to generate the SQL.
Action You should close other applications and then rerun the query.
I tried this alsou2026.
I closed all other applications and I Refreshed this Report, but again the same error is coming in WEBI
Report is working in DESKI but itu2019s not working in WEBI, I donu2019t know how to rectify this problem
Can anyone help me in this to rectify.. please
Thanks in advance
Rajesh Kumar

Hi,
I investigated further and if the previous solution doesn't help you to resolve the issue please test the below mentioned solution.
When several contexts are possible for a query, the system tests if they produce the same set of tables. If they are identical, it is not necessary to prompt the user. It is the default behavior. But for some particular universes, the designer defines different contexts with the same tables, but with a different set of joins. This will compare the context with the joins. When this happens, InfoView fails with this error.
Resolution
1. Import the universe.
2. Modify the following parameter:
COMPARE_CONTEXTS_WITH_JOINS = No
3. Export the universe.
4. Open the Desktop Intelligence report in InfoView and refresh it.
It will refresh successfully
Regards,
Sarbhjeet Kaur

BI 7.0 Web PDF Generation

Hi folks,
I do have a severe problem with PDF generation and it looks like a common issue.
I integrated Button to convert my Management Webreport to PDF, no big issue so far.
But the generated PDF is not bevaing like expected. We do have a BI report that contains 3 charts horizontally alligned by a table to fit the screen and 1 table below
those charts.
This report fits perfectly on one page landscape.
When generating PDF locally (PDF generator installed on client PC) Internetexplorer ==>PDF works as expected.
When using the Button in Webtemplate to use the BI functionality to export to PDF the PDF is a mess.
All template items are displayed in sequence taht means instead of 3 horizontal charts I see 3 charts and 1 table underneath each other.
It looks like the old fashioned 3.x print function.
My question:
Is there a way to influence the PDF generation. Maybe a class ( like former 3.x Table Interface) to modify to render the PDF like the template appearance?
We cannot install PDF clients locally nor can we ship management those reports coming from BI. Report designer is no alternative because of missing functionality.
TIA
Joerg

Thanks so far,
currently when using the container item and referring by command wizard ( export to PDF) the system is not generating any item.
Error Message 'file has no page and can't be opened...' occurs.
I think this is a really urgent Development issue because I think printing via PDF is getting more and more important since not everyone is using IE7 ( which is not fully supported by SAP either) to scale pages for printing.
Best regards
Joerg

Handle WSDL data connection timeout during PDF generation

I have created in LiveCycle Designer XDP template. In template i defined WSDL Data connection. For data loading i call xfa.connectionSet.WsDataConnection.execute(0).
For PDF generation i created LiveCylce process and use generatePDFOutput component.
If WebService works output service generates document with all data - OK.
If i turn off webservice and run process ouputservice generates PDF document with empty fields. Is where any possibility to raise execption to calling process if WSDL connection timeouts or gives SOAP fault error in response?
I want catch web service errors in process and do not generate PDF if some webservice used in PDF template is not accesible during generation.

Hi Martin,
We are experiencing the same issue with SAP/Vertex. Can you let me know how you resolve this? Did you change the SAP gateway timeout parameter? If so, which one is it?
Your help on this is greatly appreciated.
Thanks much!
Best regards,
Cyanna

Cannot retrieve teplate structure: Error creating PDF

Hi,
I've installed a Composite Form as the start of a process, and when I go to Administration and try to generate the PDF file I get the following error:
Cannot retrieve teplate structure: Error creating PDF
When I go to the log, I get this trace:
Error creating PDF
com.sap.caf.eu.gp.base.exception.EngineException: Error creating PDF
at com.sap.caf.eu.gp.model.forms.adapter.FormAdapterMediator.createInstanceDocument(FormAdapterMediator.java:462)
at com.sap.caf.eu.gp.model.forms.preproc.FormPreprocessor.instanciateTemplate(FormPreprocessor.java:1982)
at com.sap.caf.eu.gp.model.forms.preproc.FormPreprocessor.createImpersonalizedFormInstance(FormPreprocessor.java:1170)
at com.sap.caf.eu.gp.ui.admin.uforms.UnpersonalizedFormsManager.createNewForm(UnpersonalizedFormsManager.java:888)
at com.sap.caf.eu.gp.ui.admin.uforms.UnpersonalizedFormsManager.createForm(UnpersonalizedFormsManager.java:457)
at com.sap.caf.eu.gp.ui.admin.uforms.wdp.InternalUnpersonalizedFormsManager.createForm(InternalUnpersonalizedFormsManager.java:190)
at com.sap.caf.eu.gp.ui.admin.uforms.CreateUForm.onActionOK(CreateUForm.java:243)
at com.sap.caf.eu.gp.ui.admin.uforms.wdp.InternalCreateUForm.wdInvokeEventHandler(InternalCreateUForm.java:156)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:131)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:72)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:156)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:91)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:161)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:109)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:96)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:469)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:52)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1395)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1215)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDoProcessing(AbstractExecutionContextDispatcher.java:158)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppProcessing.doService(DispatchHandlerForAppProcessing.java:35)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:93)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToApplicationDoProcessing(ExecutionContextDispatcher.java:114)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:81)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:506)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:526)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:457)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:248)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:699)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:231)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:230)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:205)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:93)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:140)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:93)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:105)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:61)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:32)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:309)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
Caused by: com.sap.caf.eu.gp.model.forms.exceptions.AdapterException: Error creating PDF
at com.sap.caf.eu.gp.model.forms.exceptionhandling.ExceptionHandler.throwAdapterException(ExceptionHandler.java:851)
at com.sap.caf.eu.gp.model.forms.adapter.pdf.AdobeDSFormAdapter.createInstanceDocuments(AdobeDSFormAdapter.java:180)
at com.sap.caf.eu.gp.model.forms.adapter.pdf.AdobeAdapter.createInstanceDocument(AdobeAdapter.java:204)
at com.sap.caf.eu.gp.model.forms.adapter.FormAdapterMediator.createInstanceDocument(FormAdapterMediator.java:456)
... 70 more
Caused by: com.sap.tc.adobe.pdfdocument.base.core.PDFDocumentRuntimeException: PDFDocument Processor failed to process RenderRequest...
at com.sap.tc.adobe.pdfdocument.base.core.PDFDocumentProcessor.process(PDFDocumentProcessor.java:55)
at com.sap.tc.adobe.pdfdocument.base.core.PDFDocumentCreationContext.execute(PDFDocumentCreationContext.java:136)
at com.sap.tc.adobe.pdfdocument.impl.PDFCreationContextImpl.execute(PDFCreationContextImpl.java:90)
at com.sap.caf.eu.gp.model.forms.adapter.pdf.AdobeDSFormAdapter.createInstanceDocuments(AdobeDSFormAdapter.java:152)
... 72 more
Caused by: com.sap.tc.adobe.pdfobject.core.PDFObjectRuntimeException: Logical Target ConfigPort_Document not mapped to a physical system.
at com.sap.tc.adobe.pdfobject.core.PDFObjectDII.invoke(PDFObjectDII.java:349)
at com.sap.tc.adobe.pdfobject.core.PDFObjectDII.doSoapCall(PDFObjectDII.java:81)
at com.sap.tc.adobe.pdfobject.core.PDFObject.render(PDFObject.java:3610)
at com.sap.tc.adobe.pdfdocument.base.core.PDFDocumentRenderHandler.handle(PDFDocumentRenderHandler.java:152)
at com.sap.tc.adobe.pdfdocument.base.core.PDFDocumentProcessor.process(PDFDocumentProcessor.java:52)
... 75 more
Caused by: com.sap.engine.services.webservices.espbase.discovery.TargetNotMappedException: Logical Target ConfigPort_Document not mapped to a physical system.
at com.sap.esi.esp.service.server.query.discovery.DestinationsHelperImpl.getDSTTemplateForSystem(DestinationsHelperImpl.java:894)
at com.sap.esi.esp.service.server.query.discovery.DestinationsHelperImpl.getWSDLUrl(DestinationsHelperImpl.java:397)
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.getWSDLUrl(GenericServiceFactory.java:222)
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:187)
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:175)
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:160)
at com.sap.tc.adobe.pdfobject.core.PDFObjectDII.invoke(PDFObjectDII.java:278)
... 79 more

The address is http://<host>:<port>/inspection.wsil
It need not be localhost. Any address that's visible to the WAS where you are configuring should work. Make sure to provide the user account and password configured for ADS on the security settings of the destination.
One other thing I forgot to ask - did you do all the steps requried to configure ADS with CE? If not, please send me your email address and I'll send you the doc.
Thanks!
Rao

Error in PDF generation

Similar Messages

Maybe you are looking for