Upgrading iPrint Renderer From 1.0 or 1.0.1 to 1.1 Corrupts the iPrintRenderer.conf File
Printer Drivers are Missing After Registering the Remote Renderer
Local Renderer Fails to Print the Password-Protected PDF Files
iPrint Rendering Service Fails to Start If the Windows User Account Password Changes or Expires
iPrntRendCmd Stops Responding During Configuration or Other Command Line Operations
On applying SUSE SLE security updates, registration to a secure renderer fails. To resolve this issue, do the following:
On the appliance, execute the following commands:
Make the /opt/novell/iprintmobile/bin/certman.sh script executable: chmod+x certman.sh
sh certman.sh -t utils -c
sh certman.sh -t cert -s
sh certman.sh -t cert -g
On the Windows computer, do the following:
On applying the security patches, the existing Remote renderer continues to work without any issues. The above issue is encountered with a new Secure Remote renderer or re-registration of the existing renderer.
Certificate validation fails if the third party certificate is already configured and activated before configuring iPrint Appliance server.
To resolve this issue, configure the iPrint Appliance server again and then upload and activate the certificates.
If you have upgraded the renderer from 1.0 or 1.0.1 to 1.1, the iPrintRenderer.conf file gets corrupted. On corruption of this file, the renderer also fails to uninstall.
To resolve this issue, do the following:
Replace the contents of the c:/NDPS/Renderer/Conf/iPrintRenderer.conf file with the following:
Word=doc,docx,rtf,docm,dotm Excel=xls,xlsx,xlsm,xlsb Powerpoint=ppt,pptx,pptm,ppsm inBuiltPDFRenderer=pdf #Adobe=pdf
On your client workstation, uninstall the Renderer.
Install the latest renderer. For more information, see Installing and Configuring a Remote Renderer.
If the remote renderer configured with Microsoft Office 2013 is under continuous load, then it may fail to print PowerPoint jobs. This issue is not caused if the remote renderer is configured with Microsoft Office 2010.
To resolve this issue, stop and start the remote renderer.
If the remote renderer is configured on Windows 8.1, Windows 2012, and Windows 2012 R2 server, then over the period of time, you might encounter consistent print failure. This is because the in-built pdf renderer might have stopped responding.
To resolve the issue, restart the remote rendering service using the following commands:
To stop the renderer, run iprntrendcmd -q
To start the renderer, run iprntrendcmd -l
Sometimes the remote renderer status might change to Inactive and activating it from the Management Console also fails to change the status.To resolve this issue, restart the renderer using the following commands:
To check the status of the service, run iprntrendcmd -s
To start the renderer, run iprntrendcmd -l
If you have a remote renderer associated with the iPrint Appliance, then upgrading the iPrint Appliance changes the remote renderer status to Inactive. To resolve this issue, follow the steps from Downloading the Remote Renderer to Registering the Remote Renderer to download, install, and register the new renderer.
The iPrint Rendering Service might hang with the service status “Stopping.”
This issue is caused when the remote renderer fails to restart when using the configuration or registration commands.
To workaround this issue:
Launch the Windows Task Manager.
Click the Processes tab.
Check the Show processes from all users box.
Right-click iPrint Rendering Service.exe, then click End Process.
Start the remote rendering service by using the iprntrendcmd -l command or through the window services panel.
After registering the remote renderer, self-signed and un-signed drivers are not installed.
To resolve this issue, run the command, iprntrendcmd -rt <FDN or IP Address>
On the prompt, accept the certificate for each driver.
The local renderer fails to print password-protected or corrupt PDF files.
You might get a message in the audit page that the job is complete or success message for email printing, if the local renderer uses the pre-packaged driver for printing.
When trying to print a document, the printer might print only junk characters in the following scenarios:
This issue is caused because the local renderer does not support all the font types. To resolve this issue, you can install the Microsoft TrueType fonts on your iPrint Appliance server.
Log in as root.
Type the following command to navigate to the fonts directory, then press Enter:
cd /opt/novell/iprintmobile/fonts/
Install the supported RPM files by typing the following command, then press Enter:
rpm -ivh *.rpm
The RPM files are now installed on the iPrint server.
Run the script to retrieve the fonts by typing the following command, then press Enter:
sh fetchmsttfonts-11.1-5.7.10-fetchmsttfonts.sh.txt
The fonts are downloaded from Sourceforge and installed on your iPrint server.
Few of the Linux drivers might fail to print due to absence of certain filters. You can verify this information, using the command: lpstat -p
The command displays the status of the drivers. Change the driver for which you have received the failure messages. This is applicable only for local renderer.
If the remote renderer is registered with Built-in-PDF Renderer for processing the PDF jobs, it might print junk characters for PDF files.
To resolve this issue, you need to reconfigure the remote renderer using iprntrendcmd -c command.
If the remote renderer is not registered for PDF file processing, the printer might print only junk characters and not the actual content. This can be caused by an incompatible printer driver.
To work around this issue, use the drivers that are compatible with your printer.
The remote rendering service might not start if the credentials provided are incorrect, or if the user account does not have the Log on as a service rights.
To resolve this issue, you must assign the Log on as a service rights to the user account with which you want to set up the renderer, on the local machine:
Go to Start > Control Panel > Administrative Tools > Local Security Policy.
In the left pane, double-click Local Policies.
Click User Rights Assignment.
In the right pane, under Policy, double-click Log on as a service.
Click Add User or Group.
Add the user account to the list, then click OK.
Click OK, then close the Local Security Policy window.
When rendering PDF files using Adobe Acrobat 11 Pro, Adobe Acrobat might stop responding and not complete the rendering process.
To work around this issue, kill Adobe Acrobat from Windows Task Manager, then try again.
When handling a large number of print requests, the remote renderer might not be able automatically delete the converted job data, and the disk space allocated for the remote renderer might fill up.
To work around this issue, you must manually delete the stored jobs.
Launch the command prompt.
Stop the iPrint Rendering Service manually using the command iPrntRendCmd -q.
Delete the files in the jobs folder located at C:\NDPS\Renderer\jobs.
Start the iPrint Rendering Service using the command iPrntRendCmd -l.
The iPrint Rendering Service might not work if the password of the user account associated with the service changes or expires.
To work around this issue, you must update the new password for the iPrint Rendering Service on the Services utility.
Click Start > Run.
Specify services.msc, then click OK.
Right-click iPrint Rendering Service, then click Properties.
Click the Log On tab.
Under This account, update the new password, then click Apply.
Click OK.
Right-click iPrint Rendering Service, then click Start or Restart to start the service.
When configuring or modifying the remote renderer, the iprntrendcmd command might stop responding.
To work around this issue, close the command prompt that is currently open, launch a new command prompt window, and then try the iprntrendcmd command again.
The remote renderer on iPrint Appliance does not provide an upgrade option.
This is a known limitation of the remote renderer in the iPrint Appliance 1.1 and earlier versions.
To resolve this issue, follow the steps from Downloading the Remote Renderer to Registering the Remote Renderer to download, install, and register the new renderer.