FAQ: The remote procedure call failed and did not execute

Problem: when RPM receives a print job, the job doesn't print on our shared printer

Description: When RPM receives my print job, the queue is suspended or the job is held and it doesn't print. The two messages state:

The remote procedure call failed and did not execute.
The handle is invalid.

Note: This article is for versions of RPM prior to 5.0. We now use login credentials to access shared printers and drives correctly.

Answer: This is a Windows issue where RPM gets no response from the shared printer. The only known long-term solutions are...

  • connect the printer directly to the RPM host computer
  • move RPM to the computer sharing the printer
  • if the printer is a TCP/IP printer, configure the printer as an LPR printer on the RPM host computer