Pcounter Station
Copier accounting
Free Software
Order online


Pcounter NetWare FAQ #1

Setting up Pcounter for NetWare on Windows Vista

The Novell Client for Windows Vista will not include support for NDPS nor for Queue-based printing.

However, it is possible to get Pcounter utilities working on Vista (as they do on XP) by extracting files from the Novell Client for XP/2000. A batch file is available for download which automates the process of extracting the files from an XP client, and creating an install folder for a Vista client.

Download batch file here: GetVistaNDPSFiles.zip

After downloading, run GetVistaNDPSFiles.bat on an XP machine with the Novell Client installed and it will display further instructions.

This FAQ applies to:
Pcounter Pro
Plot Manager

Not required for:
Pcounter Administrator

Back to support page

Configuring Novell Remote Manager for use with PCOUNTWI.NLM web applications

Novell Remote Manager documentation

Controlling User Access to the Server through Novell Remote Manager

Changing the Default eDirectory Login Contexts Option

Synchronizing the eDirectory Context for Users Logging in to Novell Remote Manager

Back to support page

PCOUNTER.NLM load error: Loader cannot find public symbol: NetDBgethostbyname

Please LOAD NETDB.NLM before loading Pcounter.nlm, and then Pcounter.nlm will load properly.

Back to support page

How to use LPR and port 9100 with Pcounter and queue-based printing

  • Run Pcontrol (Network View) and select the NDS container, right-click, Create new queue.
  • Enter the new queue name and host volume.  The volume should be located on the server where Pcounter.nlm is running.  Assign to printer/print server can be left as (None).  This is the queue to which users will print for the new printer.
  • Double-click on the Pcounter server in Pcontrol (Network View) to open the Pcounter configuration and switch to the Printing tab.
  • Right-click on Pcounter Active Printing Mode, Create new printer, and enter the new printer name.  The printer should now appear in the Pcounter Active Printing Mode list.
  • Right-click on the new printer, choose Configure printer.
    • (9100) Choose Port=Appsocket, Pagecount Type=Manual.  Enter the printer's IP address and leave IP Port=9100.
    • (LPR)   Choose Port=LPR and enter the printer's IP address.  It may be necessary to check the printer documentation to determine the printer name (also known as LPR queue name).
  • Right-click on the new printer, choose Add queue to service.  Select the new queue created above.  The new queue should now appear below the new printer.
  • Double-click on the new queue to set the Pcounter settings for the queue.
  • Select the NLM Status tab and reload Pcounter.nlm.  The server will now have a new screen called Pcounter - Printer Control, which will display the printer status and allow additional controls.

Back to support page

How to force users to login to PCOUNTWI Account Balance and AuthJobs pages

The default behavior is to assume the identity of the logged in user at the client IP address.
It is possible to override this behavior and force users to login.

  • Edit \sys\public\pcounter.ini
  • Find the section: [HTTPServ]
  • Add the line:  RequireLogin=1
  • Restart PCOUNTWI.NLM

Back to support page

Pcounter Popup does not appear if a printer pool is defined

Please apply the Novell NDPSM patch for Pcounter (Post 6.5 SP2, 6.0 SP5, 5.1 SP7).

Back to support page

P Popup - Multiple popups for each job

Multiple repeated popups for each job may occur if clients are using non-secure iPrint.

In this case, the problem is that PPopup is using native NDPS protocols, and does not have the same job ownership permissions, since non-secure iPrint does not have a job owner.

It will be necessary to use either secure iPrint or native NDPS in order for PPopup to work properly.

Back to support page

P control error: "The network address is invalid. [1707]" when selecting NDPS printers

This error typically occurs if NDPS support is not installed, or was not installed correctly with the Novell Client.

To fix, reinstall the Novell Client with NDPS support.

Back to support page

PCOUNTER.NLM 5.20e load error: Loader cannot find public symbol: __I8M

This error only occurs on NetWare 4.x.
To fix, download pcounter.nlm, and replace the existing version in \SYS\SYSTEM.

Back to support page

PCOUNTER.NLM 5.20e sees no queues and will not load

In \SYS\PUBLIC\PCOUNTER.INI, add the following line to the [Global] section:


Then reload PCOUNTER.NLM.

Back to support page

PCOUNTDP.NLM uses excessive memory

This problem can be fixed by updating from NetWare 6 SP2 to SP3, and/or from NetWare 5.1 SP5 to SP6.

Back to support page

No broadcast messages are received from Pcounter for NDPS

  • Broadcast messages require a licensed connection number on a NetWare server.  However, NDPS and iPrint clients do not use, nor require a licensed connection.  Mounting a volume (mapping a drive) or printing to a legacy print queue on the NDPS server will open a licensed connection on that server.

  • Pcounter requires a fully qualified NDS username in order to detect any connection numbers associated with that user.  For native NDPS print jobs, this isn't a problem.  However, there is no way for Pcounter to resolve connection numbers from non-secure iPrint print jobs, because the NDS username is not known.  If users have a licensed connection, then it is possible to configure Pcounter to get the "real" print job username:
    • Run Pcontrol
    • NDPS Manager Pcounter configuration
    • Global Settings
    • Cross-Platform/LPD Options
    • Make sure that Find client IP address in server connection table is selected.

  • Users who have unlimited credit are not sent Account Balance notification messages.  This behavior is by design.

Back to support page

Pcounter Global/Popup/Registration settings not saved with Windows/XP Client 4.83

There is a bug in the Novell Client 4.83 for Windows/XP which prevents SYS:PUBLIC\PCOUNTER.INI from being properly saved.  A patch has been issued which fixes this problem:


Back to support page

iPrint Security

Each NDPS Printer Agent has three security levels, High, Medium and Low.  The behavior of the printer agent at each of these security levels is defined below:

  • Security = High.
    The printer agent retrieves the appropriate NDS user object.  The printer agent then determines the user's access level (None, User, Operator, ...) to the printer agent by accessing the roles assigned to that NDS user object.  All iPrint access to a printer agent at this security level requires SSL with user authentication so that the server side components can retrieve and validate the NDS user object.

  • Security = Medium
    Two behaviors are possible, depending on circumstance.
    • If an NDS user object is supplied, the printer agent trusts the NDS user object passed in by the application.  The printer agent then determines the user's access level to the printer agent by accessing the roles assigned to that NDS user object. 
    • If no NDS user object is supplied, the printer agent assigns an access level of User.

  • Security = Low
    No server side security is enforced.  This means that all users on the network have the equivalent of Manager access to the printer and can modify settings on the printer or manage any job sent to the printer.

More about NDPS security levels

When enabling a printer agent as an iPrint printer you have the choice of requiring SSL with authentication or not by checking the appropriate options in the IPP Support dialog.  The following table indicates the behavior of the iPrint print system as determined by the printer agent security level and the SSL/authentication requirement selected.

PA Security Level SSL / Authentication No SSL / Authentication
High Access Control Not Supported, Will return an error
Medium Access Control Access Always User Role
Low No Access Control No Access Control

If no access control is being enforced, the NDPS job owner typically appears as user@xx-xx-xx-xx-xx-xx, where xx-xx-xx-xx-xx-xx is the MAC address of the client.  In this case, it will be necessary to use one or more of the Cross Platform Options, found in Pcontrol, NDPS Manager Pcounter configuration, on the Global Settings tab. It is possible to:

  • Lookup the IPP client's IP address in the server connection table and apply the authenticated user at that IP address as the print job owner.
  • Search the tree for a username match.
  • Setup a map file which converts a simple name to a fully qualified NDS user name.

To enable IPP printing over SSL and require a valid ID and password to print, make sure that the printer agent's "Secure" box is checked in iManager.  When configuring a permanent desktop iPrint printer connection on a public computer (ie. used by more than one user), do not save the password when installing the printer. iPrint will ask the user again for credentials after the initial login.

Back to support page

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

Back to support page

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

    Back to support page

    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.

    Back to support page

    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.

    Back to support page

    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:

    • In Pcontrol, save the Pcounter Global Settings on any server which the user may connect to.

    Back to support page

    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.

    Back to support page

    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.

    Back to support page

    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.

    Back to support page

    Tektronix printer support in new Xerox NDPS gateway

    Please visit http://www.officeprinting.xerox.com.

    Select your printer model and search for NDPS.

    Back to support page

    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.

    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.

    After updating to NDPSM.NLM 2.20e or later, it terminates with the following message:

    Error (1048577) occurred while initializing the Managed Object database.
    Program execution cannot continue normally.


    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.

    Back to support page

    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.

    Back to support page

    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.

    Back to support page

    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.

    Back to support page

    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.

    Back to support page

    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.

    Back to support page

    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.

    Back to support page