Wednesday, December 4, 2013

One or more post-processing actions failed. Consult the OPP service log for details.

The Concurrent Request ends with Phase 'Completed' and Status 'Warning' which indicates that the Output Post Processor (OPP) failed to generate an output file.


In such cases the request log file shows a generic error message indicating the the post-processing action has failed.

...
+------------- 1) PUBLISH -------------+
Beginning post-processing of request 3181343 on node FINAPPS at 25-OCT-2011 11:41:30.
Post-processing of request 3181343 failed at 25-OCT-2011 11:41:31 with the error message:
One or more post-processing actions failed. Consult the OPP service log for details.
+--------------------------------------+
...


The actual error returned by the XML Publisher Core engine is captured in the OPP log file.
One of the easiest way to obtain the OPP log file is to run the below script from the database by providing request_id.

SELECT fcpp.concurrent_request_id req_id, fcp.node_name, fcp.logfile_name
  FROM fnd_conc_pp_actions fcpp, fnd_concurrent_processes fcp
 WHERE fcpp.processor_id = fcp.concurrent_process_id
   AND fcpp.action_type = 6
   AND fcpp.concurrent_request_id = &request_id;


Output of the script contains logfile location just like below
/u01/app/inst/apps/NZAPPS/logs/appl/conc/log/FNDOPP10981694.txt

Developer/Administrator/DBA has to go to that location and take the OPP logfile

Alternate Method:


Getting OPP Log from the application itself
a. System Administrator > Concurrent > Manager > Administer
b. Search for 'Output Post Processor'
c. Click the 'Processes' button
d. Click the Manager Log button. This will open the 'OPP'
e. Same File have your request id so search for request id.




For my issue i have edited the template with BI publisher and uploaded in instance i got the same error.
after i uninstalled BI publisher and edited the same template with same code(tag) and uploaded in the instance.then problem solved.

when open it in normally that tag is appearing as <?ref...?> something like this...this is the mail problem of this issue.

No comments:

Post a Comment