Pcounter FAQs

Virus scan exceptions for Pcounter servers

"Please configure a Windows x64 machine from the desktop or terminal session"

How can I set the maximum allowable deposit amount?

I have deleted some Windows print queues and now cannot delete them from my Pcontrol Custom view. I get the message "Printer name is invalid".

I have generated a report and only see results from today or the last few days

Virus checkers can cause unpredictable behaviour

Jobs are allowed to print below a user's low balance limit

Moving the Pcounter share

Print jobs are printing but not being recorded in Pcounter.log

"User-mapped section open" error when updating Pcounter services

"Procedure number out of range" error when printing / "Array bounds are invalid" error when printing

How to set default datatype to RAW

Broadcast messages are not being received

Is my Pcounter licensed just by entering a new serial number?

Moving print jobs due to rules or load balancing fails

How to lock down Pcounter Administrator to a specific Active Directory OU  

How to obtain a sample spool file

Setting up Pcounter for NetWare on Windows Vista and Windows 7

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

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

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

Pcounter Popup does not appear if a printer pool is defined

PPopup - Multiple popups for each job

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

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

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

PCOUNTDP.NLM uses excessive memory

No broadcast messages are received from Pcounter for NDPS

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

iPrint Security 

Error in NLM: Error -659 writing balance

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

PPopup and/or Wbalance use default instead of configured settings

Popup does not appear on NDPS 

Wbalance uses numerical format Currency instead of Pages

Pcounter queue configurations are not being applied

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

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

Tektronix printer support in new Xerox NDPS gateway

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

Error FFFFFFFF or 89FF renaming PCOUNTER.LOG

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

Print jobs are recorded but not shown in histories and reports

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

Print jobs are identified by workstation instead of by user 

PCOUNTER.NLM: Error 899C attaching to queue 

HP NDPS Gateway - Downloads and Discontinuance Statement

How to check the Pcounter registration maintenance date

Printing-related usenet newsgroups

Pcounter Popup is hidden beneath other windows

Prices revert to zero after being saved

Multiple popups occurring from Excel print jobs

Pagecount errors on Canon BubbleJets

Print jobs are recorded but account balances are not modified

Running Pcounter utilities from login scripts

Users have enough credit, but print jobs are rejected with insufficient balance

Imported client codes are not displayed in Pcounter Administrator

Permissions required to manage users, balances, and client codes

Full name does not appear on banner

Date/currency formatting is incorrect

How to find out the meaning of an error code

How to delete all client codes and start again

PPopup client code list is empty

Dialog box fonts are too large on NT 4 

Does SETUP need to be run on each workstation in order to run Pcontrol or PAdmin?

Quick configuration summary (Windows)

Quick configuration summary (NDPS)

Quick configuration summary (NetWare queues)

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

Upgrading Pcounter for Windows

Upgrading Pcounter for NetWare (NDPS)

Upgrading Pcounter for NetWare (Queues)

Moving account balances and data between NetWare and Windows or between servers

Virus scan exceptions for Pcounter servers
It is recommended that the following files and directories on all Pcounter servers be made exempt from any virus scans.
C:\PCOUNTER
C:\Program Files\Pcounter for NT
C:\Windows\System32\spool\PRINTERS
C:\Windows\System32\PCNDATA.exe
C:\Windows\System32\PCOUNTER.exe
C:\Windows\System32\PCOUNTSP.DLL
C:\Windows\System32\PCOUNTUI.DLL
Active virus scans have been known to cause corruptions to spools and essential Pcounter files.

Back to top

"Please configure a Windows x64 machine from the desktop or terminal session"

How can I set the maximum allowable deposit amount?
In the file C:\PCOUNTER\PCOUNTER.ini (default location) add the following:
[PAdmin]
MaxDepositAmount=X
where X is the amount in pence, i.e. 100 = £1.00

Back to top

I have deleted some Windows print queues and now cannot delete them from my Pcontrol Custom view. I get the message "Printer name is invalid".
It is always best to remove printers from the custom view before deleting them.
If they have been deleted first, they can be removed from the following registry key:
HKEY_CURRENT_USER\Software\A.N.D. Technologies\Pcontrol\Custom
We do strongly recommend backing up the registry before making changes.

Back to top

I have generated a report and only see results from today or the last few days
This is a very common issue we see. It is not a fault - this is due to the report settings and the log file settings.
If your 'Report From' settings are 'Active Log File' only the current file will be taken into account when generating the report, so if the log has just changed only a few results will show.
Log files can be set to change Weekly/Monthly/Annually. As such, this is commonly seen on the 1st of the Week/Month/Year
To include previous logs in reports go to
Pcounter Administrator > Report Generator > Generator Preferences and set 'Report From' to 'Active Log Directory' or 'Custom Log Files List' and browse to the relevant log files

Back to top

Virus checkers can cause unpredictable behavior

Back to top

Jobs are allowed to print below a user's low balance limit
In the Pcounter printer configuration, make sure Action if below low balance limit = Delete job or
Pause job.
If the above setting is already in effect, make sure that the printer's spool setting is set to Start
printing after last page is spooled. If printing starts before the spool file is completely written,
Pcounter will not be able to determine the number of pages in the job before printing begins.
For the most accurate "before job" counting results, it is recommended that the default datatype be set to
RAW, if possible.  This can be set by making sure that Enable Advanced Printing Features is disabled

Back to top

Moving the Pcounter share
If the Pcounter data is to be moved to another location, then the Pcounter share on the
data server will need to be moved.
In Windows Explorer, find the directory location for the Pcounter Share, right-click, select Sharing.
Click the Not Shared button.
Run Pcontrol on the Data server, locate the Data server in Network View, right-click, select Pcounter Configuration.
On the Global Settings page, create the Pcounter share again in the desired location.

Back to top

Print jobs are printing but not being recorded in Pcounter.log
Has the printer been configured with a Pcounter port? If not, configure the Pcounter port through the printer's properties or by using the Pcounter Port Wizard in the Pcounter server configuration.
Verify that the Pcounter Data Server service is running and that the Pcounter print server is referencing the correct data server in Global Settings. If the data server has been changed since the Pcounter Printer Control service was started then you will need to restart the printer control service.
If the PCOUNTER share was created manually, instead of in Pcontrol, then the \\DataServer\PCOUNTER\DATA subdirectory may also need to be created.
Make sure that Pcounter Administrator (PAdmin) is also referencing the correct data server in Utility, Preferences, Global Settings. Also check Utility, Preferences, Reports/Print Histories in order to make sure that it is reading from the preferred log file.
Has your 60 day trial period expired? If so, print job data will not be recorded. You can request a trial period extension.
Make sure that the SYSTEM account has full control permission to the PCOUNTER share and the DATA subdirectory on the data server.
Check the Application Event Log on the data server. If there are any Pcounter errors, they will be recorded here.

Back to top

"User-mapped section open" error when updating Pcounter services
This error occurs if the Event Viewer is open and viewing the Application log. The Event Viewer reads event messages from service EXE files, preventing them from being deleted or replaced. Either close the Event Viewer or view the System or Security logs in order to update the Pcounter services.  Other monitoring software may also be using the event logs as well.
A workaround for this error is to install the services manually.  Please see the Pcounter for Windows Upgrade Guide, section 4 Troubleshooting and known Errors. 

Back to top

"Procedure number out of range" error when printing / "Array bounds are invalid" error when printing
This error can occur if the Pcounter ports and Printer Control Service versions are not the same version. Please make sure that all
Pcounter service and port versions are the same.
Run Pcontrol, Network View.
Find your server in the domain/workgroup,right-click, and select Pcounter, Configuration.
On the Services/Ports page, press Update
for each required component and restart the services.

Back to top

How to set default datatype to RAW
(Windows 2000/XP)
Open the Printer Properties.
Choose the Advanced tab.
Make sure that Enable advanced printing features is disabled1 

Back to top

Broadcast messages are not being received
Windows NT4/2000/XP/2003 workstations and servers
A recent Microsoft security bulletin was issued regarding vulnerabilities in the Messenger Service.  Applying this patch and/or other actions discussed in the bulletin, such as blocking NetBIOS ports or disabling the Messenger Service, will cause broadcast
messages not to be received.  The Messenger Service is required to be running on workstations in order to receive broadcast messages, and is required to be running on servers in order to send broadcast messages.
Windows XP SP2
SP2 disables the Messenger service during installation.
Windows 9x workstations
Windows 9x workstations require WinPopup or equivalent to be running, such as Awesome Popup.
Testing
(2.15 and later) Use the MSGDEBUG option from the Pcounter server command prompt:
pcounter msgdebug [userName or \\computerName]
Use the NET SEND command from the Pcounter server Command Prompt to test broadcast messages.
Pcounter Configuration
In the Pcounter server: Messaging Configuration (Pcontrol, Configure Pcounter Server, Global Settings,
Messaging Configuration), Pcounter can be configured to send messages to user names, workstation names, or both.

Back to top

Is my Pcounter licensed just by entering a new serial number? After entering a valid registration key in Pcontrol, please ensure that the two Pcounter services are restarted so that they pick-up the new maintenance codes.

Back to top

Moving print jobs due to rules or load balancing fails
If Advanced printing features is selected in the printer properties of the source printer, then it must also be selected in the printer properties of the destination printer in order for jobs to be moved properly.
However, if Advanced printing features is selected on the destination printer, then jobs will be moved properly regardless
of the setting on the source printer.
Turning off Advanced printing features sets the default spool datatype to RAW.

Back to top

How to lock down Pcounter Administrator to a specific Active Directory OU
Run Pcounter Administrator, and browse to the specific OU which should be locked down.
Quit Pcounter Administrator.
Run RegEdit and browse to the key: HKEY_CURRENT_USER\Software\Pcounter\PAdmin
Double-click on the value ADSContainer, and copy the contents to the clipboard.
 (Example: LDAP://CN=Users,DC=pcounter,DC=com)
Edit the shortcut used to launch Pcounter Administrator  (Example: C:\Documents and Settings\All Users\Start Menu\Programs\Pcounter for NT\Pcounter Administrator.lnk)
Edit target and add " LockOU=XXX" to the end of the target path, where XXX is the value pasted from the ADSContainer above.
 (Example: C:\Program Files\Pcounter for NT\NT\PADMIN.EXE LockOU=LDAP://CN=Users,DC=pcounter,DC=com)
Run Pcounter Administrator again.

If a virus checker is running which is monitoring the spool folders and other system areas, it can
cause conflicts with Pcounter (and other software). It is unnecessary to scan spool files for viruses -
even if no conflicts occur, CPU cycles are being wasted. Please configure any virus scanning software to ignore the spool folders.This message is displayed when trying to use Pcontrol to remotely access the Global Settings of another machine (server or workstation) running Pcounter.
This will appear for one of two reasons:
1. The source machine is x86 architecture (32-bit) and the target is x64 architecture (64-bit).
This will not be possible, you must open the Global Settings locally or from another x64 machine.
2. The target machine, despite being x86 architecture, has a C:\WINDOWS\SysWOW64 directory
Certain 3rd party applications are known to create such a folder regardless of the architecture of the machine onto which they are installed.
If this directory exists on an x86 machine Pcounter will consider it to be x64. Either rename or delete the directory.

Back to top

How to obtain a sample spool file

 Some none-standard drivers (such as GDI or host-based) can be difficult for Pcounter to obtain a correct page count from. More often than not these drivers are for low-end devices which are not specifically intended for network printing.

If you have a driver which Pcounter is having trouble calculating the pagecounts for you may be asked by Altman Technologies Support to provide an example spool file so that we can analyse the spool and create a fix for the specific driver family. The instructions for obtaining a sample spool file are:

First make the following changes to the printer in question:

1. On the printer properties > Advanced tab, uncheck "Enable advanced printing features".

2. In the same location, ensure that "Keep printed documents" is checked. This will keep a copy of the spool file after printing

3. In the same location, click the Print Processor button and chance this to WinPrint and RAW. 

Now monitor the issue and check the Pcounter log periodically for jobs that have the problem. If you find one, open the raw Pcounter.log in a text editor, and find the record in question. In the raw log it will look something like this:

ATL\CPieper,Test Page,\\CMP_D830\mpc6000,10/06/2011,13:05,\\CMP_D830,Altman Technical,,A4,/C/Jt=4/Cp=1/Mt=PLAINORRECYCLED/Ts=4DF2088A/ID=1A,67303,1,0.10,20.45

The field in red is the job ID field. This is a HEX number, merely used to identify the spool file. Once you have the ID of the job from the Pcounter log you can then browse to your spool folder and find the corresponding spool file. Default location of the spool folder on all Windows Server platforms is:

C:\Windows\System32\spool\PRINTERS\ 

PLEASE NOTE: whereas the ID in the log is a HEX number, the name of spool file will be the decimal representation of this number. For instance, highlighted above is 1A, the spool file will be called 26, or more precisely 00026.spl (1A-HEX = 26-DEC). This is the file you will need to look for. Take a copy of this and email to support@altman.co.uk. 

Back to top

Setting up Pcounter for NetWare on Windows Vista and Windows 7
The Novell Clients for Windows Vista/7 do not include support for NDPS nor for Queue-based printing.
However, it is possible to get Pcounter utilities working on Vista and 7 (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. Both x86 and x64 are supported.
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:
-Pcontrol
-PPopup
-Pcounter Pro
-Plot Manager
Not required for:
-Pcounter Administrator
-Wbalance

Back to top

Configuring Novell Remote Manager for use with PCOUNTWI.NLM web applications
Novell Remote Manager documentation
http://www.novell.com/documentation/oes/remotemgr/index.html?page=/documentation/oes/remotemgr/data/a7hjvxo.html
Controlling User Access to the Server through Novell Remote Manager
http://www.novell.com/documentation/oes/remotemgr/data/bqtzy2d.html#bx4teis
Changing the Default eDirectory Login Contexts Option
http://www.novell.com/documentation/oes/remotemgr/data/bqtzy2k.html#bqu37ru
Synchronizing the eDirectory Context for Users Logging in to Novell Remote Manager
http://www.novell.com/documentation/oes/remotemgr/data/ak1pbdy.html#bqsftde

Back to top

PCOUNTER.NLM load error: Loader cannot find public symbol: NetDBgethostbyname
Please LOAD NETDB.NLM before loading Pcounter.nlm, and then Pcounter.nlm will load pro

Back to top

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 top

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).
http://support.novell.com/cgi-bin/search/searchtid.cgi?/2969537.htm

Back to top

PPopup - 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 top

Pcontrol 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 top

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 top

PCOUNTER.NLM 5.20e sees no queues and will not load
In \SYS\PUBLIC\PCOUNTER.INI, add the following line to the [Global] section:
BypassSchemaExtensions=0
Then reload PCOUNTER.NLM.

Back to top

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 top

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 top

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:
http://support.novell.com/filefinder/14232/index.html

Back to top

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 = 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 = 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.

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 top

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 top

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.

Back to top

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 top

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 top

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.

Back to top

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 top

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 top

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 top

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 top

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:
Restore the original version of NDPSM.NLM that was previously running and reload it.
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.
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.
Reload NDPSM.NLM 2.20e or later. It will be necessary to set the Pcounter default printer configuration

Back to top

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 top

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 top

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 top

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 top

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.
Run NWAdmin. Open the workstation group you would like to fix and select Associated Policy Packages.Select the Workstation Package and choose Details.
Under the Default package schedule select Edit, Advanced Settings, Impersonation.
Make sure that the drop down menu reads "Interactive User" rather than "System".
As with most ZENworks Policy Package changes, the workstation should be restarted in order for changes

Back to top

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

Back to top

HP NDPS Gateway - Downloads and Discontinuance Statement
Please click on the following link:
HP NDPS Gateway - Downloads and Discontinuance Statement

Back to top

How to check the Pcounter registration maintenance date
- Run Pcontrol, Network View.
- Find and select the registered server, right click, choose Pcounter, Configuration.
- On the Global Settings tab, follow the link to Registration and Trial Period, and the registration information will be displayed.

Back to top

Printing-related usenet newsgroups
Windows XP: microsoft.public.windowsxp.print_fax
Windows 2000: microsoft.public.win2000.printing
Windows NT: microsoft.public.windowsnt.print
NetWare NDPS: novell.support.ndps-neps
NetWare queues: novell.support.netware.queue-based-printing
NetWare iPrint: novell.support.iprint

Back to top

Pcounter Popup is hidden beneath other windows
This should not be a problem on Windows 95 or Windows NT 4.0, but a change was made in later versions of Windows to prevent applications from stealing focus from other programs.
Open the registry key: HKEY_CURRENT_USER\Control Panel\Desktop
Set the REG_DWORD value: ForegroundLockTimeout to 0
This value can also be set using the optional TweakUI Control Panel - on the General tab, make sure that the option Prevent applications from stealing focus is not selected.

Back to top

Prices revert to zero after being saved
Typically this occurs if fractional/decimal prices are entered and the Global Setting option Numerical Format=Pages. If Numerical Format=Pages, then only whole number integer values are allowed for prices. To set the Numerical Format to Currency, open the Pcounter server configuration, and change the Numerical Format on the Global Settings page to Currency - then Pcontrol will save the decimal values in the price fields.

Back to top

Multiple popups occurring from Excel print jobs
Microsoft Excel prints each level of a worksheet as a separate print job. This can cause a popup to appear for each print job. Multiple popups can be overridden in PPopup, Preferences - make sure Process multiple jobs is selected. PPopup will handle all jobs resulting from a single Excel print request if the user waits until the last job is finished spooling before entering a response in the popup window.

Back to top

Pagecount errors on Canon BubbleJets
Pcounter supports page counting on Canon BubbleJet printers starting with versions 5.12g and 2.08a. Please consider updating your Pcounter version if BubbleJet accounting is required.

Back to top

Print jobs are recorded but account balances are not modified NetWare
- In the Pcounter printer or queue configuration, make sure that Accounting=User account balances and log file.
- Also in the Pcounter printer or queue configuration, make sure that the paper size prices are set to something other than zero.
- Make sure that the printer/queue configuration that you are applying is for the specified printer/queue object, and not the server default. The server default configuration only applies to a particular object if that object has not had its own Pcounter configuration saved. To restore an object's configuration to the default:
- Queues: On the Printing tab of the Pcounter server configuration, right-click the queue and choose Reset default values.
- NDPS: On the Printer Agents tab of the Pcounter NDPS Manager configuration, right-click the printer agent and choose Reset default values.
- (Queues) You may need to restart Pcounter.nlm if you have made changes to the configuration.
- Make sure that you have granted the Pcounter print server (NDS queues) or the NDPS Manager attribute rights in the top-level user containers so that Pcounter can modify account balances in NDS. This can be done in Pcontrol (Global Settings) or NWAdmin. If Pcounter has insufficient permission to modify balances, then all balances are interpreted as zero.
- Check the Error log: \sys\system\pcounter\errorlog.txt. If there are any Pcounter errors, they will be recorded here.
Windows
- In the Pcounter printer configuration, make sure that Accounting=User account balances and log file.
- Also in the Pcounter printer or queue configuration, make sure that the paper size prices are set to something other than zero.
- Make sure that the printer configuration that you are applying is for the specified printer, and not the server default. The server default configuration only applies to a particular printer if that printer has not had its own Pcounter configuration saved. To restore a printer's configuration to the default:
- On the Printers tab of the Pcounter server configuration, right-click the printer and choose Reset default values.
- Check the Application Event Log on the data server. If there are any Pcounter errors, they will be recorded here.

Back to top

Running Pcounter utilities from login scripts
Windows programs appear to be more stable when running from a local drive as opposed to a network drive. A good strategy for distribution is to keep the latest PPopup.exe and/or WBalance.exe version on a publicly readable network shared drive, copy them to a local drive, then run locally.
Login scripts or batch files will appear to hang when running Pcounter utilities such as PPopup.exe or WBalance.exe. This is because the script waits for the program to terminate before continuing. Instead of running the utility directly, precede the command with start or command /c.
Windows
@echo off
:: this xcopy command updates PPopup.exe from the Pcounter share
xcopy \\dataServer\pcounter\ppopup.exe "c:\program files" /d/y
start "c:\program files\ppopup.exe"
NetWare
It is best to create an external batch file which contains the utilities to run, for example \\ServerName\sys\public\pcounter.bat:
@echo off
:: this xcopy command updates PPopup.exe from the public directory
xcopy \\ServerName\public\ppopup.exe "c:\program files" /d/y
start "c:\program files\ppopup.exe"
Then add the following line to the login script:
(NetWare login scripts use a # before each external program.)
#\\ServerName\sys\public\pcounter.bat

Back to top

Users have enough credit, but print jobs are rejected with insufficient balance
NetWare
Make sure that you have granted the Pcounter print server (NDS queues) or the NDPS Manager attribute rights in the top-level user containers so that Pcounter can modify account balances in NDS. This can be done in Pcontrol (Global Settings) or NWAdmin. If Pcounter has insufficient permission to modify balances, then all balances are interpreted as zero. See also: Permissions required to manage users, balances, and client codes.
Windows
Make sure that the SYSTEM account has full control permission to the PCOUNTER share and the DATA subdirectory on the data server. Also check the Application Event Log on the data server. If there are any Pcounter errors, they will be recorded here.

Back to top

Imported client codes are not displayed in Pcounter Administrator
When importing a 2-dimensional client code list into PAdmin, make sure that each client code has its own record as well as associated subcode records.
For example, the following list will import 2 client codes with 2 subcodes each.
Note that the empty subcode field implies a client code record.
clientCode1,,description of clientCode1
clientCode1,subCode1,description of subCode1
clientCode1,subCode2,description of subCode2
clientCode2,,description of clientCode2
clientCode2,subCode3,description of subCode3
clientCode2,subCode4,description of subCode4
The following list will import 4 client codes with descriptions.
Note that the empty subcode field is still used.
clientCode1,,description of clientCode1
clientCode2,,description of clientCode2
clientCode3,,description of clientCode3
clientCode4,,description of clientCode4
This example is incorrect because there are no dedicated client code records.
clientCode1,subCode1,description of subCode1
clientCode1,subCode2,description of subCode2
clientCode2,subCode3,description of subCode3
clientCode2,subCode4,description of subCode4
This example is incorrect because the description field is in the wrong position.
There should be a blank subcode field in each record.
clientCode1,description of subCode1
clientCode1,description of subCode2
clientCode2,description of subCode3
clientCode2,description of subCode4

Back to top

Permissions required to manage users, balances, and client codes
Windows
Modify: Full control share permission to \\DataServer\Pcounter.
balances: Read/Write NTFS permission to \\DataServer\Pcounter\Data.
Run reports: Read share permission to \\DataServer\Pcounter.
Read NTFS permission to \\DataServer\Pcounter\Data. (Write permission required for writing log file when modifying balances.)
Modify client Full control share permission to \\DataServer\Pcounter.
codes:Read/Write NTFS permission to \\DataServer\Pcounter.
Novell NetWare
Modify balances (NetWare 4.x): Read/Write permission to All Properties in the top-level user context(s), or Read/Write permission to Account Balance, Allow Unlimited Credit, and Low Balance Limit properties of each user.
Modify balances (NetWare 5.x): Read/Write/Inheritable permission to Account Balance, Allow Unlimited Credit, and Low Balance Limit properties in the top-level user context(s).
Run reports: Read/File Scan permission to the Pcounter.log location. (Write permission required for writing log file when modifying balances.)
Modify client codes: Read/Write/Erase/Create/Modify/File Scan permission to the PPopup.dbf location.
How to grant permissions to properties in NWAdmin:
(Note: Low balance limit may be shown as Minimum account balance in other applications such as ConsoleOne.)
- Select a top-level user context, right-click, choose Trustees of this object.
- Press Add Trustee, and find the object to whom the permissions will be granted.
- (NetWare 4.x) under Property rights, select All properties and check Read and Write.
- (NetWare 5.x) under Property rights, select Account Balance, Allow Unlimited Credit, and Low Balance Limit, and check Read, Write, and Inheritable.

Back to top

Full name does not appear on banner
NT
Full names can be modified in User Manager, User Properties. In Pcounter Administrator, full names will be shown automatically if they have been defined.
NetWare
The Pcounter print server or NDPS Manager needs permission to read the Full Name property of all users. This property can be modified in NWAdmin, (select user), right-click, Details, Identification page. In Pcounter Administrator, full names will be shown if "Display fullnames" is checked in Utility, Preferences.
NetWare 4.x: Read permission to All Properties in the top-level user context(s), or Read permission to Full Name property of each user.
NetWare 5.x: Read/Inheritable permission to Full Name property in the top-level user context(s).
How to grant permissions to properties in NWAdmin:
- Select a top-level user context, right-click, choose Trustees of this object.
- Press Add Trustee, and find the object to whom the permissions will be granted.
- (NetWare 4.x) Under Property rights, select All properties and check Read.
- (NetWare 5.x) Under Property rights, select Full Name, and check Read and Inheritable.

Back to top

Date/currency formatting is incorrect
Windows
Pcounter services run in the context of the SYSTEM account, which has no user profile. Therefore the default system locale settings must be used. Make sure that the correct language/country is selected in Control Panel, Regional Settings. Restart the services if you make a change.
NetWare
If your registration (or trial period) permits, please use 5.10d or later. Otherwise the Pcounter NLMs will use the Windows locale settings (see Windows above) of the the machine which saved the Pcounter server configuration in Pcontrol.

Back to top

How to find out the meaning of an error code
Microsoft All errors:http://msdn.microsoft.com/library/en-us/debug/base/system_error_codes.asp
Novell NetWare All errors:http://www.novell.com/documentation/nwec/
Client/Requester (8800 to 88FF):http://www.novell.com/documentation/nwec/nwec/data/al2pcj4.html
Server (8901 to 89FF):http://www.novell.com/documentation/nwec/nwec/data/al2rw7q.html
NDS (-301 to -799):http://www.novell.com/documentation/nwec/nwec/data/alwxsrr.html

Back to top

How to delete all client codes and start again
Delete the popup database files PPOPUP.DBF and PPOPUP.CDX.
It is important that PPOPUP.CDX (the index file) also be deleted, or else the index will be out of sync the next time client codes are added.
If it is necessary to reset the client code user/group associations, the files PASSOC.DBF and PASSOC.CDX should also be deleted.
Windows
The files are located in the PCOUNTER share on the data server.
NetWare
The files are located in the directory specified in the file server's Pcounter Popup configuration.

Back to top

PPopup client code list is empty
First
Make sure that the user(s) have read permission to the directory where the client code database is stored. If the user presses the Reload list button and an Error -61 or Access denied message is displayed, then grant users read permission (write permission is not required) to the following location:
Windows: This is found in the Pcounter share on the data server: \\DataServer\Pcounter
NetWare: This is found in the location specified in the server Pcounter configuration, on the Popup page.
Second
In the server Pcounter configuration, on the Popup page, make sure that Associate client codes with network user and group names has not been selected. If this feature is enabled and no associations have been made in Pcounter Administrator, then all popup lists will be empty. Use client code associations only if it is necessary for users to be shown different lists of client codes. Otherwise turn off this feature, and everyone will see the same complete list of client codes.

Back to top

Dialog box fonts are too large on NT 4
Please download and install the Tahoma font:
http://download.microsoft.com/download/office97pro/fonts/1/w95/en-us/tahoma32.exe

Back to top

Does SETUP need to be run on each workstation in order to run Pcontrol or PAdmin?
No. If Pcounter is originally installed on a shared network directory, then any user with access permission to that directory can run the Pcounter programs. For ease of use, create a shortcut to the Pcontrol network location on the workstation.
Components can also be extracted from the Pcounter install directory, copied to workstations, with manually created shortcuts to the local file(s).
- Pcontrol - Pcontrol.exe and Pctrl*.dll
- Pcounter Administrator (NetWare) - NetWare\PAdmin.exe
- Pcounter Administrator (Windows) - NT\PAdmin.exe and NT\Andadlib.dll (for Active Directory support)
- Pcounter Administrator automation also requires Account.exe from the same folders above.

Back to top

Quick configuration summary (Windows)
Setup the Data Server
- In Pcontrol, select the Windows computer which will be the Data server and choose Pcounter configuration.
- Create the Pcounter shared directory - this is where all printing data is stored. Don't forget to set the appropriate permissions to the share and its contents.
- Set the Global and Popup settings.
- Select the Services/Ports tab and install the Data Server service.
- Press the Configure button if a new log file should be written periodically and/or configure custom account balance notification messages.
Start the Data Server service.
Setup a print server
- In Pcontrol, select the Windows print server and choose Pcounter configuration. A print server can also be the Data server.
- Set the Global and Popup settings - on the Global Settings tab, they can be imported from the Data server (or any other previously configured computer) so that they need not be entered again.
- Optional) A default printer configuration can be set which will apply to all printers which do not have their own configurations.
- Select the Services/Ports tab and install the port monitors.
- Select the Printers tab. Configure Pcounter accounting settings, prices, and rules on the required printers. Use the Pcounter Port Wizard or press the Properties button to create and configure Pcounter ports for the printers.
- Select the Services/Ports tab, install and start the Printer Control service.
- Start printing now!

Back to top

Quick configuration summary (NDPS)
After running SETUP, run Pcontrol and select the NDPS Manager where printers are to be monitored. The NDPS Manager can be found by browsing the NDS tree in Pcontrol and selecting the NDPS Manager from the context where it is located.
- Right click on the NDPS Manager and select Pcounter, Configuration (or press the P button on the toolbar) to configure the NDPS Manager.
- On the Global Settings tab, select Install server files.
- PCOUNTDP.NLM does not need to be loaded manually nor should it be added to AUTOEXEC.NCF. NDPSM will load it automatically as needed, when the printer agent is started up.
- Set the Global Settings. If many printers will be monitored, select Default printer configuration, which allows default settings/prices/rules to be specified for all printers. Press Apply to save changes before the NLM is loaded.
- Go to the Printer Agents tab. For each printer where accounting is required, select it. If a printer needs its own configuration which is different from the defaults set above, press the Configure button, and configure settings/prices/rules for the printer.
- Press Add Accounting so that the Pcounter NDPS accounting gateway NLM is loaded along with the printer agent. Shutdown and startup the printer agent to start accounting. The next time the printer agent starts up or the NDPS Manager is loaded, the Pcounter NDPS accounting gateway NLM will also be loaded.
- PCOUNTER.NLM is used for queue-based printing. It is not required to be configured nor used with NDPS.

Back to top

Quick configuration summary (NetWare queues)
After running SETUP, run Pcontrol and select the file server where queues are to be monitored. To configure a server in bindery mode, select a server from the NetWare Servers list in Pcontrol. To configure a server in NDS mode, browse an NDS tree in Pcontrol and select a server from the context where it is located.
- Right click on the server and select Pcounter, Configuration (or press the P button on the toolbar to configure the server.
- Set the Global Settings. If many queues will be monitored, select Default Queue Configuration, which allows default settings to be specified for all queues.
- Assign/Create a new print server object which is not being used on the network, exclusively for Pcounter's use.
- (Bindery version only) If Pcounter will be maintaining user account balances/quotas, make sure that accounting is installed on the accounting file server. Accounting is installed on NetWare 3.x using SYSCON, Accounting.
- (NDS version only) Install the Pcounter schema extensions. If Pcounter will be maintaining user account balances/quotas, make sure that the Pcounter print server has been granted attribute rights in the context(s) where the queue users are located.
- Select the Printing tab. Add existing queues which Pcounter should monitor to the Queue monitor mode list. If any queues require individual configurations, rules, and/or prices, set them here. For Pcounter to control the flow of data to printers, Pcounter active printing mode printers can be created with ports assigned to them and with queues to service.
- Press Apply to save changes before loading the NLM.
- Select the NLM Status tab. Copy the NLM and banner templates to the server. When using NetWare 4.10 or later, Pcontrol can be used to load and unload the NLM. Otherwise Pcounter is loaded from the file server console command prompt.
The command line syntax is:
(Bindery Version) LOAD PCOUNT3X
(NDS Version) LOAD PCOUNTER
Pcounter can run at server boot time by adding one of the above lines to the \SYS\SYSTEM\AUTOEXEC.NCF file.

Back to top

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 top

Upgrading Pcounter for Windows
- Close all currently running Pcounter programs on the desktop.
- After downloading, run SETUP. This will overwrite your existing program files and icons; however, this will not affect printing. To update the server components, please continue below.
- Run Pcontrol, Network View.
- Find your server in the domain/workgroup, right-click, and select Pcounter, Configuration.
- (Print Server) On the Services/Ports tab:
- Stop the Pcounter Printer Control Service.
- Update the Pcounter Port.
- If the port is being updated from 2.15 or earlier, to version 2.20 or later, first install the Pcounter Port and then update the old ports.
- Update the Pcounter Printer Control Service.
- Start the Pcounter Printer Control Service.
- (Data Server) On the Services/Ports tab:
- Stop the Pcounter Data Server Service.
- Update the Pcounter Data Server Service.
- Start the Pcounter Data Server Service.
- See also: "User-mapped section open" error when updating Pcounter services
- Generally, newer versions of server software are backward-compatible with older versions of PPopup, so it is not necessary to update PPopup.exe. However, if the upgrade is intended to address any PPopup issues or new PPopup features, then PPopup.exe should be updated on client workstations.
- If "User-mapped section open" error is occurring, close Pcontrol.
- Open the Services Control Panel.
- Stop Pcounter Data Server service.
- Stop Pcounter Printer Control service.
- Stop Spooler (and dependent) services. Examples of dependent services are Print Server for Macintosh and TCP/IP Print Server.
- Copy the following files from the Pcounter program directory (typically C:\Program Files\Pcounter for Windows\NT\Server) to the Windows\System32 directory:
- PCOUNTER.EXE
- PCNTDATA.EXE
- PCOUNTSP.DLL
- PCOUNTUI.DLL
- Start Spooler (and dependent) services.
- Start Pcounter Printer Control service.
- Start Pcounter Data Server service.

Back to top

Upgrading Pcounter for NetWare (NDPS)
- Close all currently running Pcounter programs on the desktop.
- After downloading, run SETUP. This will overwrite your existing program files and icons.
- Run Pcontrol, Network View.
- Find the NDPS Manager in the NDS tree, right-click, and select Pcounter, Configuration.
- On the Global Settings page, select Install server files.
- Either restart NDPSM.NLM, or else shutdown all Pcounter printer agents and start them up again.
- Generally, newer versions of server software are backward-compatible with older versions of PPopup, so it is not necessary to update PPopup.exe. However, if the upgrade is intended to address any PPopup issues or new PPopup features, then PPopup.exe should be updated on client workstations.

Back to top

Upgrading Pcounter for NetWare (Queues)
- Close all currently running Pcounter programs on the desktop.
- After downloading, run SETUP. This will overwrite your existing program files and icons.
- Run Pcontrol, Network View.
(NDS Pcounter.NLM) Find your server in the NDS tree, right-click, and select Pcounter, Configuration.
- (Bindery Pcount3x.NLM) Find your server in the NetWare Servers list, right-click, and select Pcounter, Configuration.
- On the NLM Status page, press Install server files.
- Restart Pcounter.NLM.
- Generally, newer versions of server software are backward-compatible with older versions of PPopup, so it is not necessary to update PPopup.exe. However, if the upgrade is intended to address any PPopup issues or new PPopup features, then PPopup.exe should be updated on client workstations.

Back to top

Moving account balances and data between NetWare and Windows or between servers
- Moving balances between NetWare servers on the same tree
Since balances are stored in NDS, the only action required is backing up and restoring of NDS partitions - which is outside the scope of Pcounter.
- Moving balances between NetWare servers on the same tree
Since balances are stored in NDS, the only action required is backing up and restoring of NDS partitions - which is outside the scope of Pcounter.
- Moving balances between Pcounter 2.x for Windows and 5.x for NetWare, or Pcounter 2.x data servers in different domains
In Pcounter Administrator, select Utility, Save all Balances.
This will save a batch file which can be used with Account.exe later to reset the account balances again.
Locations of Account.exe:
- NetWare: d:\PcounterInstallDir\NetWare\Account.exe
- Windows: d:\PcounterInstallDir\NT\Account.exe
Before running the batch file in the command prompt, set the path to include the directory where Account.exe is located.
Example:
@ECHO OFF
PATH d:\PcounterInstallDir\NetWare;%PATH%
BALANCES.BAT
Moving balances between Pcounter 3.x/4.x for NetWare and Pcounter 2.x for Windows or 5.x for NetWare
In WAccount, select Statistics, View all Balances.
This will create a text file which you can convert into a batch file which can be used with Account.exe later to reset the account balances again.
The text file will look like this:
admin 14.00
john 166.28
mary 15.90
The modified batch file should look like this:
d:\path\ACCOUNT.EXE balance admin 14.00
d:\path\ACCOUNT.EXE balance john 166.28
d:\path\ACCOUNT.EXE balance mary 15.90
Moving data between Pcounter 2.x for Windows data servers
Once the Pcounter share has been created on the new data server, just copy all files including subdirectories from the old data server to the new data server, ie. from \\oldDataServer\Pcounter to \\newDataserver\Pcounter. Please also see notes regarding account balances above.
- Moving client codes from Pcounter NetWare to Windows
Copy PPopup.DBF and PPopup.CDX from the Popup Database Location specified in the Pcounter NetWare server configuration, to the Pcounter share on the new data server, ie. to \\newDataserver\Pcounter.
- Moving data between Pcounter 5.x for NetWare servers
- Copy \sys\system\pcounter\*.* (Support files) between servers.
- Copy \sys\public\pcounter.ini (Global Settings) between servers.
- In Pcontrol, run the Pcounter configuration for the new server and make sure that any log file and/or popup database location references from the old server are changed to locations on the new server. Then copy the affected files from the old server to the new server.

Back to top