Bind to Printer Agent - Unknown Object

  • 7004605
  • 06-Oct-2009
  • 26-Apr-2012


Novell iPrint for Linux
Novell iPrint for NetWare
Novell iPrint Client for Windows


Print jobs are not processed quickly through the Print Manager.  Printing delays exist.  The ndpsmmon.log and PsmStatus Client Event log shows the following messages with great frequency:

Error Syntax:
[TimeStamp] , Operation: Bind to Printer Agent, 
Selection Error: Unknown Object Identification (no such object) ,     
User Name: .[UserCN].[OU].[OU].[O].
Address: [IPAddress],
Object Name: .[PrinterObjectName].[OU].[OU].[O].
Error Example:
2/12/08 03:21:52, Operation: Bind to Printer Agent, 
Selection Error: Unknown Object Identification (no such object) ,     
User Name:
Object Name:
Linux location of ndpsmmon.log 

NetWare location of ndpsmmon.log



Remove the printers listed in the error log from the workstations.  There are two methods to accomplish this task:

Method 1:  Manually Remove

Find the user workstation, open the Microsoft Printers and Faxes Window, and delete the printer. To help locate the workstation that has the printer installed which does not exist on the Print Manager, the log shows the name of the printer, the name of the user, and the IP address of the user's workstation.  This option is valid for NDPS installed printers and iPrint printers.

Method 2:  iPrint auto-removal of printers (valid only for iPrint printers)
  1. Using iManager, create a printer, which matches the name that appears in the log, to the Print Manager
  2. Delete the printer using iManager -> iPrint -> Delete Print Object
  3. View the printer in the iManager iPrint deleted list
    1. iManager -> Manage Print Manager -> Printer Agents Redirection -> Deleted Printer Agent Redirection
    2. Printers listed here will be auto-removed from workstations if they were installed as iPrint printers. 
      1. Note:  This feature doesn't work with NDPS installed printers.
  4. Monitor the logs (ndpsmmon.log or client event logs) and slowness symptom
  5. Over time, the logs should show the message with gradual infrequency.  If messages continue to appear, ensure that printer shows in the Deleted Printer Agent Redirection list.  If the printer exists in the deleted list and the logs, refer to Method 1 to remove the printer.
Method 3: NDPS auto-removal of printers (valid only for NDPS printers)
  1. Using the list of printers revealed in the ndpsmmon.log, create the "Unknown" printer object in the specified container.  Be sure to use the same name.
  2. Go to iManager - iPrint - RPM Configuration
    1. Select the top most container which holds (or its sub-containers) user objects with NDPS printers installed.
    2. Under "Printers to remove", click the "Add Controlled" or "Add Public" button. 
    3. Click Ok.
    4. Add the printers which are reported in the ndpsmmon.log.
  3. The next time the user logs onto the Windows desktop, that printer will be auto-removed.
  4. Once you feel confident that all users have rebooted their machines and have the printer removed from their workstations:
    1. delete the printer object using iManager
    2. remove that printer from the "Printers to remove" list.
  5. Periodically, check the ndpsmmon.log to verify the printer no longer shows up as Unknown.

Additional Information

The Windows Print Spooler frequently requests status of printers installed to workstations.  The frequency depends on which applications are open, the version of the Windows Print Spooler, and the operations being executed by the end user.  When printers installed to the workstation are in an error state, the frequency increases even more.   Each Windows Print Spooler status request against an iPrint printer installed to the workstation requires the iPrint client to query the Print Manager database for that printer and its status.

The condition described in this TID occurs when the printer does not exist in the Print Manager database, but is installed on the Windows workstation.  If many workstations are in this condition, the Print Manager is overly burdened with these requests, resulting in slow performance.

iPrint has a feature that avoids this problematic condition.  When a printer agent is deleted using iManager, the printer agent is added to the Print Manager database deleted list.  If a client requests status of a deleted printer, the printer is auto-removed from the workstation.  Similar technology does not exist with the NDPS client. 

To distinguish between iPrint installed printers and NDPS installed printers, view the printer name in the Windows Printers and Faxes Window. 
PAname on ipp://<address>
PAname on AdminDefinedName
NDPS installed printer as it shows in the Printers and Faxes Window:
PAname.ou.ou.o on TreeName