On-Demand Print Client Error_ Server Is Stopped

Description

When using the On-Demand Print Client to print to the LPS, I get an error stating that the server is stopped, despite the fact that the server is running.

Solution

This issue is usually accompanied with an error 117 in the Windows application event log ("Failed to connect to Batch Print"). Contact your system administrator before attempting this solution.
To resolve the problem, follow these steps:

Win NT/2000

  1. Stop the Loftware Print Server.
  2. From the Windows NT desktop of the machine where the LPS is running, select Start | Run
  3. Type "dcomcnfg" in the Run box.
  4. Click OK; the Distributed COM Configurator opens.
  5. Select the "Default Security" tab and in the "Default Access Permissions" section, click Edit Default.
  6. Click Add. On the "List Names From" line, choose the appropriate domain for the account the LPS is using, and then click Show Users. Highlight the user the LPS is using from the list of names, click Add, and OK.
  7. In the "Default Launch Permissions" section of the "Default Security" tab, click Edit Default.
  8. Click Add. On the "List Names From" line, choose the appropriate domain for the account the LPS is using, and then click Show Users. Highlight the user the LPS is using from the list of names and then click Add, click OK.
  9. Re-start the LPS and launch the On Demand Print Client from the remote workstation. ODP Client should now process without error.

Windows XP

  1. Start > Run, type dcomcnfg in the Run Box.
  2. Go to Component Services > Computers > My Computer.
  3. Right-click My Computer, choose Properties, or in the Menu Bar, choose Action > Properties.
  4. Open the Default COM Security Tab, and in both the Access Permissions and Launch permissions sections, type in the Username for which you wish to add permissions.
  5. Press the Check Names button, the network name and user is displayed.
  6. Click OK.
  7. Re-start the LPS and launch the On Demand Print Client from the remote workstation. The ODP Client should now print without error.