24.9 Troubleshooting iPrint Migration

iPrint Service Does not Work After Transfer ID Process

Source: The iPrint service does not work after the Transfer ID process is complete.
Action: On completion of the Transfer ID process, confirm the following values:

  1. Go to /etc/opt/novell/iprint/conf/ipsmd.conf and change the PSMHostAddress value to the source server's IP address or DNS name (preferably a CNAME was used). Use the address that was used when you loaded with the /dnsname or /ipaddress switch. If you are unsure, view the name by which the iPrint printers are installed at the workstations.

  2. Change the eDirectory server1 value to a reliable eDirectory server address.

  3. Go to /etc/opt/novell/iprint/conf/idsd.conf and change the IDSHostAddress value to the source server's IP address or DNS name (which is now the target server's IP or DNS).

  4. Change the eDirectory server1 value to a reliable eDirectory server address.

  5. Go to /etc/hosts and ensure that entries are correct for the new identity.

  6. Go to /etc/opt/novell/iprint/httpd/conf/iprint_ssl.conf and update the AuthLDAPDNURL "ldaps://[address..]" to any reliable LDAP server.

  7. Go to /etc/opt/novell/iprint/httpd/conf/iprint_g.conf and update the address after the ServerName entry. Ensure that you choose the new identity IP address.

  8. Restart the Print Manager (rcnovell-ipsmd restart), Driver Store (rcnovell-idsd restart), and Apache (rcapache2 restart).

  9. Use iManager to test iPrint by using the Print Manager, Driver Store, and printers.

    If you encounter an error while managing the Print Manager, one of the certificates may need to be updated. To troubleshoot, see the Cool Solutions article “Certificate Re-creation Script for OES”.

Printers are not migrating to OES

Explanation: Occasionally the iPrint migration status is successful but the specified Print Manager is not active or is down, and so printers are not migrated to the OES server.
Possible Cause: Some other Print Manager is active or is already loaded on the OES server.
Action: On the OES server:

  1. Search for the ipsmd daemons by executing the ps ax | grep ipsmd command. This displays two running ipsmd processes.

  2. Kill the individual ipsmd daemons by executing kill -9 pid_of_ipsmd

  3. Restart migration by executing iprintmig.

Target server authentication fails in a cluster environment

Explanation: The loopback address is not authenticated.
Possible Cause: The loopback address is not being resolved to the IP address of the target server in the cluster environment.
Action: Enter the IP address or DNS name of the target server.

Printers are not migrating with the -f option

Explanation: iprintmig skips adding printers from the file containing the printer list.
Possible Cause: If the file with the printers to be migrated contains extra spaces or characters, the file is skipped by the utility.
Action: Delete the extra spaces or characters and restart the migration process.

Invalid driver path assignments

Explanation: Specific printers are not being migrated, and you see the error message XMLToDoCIMInstance::doWork(): CIMException encountered (general error) <Operating System Name> GetDriverInfo failed:<Printer Name> during migration.
Possible Cause: The printers are associated with deleted or missing drivers.
Possible Cause: The driver is associated with a remote path that no longer exists. The path can be a remote server or an unmounted volume.
Action: Verify the driver path and generate a report to correct the driver assignment:

  1. In iManager, select Manage Print Manager.

  2. Select an NDPS Manager.

  3. Click OK.

    NOTE:If the Print Manager is down, click Startup to change the status to Active.

  4. Click Printer Agents Configuration Report.

  5. Select one or more configuration options for the operating system name displayed in the error message.

  6. Click Generate Report.

  7. The driver assignment path is displayed for individual Printer Agents in the report.

  8. Verify that the complete driver path is a valid assignment.

  9. (Conditional) If the path is invalid, select Manage Printer and do the following:

    1. Choose a required printer under NDPS Printer Name.

    2. Click OK.

    3. In the Drivers tab, select the specific operating system for which the assignment is invalid. A message displays this message - The current driver does not exist.

    4. Click OK.

    5. Select either NONE or a suitable driver.

Printers are not migrating in the same eDirectory tree under the same context

Explanation: Printers are not being migrated, and you see an error message: CIMException encountered (general error): Creation of printer 'CN=<PrinterName>,o=<organization>' object failed. Object exists, but failed to get iPrintPrinterManager value.
Possible Cause: The migration was in the same eDirectory tree, and the source Print Manager and target Print Manager were under the same context.
Action: Use iManager to create a Print Manager on the target server in a different context. Restart the migration with the target Print Manager as the newly created Print Manager.

Migration fails even after a pre-check is passed

Explanation: When you restart the source server, the migration fails if the Print Manager was not successfully unloaded.
Possible Cause: The eDirectory attributes for the unloaded PSM are not cleaned up.
Action: Restart the Print Manager.

Migration fails when the Print Manager does not have a clean shutdown

Explanation: When the Print Manager does not have a clean shutdown, migration fails with an error message stating this is an invalid print manager on target.
Possible Cause: The eDirectory status for the Print Manager is not updated when the Print Manager shutdown is not clean.
Action: Restart the Print Manager.

Migration fails when a printer is assigned to a Print Manager

Explanation: The migration fails with an error message: CIMException encountered (general error): Creation of printer <Printer FDN> (Eg: cn=Printer1,o=novell) object failed. Object exists, iPrintPrinterManager value indicates that the printer is associated with another ipsmd.
Possible Cause: Trying to reassign a printer to a new Print Manager when the existing Print Manager assigned to this printer is down.
Action: Do not select the printer that is currently assigned to a Print Manager on the target server when it is down.

Migration fails when the SYS volume folder is not available on the source server

Possible Cause: The sys:ndps folder was renamed or deleted from the source server.
Action: Ensure that the sys:ndps folder is on the source server.

Migration fails for container admin credentials on the source server

Explanation: Printer objects with the container admin credentials are not being migrated.
Possible Cause: There is a mismatch between the source server and container admin credentials for the user. The source server might not be in the same container where full access rights are defined.
Action: Ensure that the user has the following rights and permissions assigned explicitly so that the user can access and execute psminfo.nlm:

  • The read permission to the sys:ndps folder on the migration source server.

  • Add the user as a trustee with supervisor rights to the source server NCP Server object.

Migration fails with an error message

Explanation: Migration fails with the following error message: 'OpenWBEM4::HTTPException' what(): Unable to process request: 401: Authentication failure Aborted.
Possible Cause: The admin user is not correctly LUM-enabled.
Action: LUM-enable the admin user:

  1. Run yast2 novell-lum from the command prompt.

  2. Click Continue.

  3. Enter the admin password.

  4. Click Next and follow the on-screen prompts.

The Driver Store and Print Manager are not initialized after migration on the target server

Explanation: The Driver Store and Print Manager are not initialized on the target server when SLP configuration is used.
Possible Cause: Problems in SLP configuration before starting migration.
Action: Enter the slptool findsrvs service:ndap.novell | grep <TREE NAME> command to list the TREENAME. If the tree name is not listed, fix the SLP configuration. For details, see Prerequisites.

Printers not coming up after Transfer ID migration

Explanation: You migrate printers by using the Transfer ID option, but printers are not coming up.
Possible Cause: Printers are not being associated with the drivers after a Transfer ID action.
Action: Use the following procedure:

  1. Run the /opt/novell/bin/ipsmd -x /tmp/psmimport_idswap.xml -s <Server IP Address> -u admin -f command on the OES 24.4 console.

  2. Enter the admin password.

Printer fails to install with the error “wrong printer URL”

Explanation: On successful migration, the redirected printers fail to install on the target server.
Action: If the iPrint service is configured with the IP address and if the source server is down, installation fails.

Ensure that the source server is up and running and then install the redirected printer.

Action: If the iPrint service is configured with DNS and the DNS is not resolved with the target server IP address, installation fails.

Ensure that the DNS is resolved to the target server IP address and then install the redirected printer.

Migration is completed with the status displaying as “Successful with warnings. Please refer the migration log”

Explanation: The message is displayed when the drivers associated with the printers are not migrated to the target server.

The printers are migrated, but you cannot install the printers for which the driver download or upload has failed.

Action: Check the migration log for the drivers that failed to migrate. Do not perform a migration; instead, manually upload or download those drivers to the target server.

Printers migrated from the source to target in the same context, are not migrated to the target in a different context

Explanation: When you migrate printers from the source to the target in the same context, then you restart the Printer Manager and try to migrate those printers again in a different context, the printers fail to migrate.
Action: Do not migrate printers in a different context if they have already been migrated from the source to the target in the same context.

Problems with accessing newly created printer agents after copying the padbtxt.xml file from the source to the target

Explanation: When you copy the padbtxt.xml file from the source to the /opt/novell/iprint/share directory on the target, the Migration Tool cannot access any newly created Printer Agents that were added to the source after copying the file.
Action: Copy the padbtxt.xml file from the source to the target everytime you create printer agents. When you select printers to migrate and migration passes successfully, but the printers selected for migration are still not migrated, one possible reason could be the presence of an outdated padbtxt.xml file in the directory. Remove the file and retry the migration procedure.

Redirections are not successful when printers are migrated

Explanation: When you redirect one printer to another on the source, migrate both the redirected printer and the other printer to the target, associate a driver to the redirected printer on the target server, then try to install the other printer from the target server, the printer installation fails. This is because this printer on the target server points to the redirected printer on the source, which does not have any drivers associated with it.