|
Diagnosis
An error occurred while creating a print version. Procedure
Contact your SAP administrator. Procedure for System Administration
Note 918236 contains detailed information.
Communication Failure:
Possible reasons for a communication failure:
- J2EE Engine of the SAP Enterprise Portal has not started.
- The RFC destination in the JCO Provider of the SAP J2EE Engine has not
been created.
- The RFC destination does not exist in the application server.
- Settings in SM59 on the application server do not match the settings of
the RFC destination in the JCO Provider of the J2EE Engine.
In Customizing, check the two activities:
- Application Server -> WebDynpro for ABAP -> Set Up Printing for
WebDynpro ABAP -> Set Up RFCDestination in the SAP NetWeaver Portal
- Application Server -> WebDynpro for ABAP -> Set up Printing for
WebDynpro ABAP -> Set Up RFC Destination for SAP NetWeaver Portal
System Failure:
Possible reasons for a system failure:
- Application server for ABAP and Application Server for Java have a
different support package level:
Check the support package level of your application server for ABAP andJava installation. The support package level must be identical.
- Adobe Document Service is not available
In Customizing, check the following activity:
Application Server -> WebDynpro for ABAP -> Set Up Printing forWebDynpro ABAP -> Set Up WebServiceDestination for the Adobe DocumentService.
- Usage type BI-Java is not installed:
Check whether the usage type BI-Java is installed on the applicationserver for Java
|