13.4 General Issues

13.4.1 Unable to customize iPrint maps

The existing maps cannot be modified on updating the iPrint Appliance server with the latest patches.To resolve this issue, edit the HTML tags in the existing maps and replace with the new tags.

  1. Open the iPrint map file in any HTML editor. For example, firstfloor.htm

  2. The snippet from the map file that needs modification:

    <html>
      <head>
        <title>
        </title>
        <meta http-equiv="content-type" content="text/html; charset=UTF-8">
        <style id="iprint_style">
          #ipp_printer { color: windowtext; font-family: sans-serif; font-size: 10pt; font-style: normal; font-weight: normal; }
    </style>
      </head>
      <body style="cursor: default;">
    
  3. Replace only the above snippet with the new tags, do not modify any other tags in the file.

    <html>
      <head>
        <meta http-equiv="content-type" content="text/html; charset=UTF-8">
        <style id="iprint_style">
          #ipp_printer { color: windowtext; font-family: sans-serif; font-size: 10pt; font-style: normal; font-weight: normal; }
    </style>
        <link href="styles/iprintappliance.css" rel="stylesheet">
        <script src="scripts/iprint.js">
        </script>
        <script src="../ippdocs/nls/en/iprntmsg.js">
        </script>
      </head>
      <body bgcolor="#ffffff" onload="OnLoadPDisplay();">
        <div id="instruction">
          <div id="instructionHeading">
          </div>
          <div id="instructionContent">
          </div>
        </div>
        <div id="BodyMainDiv" style="position: relative;">
        </div>
  4. Save the file and relaunch the map in the Map tool. You can now successfully modify the map.

13.4.2 Unable to upload Xerox GPD and HP UPD driver from iManager

The drivers cannot be uploaded due to out of memory issue. To resolve this issue, we recommend you to increase the Java heap size to 1GB for iManager.

Perform the following steps:

  1. In the /etc/opt/novell/tomcat6/conf/novell-tomcat6.conf file append the variable JAVA_OPTS with the value -Xmx1024M.

  2. Execute the following command to restart tomcat:

    rcnovell-tomcat6 restart

13.4.3 Fails to Print Jobs With Conversion Failure Error

If the printer drivers are faulty the jobs might fail with a conversion failure error.

To resolve this issue, reinstall the driver for that particular printer.

13.4.4 iPrint Appliance Migration Target Server SSL Authentication Fails

iPrint Appliance Migration target server SSL authentication might periodically fail.

To resolve this issue, close the miggui application and launch it again.

13.4.5 RPC Error When Enabling Printers for Mobile Printing

When enabling printers for Mobile printing using the iPrint Appliance Management Console, you might encounter an RPC error.

To resolve this issue, you can log out and log in to the iPrint Appliance Management Console if the browser session is open for a long time, or you can refresh the Printers page. If you are still seeing the RPC error, restart the Print Manager service, and then try to enable the printer for mobile printing.

  1. On a Web browser, use either the host name or the IP address to access the Management Console. For example, https://10.0.0.1:9443 or https://iprint.example.com:9443.

  2. Click the iPrint Appliance Configuration icon.

  3. Under Configuration, click Services.

  4. Select Print Manager.

    The Action and Options drop‐down menus are activated.

  5. Click the Action drop-down menu, then click Restart.

13.4.6 Email Printing Fails When the Filename Includes Extended Characters Or Double-byte Characters

Printing through email fails, if the name of the file includes either extended characters or double-byte characters.

To resolve this issue, rename the file to include only supported characters.

13.4.7 Unable to Configure Email Printing When SSL Is Enabled for IMAP/POP on a Mail Server

If SSL is enabled for IMAP/ POP on a mail server, you might be unable to configure email printing using the iPrint Appliance Management Console.

To work around this issue, you must manually import the mail server certificate into iPrint Appliance using the Management Console.

  1. On a Web browser, use either the host name or the IP address to access the Management Console. For example, https://10.0.0.1:9443 or https://iprint.example.com:9443.

  2. Click Digital Certificates.

  3. In the Key Store drop-down menu, select JVM Certificates.

  4. Go to File > Import > Trusted Certificate.

  5. Browse and select the mail server certificate, specify an Alias name, then click OK.

  6. Click Close.

  7. Click Reboot to reboot iPrint Appliance.

After iPrint Appliance reboots, configure email printing from the iPrint Appliance Management Console.

13.4.8 DataStore Creation Fails

When trying to create a DataStore, you might see a message: Failed to parse the XML file: XML document structures must start and end within the same entity.

To work around this issue, run the configuration script located at /opt/novell/iprintmobile/bin/config.sh.

If you are still seeing the error, you must reinstall iPrint Appliance.

13.4.9 Garbage Characters Printed When Printing from Gmail on Internet Explorer

If you are using Gmail on Internet Explorer and you try to print an email, you might see garbage characters in place of line breaks. This is caused by a character encoding issue.

To work around this issue, you must change the default text encoding to UTF-8 in your Gmail settings.

  1. Launch Internet Explorer, then go to www.gmail.com.

  2. Sign in to Gmail with your user name and password.

  3. Click the settings icon in the upper-right corner of the screen, then select Settings.

  4. Under General settings, in the Outgoing message encoding section, select Use Unicode (UTF-8) encoding for outgoing messages.

  5. Click Save Changes.

13.4.10 “Canceled by Operator” Messages in the Audit Logs

In the audit log files, you might see the following message:

Canceled by operator

This issue occurs if the files are not rendering correctly.

To work around this issue, ensure that the rendering service is active, and that the renderer is configured correctly.

13.4.11 Secure Printer Continues Printing after Changing the User Password (Local Appliance eDirectory Users Only)

When users change their passwords, secure printers might continue printing with the old password for up to 10 minutes. This is because of caching inside the iPrint LDAP authentication module, and affects only the users created inside the local eDirectory tree on iPrint Appliance.

To fix this issue, add the parameters LDAPDNCacheTTL and LDAPDNCacheEntries to the iprint_g.conf file, located at /etc/opt/novell/iprint/httpd/conf/iprint_g.conf as shown below:

To change the caching time to 30 seconds:

<IFModule mod_authnz_ldapdn.c> LDAPDNCacheTTL 30 </IfModule>

To disable caching:

<IFModule mod_authnz_ldapdn.c> LDAPDNCacheEntries -1 </IfModule>

After updating the iprint_g.conf file, launch the terminal window, and then restart the Apache service using the iPrint Appliance Management Console:

  1. On a Web browser, use either the host name or the IP address to access the Management Console. For example, https://10.0.0.1:9443 or https://iprint.example.com:9443.

  2. Click the iPrint Appliance Configuration icon.

  3. Under Configuration, click Services.

  4. Select Apache server for Novell for iPrint.

    The Action and Options drop‐down menus are activated.

  5. Click the Action drop-down menu, then click Restart.