Novell Netware specific FAQ

Pcounter Global and Popup settings not saved with NT/2000/XP Client 4.83

There is a bug in the Novell Client 4.83 for NT/2000/XP which prevents SYS:PUBLIC\PCOUNTER.INI from being properly saved.  A patch has been issued which fixes this problem: http://support.novell.com/filefinder/14232/index.html

How to force users to authenticate using iPrint IPP

  • Login to iManager on the server: http://serverName:2200/
  • Expand the iPrint menu and choose Enable iPrint Access.
  • Enter the name of the NDPS Manager object.
  • Make sure that the Secure box is checked for each printer in question.
  • Press the OK button to save.

Error in NLM: Error -659 writing balance Description of error -659:

The time synchronization provided for use by NDS is not synchronized between the source and target servers. Background modifications to objects will fail when the target server has a modification timestamp higher than the source server. Information about server time synchronization: http://support.novell.com/servlet/tidfinder/10058645

Pcontrol error: Bindery mode is not supported on \\SERVER\QUEUE.

  • Queues which are selected in Pcontrol Network View, under the NetWare Servers section are referenced by Pcontrol as bindery queues. Bindery services are no longer supported in Pcounter 5.20 and later. This error will occur while opening a queue's Pcounter configuration or while trying to do a queue print history or report.
  • Since the Bindery is a subset of NDS/eDirectory, the same queue can be found in the NDS tree in Pcontrol Network view. All Pcounter options can be performed here.
    • Bindery
    NDS
    		  

    PPopup and/or Wbalance use default instead of configured settings

    All of the Pcounter Global and Popup settings are kept in SYS:PUBLIC\PCOUNTER.INI. Please make sure that users have read permission to this file.

    Popup does not appear on NDPS

    NDPS popups will not work on jobs retrieved from legacy queues. Please make sure that the printers in question are controlled access, PPopup will not work on public access printers. If the printers are controllled access, This can occur in situations where clients are configured to use multiple protocols, ie. both TCP/IP and IPX. Even if the clients are configured to use IP as the preferred protocol, this does not guarantee that NDPS will use the same protocol. For PPopup to work properly, it is necessary that the clients' NetWare/NCP and NDPS be using the same protocol. However, the NDPS Manager can be forced to use a particular protocol by using a simple command line option when loading NDPSM.NLM. Please see: http://support.novell.com/servlet/tidfinder/10063683 for more information.

    Wbalance uses numerical format Currency instead of Pages

    All of the Pcounter Global and Popup settings are kept in SYS:PUBLIC\PCOUNTER.INI. Please make sure that users have read permission to this file. Also, if users are logging into multiple servers, Wbalance may not be looking for PCOUNTER.INI on the expected server. If this is the case, then the following options will work:

    • Edit/Create WBALANCE.INI in the same directory as WBALANCE.EXE: [Preferences]FileServer=SERVERNAME
    • In Pcontrol, save the Pcounter Global Settings on any server which the user may connect to.

    Pcounter queue configurations are not being applied

    • If Pcounter is managing NDS queues, make sure that the queue configuration is not being done in bindery mode. To configure the queue in NDS mode, browse the NDS tree in Pcontrol Network View, select the queue, and press the P button on the toolbar. Alternatively, open the Pcounter server configuration in NDS mode, and on the Printing page, right-click on the queue and choose Configure queue.
    • The default queue configuration (on the Global Settings page of the Pcounter server configuration) is ignored by any queues which have had their own configuration previously saved. To have a queue use the server default queue configuration, open the Pcounter server configuration, and on the Printing page, right-click on the queue and choose Reset default values.
    • The Pcounter server configuration has a feature called Always check queue configurations on the Global Settings page. If this feature is selected, then queue configurations will be read for each print job. If it is not selected, then NDS traffic may be reducred, but it will be necessary to reload PCOUNTER.NLM in order for any queue configuration changes to be applied.
    • The queue configuration options Enable popup window, Hold all jobs, and Count jobs in advance are not dynamic, and require PCOUNTER.NLM to be reloaded.
    • If queues are added or removed from Pcounter server configurations, then PCOUNTER.NLM must be reloaded.

    Pcounter NDPS error: (Long) Error 899C getting VOL:\Path dir handle

    Pcounter uses 2 different methods to rename log files - if this error occurs then it will use another method. Generally this message can be ignored, and all functionality will still be intact.

    PCOUNTER.NLM error: Error -603 reading printer PrinterName configuration.

    No print queues are configured for counting. Please use Pcontrol to configure the NLM. If non-NDPS printers have already been configured for printing on another print server, then they should not be added to the Pcounter Active Printing mode list. Instead, queues which have already been configured for printing should be added to the Pcounter Queue Monitor mode list.

    • Run Pcontrol. In the Pcounter server configuration, on the Printing page, right-click on the printer and remove it from the list.
    • If the printer had been previously configured for printing with another print server, run NWAdmin and add the printer to the other print server's list of printers.
    • Add queues which have already been configured for printing to the Queue Monitor mode list.
    • Double-click on the queues to configure Settings, Prices, Rules, etc.
    • On the NLM Status page, reload PCOUNTER.NLM.

    Tektronix printer support in new Xerox NDPS gateway

    Please visit http://www.officeprinting.xerox.com. Select your printer model and search for NDPS.

    NDPSM.NLM 2.20e or later is unable to load (Error 1048577)

    The following error occurs only if Pcounter 5.10 was used. It is not an issue with 5.10a or later versions. Cause: Pcontrol 1.10 (included with Pcounter 5.10) was used to save the default Pcounter printer configuration in Global Settings, and a version of NDPSM.NLM prior to 2.20e was running. Problem: After updating to NDPSM.NLM 2.20e or later, it terminates with the following message: NDPSM-2.20-199 Error (1048577) occurred while initializing the Managed Object database. Program execution cannot continue normally. Solution:

    1. Restore the original version of NDPSM.NLM that was previously running and reload it.
    2. Run Pcontrol 1.10 (from Pcounter 5.10), select the NDPS Manager, right click, choose Pcounter Configuration. On the Global Settings page, select Default printer configuration and save.
    3. Download ndpsfix.exe, and from a Command Prompt, type: ndpsfix .ndpsManagerName.ou.o where ou.o is the context where the NDPS Manager is located. Include the dot before ndpsManagerName. This will delete the default printer configuration.
    4. Reload NDPSM.NLM 2.20e or later. It will be necessary to set the Pcounter default printer configuration again.

    Error FFFFFFFF or 89FF renaming PCOUNTER.LOG

    Typically this error occurs when Pcounter is configured to rename the log file daily and there is no print activity during a weekend or holiday. Therefore, there is no log file to rename and no need to be concerned when the message occurs.

    NLM terminates with error: "Loader cannot find public symbol: XXXX"

    This means that Pcounter is using a function which requires a support pack version that is later than the one currently being used. Please visit http://support.novell.com/filefinder/6385/index.html to get the latest NetWare support pack. If NetWare 4.10 is being used, get the updated CLIB and DSAPI libraries.

    Print jobs are recorded but not shown in histories and reports

    Print jobs are recorded differently in NDS and Bindery mode. Bindery objects are recorded by simple name only, while NDS objects are recorder by full canonical name (name.ou.org). If Pcounter Administrator (PAdmin) is running in Bindery mode, NDS objects will not be shown in reports, and vice-versa.

    • Make sure that Pcounter Administrator (PAdmin) is configured to read the correct log file location. Select Utility, Preferences, and select the file server where the Global Settings are stored.
    • To get a printer history/report from Pcontrol in NDS mode, find the printer/queue in the NDS tree, right-click, and choose Pcounter, Reports, or Pcounter, Print History.
    • To get a printer history/report from Pcontrol in Bindery mode, find the queue under the server in the NetWare Servers list, right-click, and choose Pcounter, Reports, or Pcounter, Print History.
    • To make sure PAdmin is running in NDS mode, select Utility, Switch to NDS mode, or select an NDS context in Pcontrol, right-click, and choose Pcounter, Accounting.
    • To make sure PAdmin is running in Bindery mode, select Utility, Switch to Bindery mode, or select a server in Pcontrol, right-click, and choose Pcounter, Accounting.

    Pcounter.nlm terminates with error: "Unable to authenticate connection - error -669 or FFFFFD63"

    We're not exactly sure what causes this error, but it can usually be fixed by setting the Pcounter print server's password in NWAdmin. Make sure that you set it the same as the password which was set in Pcontrol.

    Print jobs are identified by workstation instead of by user

    If ZENworks is being used, workstations are put into Workstation Groups, and Workstation Policies are applied, then Pcounter may see the workstation name as the print job owner.

    1. Run NWAdmin. Open the workstation group you would like to fix and select Associated Policy Packages.
    2. Select the Workstation Package and choose Details.



    3. Under the Default package schedule select Edit, Advanced Settings, Impersonation.
    4. Make sure that the drop down menu reads "Interactive User" rather than "System".



    5. As with most ZENworks Policy Package changes, the workstation should be restarted in order for changes to take effect.

    PCOUNTER.NLM: Error 899C attaching to queue

    Error 899C means that the print queue is not located on the server where Pcounter.nlm is running. The queue directories are located on specific volumes on specific servers. Pcounter must be configured and run on the server where the print queues are located. A queue's host volume is chosen when a queue is created, and the current volume/server for a queue can be viewed in Pcontrol, by selecting the queue, right-clicking and choosing Properties.