Question
- What is the meaning of the NPrinting Error Log message: "The remote procedure call failed" or "Failed to Open Document"
Answer
There are several possibilities:
QlikView
- The remote procedure call failed message is always generated when the QV Desktop is 'closed' or forcibly shut down during the processing of an NPrinting report.
- Note that NPrinting sends API calls to the QV desktop for report processing where the QV desktop does the heavy lifting during report generation.
- If the QV desktop is closed during the processing of an NPrinting report, the RPC remote procedure call failed message will appear.
- If using Local QV NP connections, this error will be added to the logs when the NP server is shutting down
- If using Server QVP connections, this error will be added to the logs when the QlikView server is shutting down
Qlik Sense:
- The Qlik Sense App is not published: this will generate failed to open document error
QlikView and Qlik Sense
- Section Access: if the NPrinting administrator and report recipients are NOT added to the SA load script
- Triggers (which are unsupported)
- Any unsupported items interfering with accessing of a QlikView or Qlik Sense document/application ie: On Open trigger in QikView.
- Invalid document path: In some cases the name of the QVW or Sense ID has changed. Ensure you are using accurate document paths and Qlik Sense IDs.
- The NPrinting Connection is 'not' in a 'Generated' status. Reload the NP connection associated with the report in question and ensure the connection is 'Generated'.
- If opening/editing NPrinting Microsoft office templates, ensure you have a licensed copy of MS Office running to prevent opening failures
- Ensure the version of the NPrinting Designer is the same version as the NPrinting Server.
You may also see this error when:
We suggest:
- Checking and keeping on top of and removing unsupported items
- Ensure the NPrinting service account can open the QVW
- Ensure valid network or QVP paths to QVWs and QVFs (accurate sense app IDs)
- In some cases, upgrading to the latest version of NPrinting will solve this issue. ie: when running an older unsupported version of NPrinting for example.
- Ensure that if Section Access is used that section access with NPrinting requirements are met. See https://community.qlik.com/t5/Knowledge/NPrinting-Reports-with-Qlik-Sense-connections-to-QS-apps-tha...
References:
