NT_PrinterQueue does not find all print shares. (NETIQKB50713)

  • 7750713
  • 02-Feb-2007
  • 12-Nov-2010

Environment

NetIQ AppManager 6.x
NetIQ AppManager 7.0.x

Situation

NT_PrinterQueue does not find all print shares.
Error: 'Failed to retrieve printer queue info. Please check if mc run as NT domain account. Otherwise, printer name is invalid.'
NT_PrinterQueue is not able to enumerate the print queues.

Resolution

To determine the actual network or system issue preventing Windows from connecting to the specified printer:

  1. Log on to the Managed Client as the netiqmc service account.
  2. Click Start> Run.
  3. Enter cmd and click OK.
  4. Using the PrintServerName and PrintShareName values as specified in the KS parameters, execute the command:

    cmd /c net print \\{PrintServerName}\{printShareName} > c:\Progra~1\NetIQ\Temp\9999.tmp

When you determine the issue preventing Windows from connecting to the specified printer, you will know what action to take to resolve the issue, for example:

  • Use an NT Domain Account rather than LocalSystem for the netiqmc service account.
  • Specify the correct printer name or share.
  • Resolve the network or system issue as designated by Microsoft pertaining to the error message that is returned from running the net print test command.

Cause

A network or system issue is preventing Windows from connecting to the specified print server share. For example, the NetIQ AppManager Client Resource Monitor Service (netiqmc service) account might not have permissions to the specified print server share, or an incorrect printer name might have been specified.

Additional Information

Formerly known as NETIQKB50713

Note that this KS is not designed to monitor printers on the network. It is designed to monitor printers being hosted on the network by a given server. However, those servers must be set up as a local printer on that server for this KS to work. 

The KS might successfully monitor networked printers which are not set up as local printers on the server where this job is running, but if it is unsuccessful, set the printer as a local printer.