Password
problem when NLM logging in as print server:-
Error -632 is referred to by Novell as "System failure".
Error -669 is referred to by Novell as "Failed authentication"
These are potential causes and solutions to this problem, in order
of preference:
- reset the password in Pcontrol and also through
NWAdmin/ConsoleOne.
- recreate the print server in NWAdmin/ConsoleOne instead of
Pcontrol.
- fix replicas, make sure they are up to date (dsrepair).
May be related to NDS not being replicated across all servers,
advisable to check replica's synchronisation.
|
Printing
working but not being counted:-
Possible cause is that the evaluation has expired.
Check in Pcontrol under server configuration and the "registration
and trial period".
|
Error
-603 when loading pcounter.nlm:-
In general means "No such attribute" in NDS.
With regards to Pcounter it could mean that the schema extensions
were not installed but more commonly it means that a Pcounter
configuration was not saved/found for the NDS object that the NLM is
trying to access.
Could be related to NDS not being replicated across all servers,
advisable to check replica's synchronisation.
|
Error
-603 when installing the schema:-
Means that the installer needs to be admin for the tree (root), not
just for a particular container.
It may be necessary to get some co-operation from the big, bad
admin of the tree!
|
Error
-601 adding queue in Pcontrol:-
In general means "no such object" in NDS. Likely that
Pcontrol is trying to assign an attribute to an object which the
calling user hasn't sufficient rights, or something like that. It's
hard to tell sometimes.
|
When
updating versions:-
There is no need to un-install first. New versions can safely be
installed over previous; so long as you are within your maintenance
licence period - otherwise the update will change Pcounter to be an
expired evaluation!
(To check this, use the Register link from the Global settings tab
in Pcontrol, Pcounter configuration).
Running Setup to install the software does not
automatically update the NLMs. These need to be updated using
Pcontrol.
Unload the NLM(s) - which can also be done from Pcontrol - before
updating, then re-Load.
All configurations are left as before the update.
But see below if NDPS!
|
Never
un-Load & re-Load the PCOUNTDP.NLM manually:-
This can cause stability problems on the server.
Un-Load & re-Load the Printer Agents or the NDPSM.NLM to
accomplish this.
Generally, to update the Pcounter NDPS NLM to a later version, you
will need to stop all printer agents that have Pcounter
accounting turned on & then restart them or else unload and
reload NDPSM.NLM. However, if there is a later release of NDPSM
contained in the update, this NLM should be unloaded & then
reloaded.
|
If
page-counting errors seem to be occurring:-
- Put the Printer/Queue on hold in Pcontrol.
- Print a job that causes the miscounting
- When the job is sat in the queue to be printed, please
highlight it on the right side of Pcontrol, R-click & Save
as...
- You can now take the Printer/Queue off hold.
- Please email the saved spool file & also the original
document.
|
No
Banner template files are available from the banner pulldown list:-
No Banner template files are available from the banner pulldown
list, although they do exist in SYS:\system\pcounter.
There is a problem in Win9x which prevents *.BAN from being shown
correctly in the drop down list for the banner files (you should see
them correctly on Windows) - but you can type in the file name manually.
|
How
does Pcounter work with NPrinter:-
Queue Monitor mode must be used; Pcounter's active printing mode
does not work with NPrinter, since Nprinter requires Pserver.nlm.
Make sure that Pcounter and Pserver are not using the same
print server object.
|
NDPS
accounting stops after installing a NetWare service pack:-
If after installing a NetWare service pack, Pcounter fails to
account for NDPS-based printing, please ensure that the accounting
check box for each agent is set - the install of the service pack
has been reported to reset this to off!
|
Pcounter
Popup - Client/Cost-centre billing:-
Popup Overview
Any Win32 station on the network can be
setup to have a window pop up after each print job, allowing users
to enter additional information for the logging of the job. All that
is necessary on the workstations is to run PPOPUP.EXE on each
station where this feature is required. PPOPUP is activated for each
printer by checking the Enable popup window box in the Pcounter
queue configuration. When a print job is submitted, Pcounter puts a
hold on the job until the user enters the information, and then
releases it.
For PPOPUP to automatically run when a user logs on, create a
shortcut to PPOPUP.EXE in Start Menu, Programs, Startup, or add
PPOPUP.EXE to a login script. If PPOPUP is launched from a login
script, use the following syntax: START DRIVE:PATH\PPOPUP [/options]
PPOPUP can display in English, French, German, Spanish, Portuguese,
Italian, Finnish, Dutch, and Swedish.
See PPopup Start_Up for
additional information.
Requirements
- The Novell Client is required on the workstation.
- The popup window settings are read from
\SYS\PUBLIC\PCOUNTER.INI on the default server, so users need
read permission to this file.
- The following Window types are supported;
Client code list, Entry Form, ID and Password, Matter number
list, Confirmation Popup. Certain users can be configured to be
exempt from Popup.
The following Window types are supported;
Client code list, Entry Form, ID and Password, Matter number list,
Confirmation Popup.
Certain users can be configured to be exempt from Popup.
|
Is
Pcounter still supporting Bindery and NetWare 3.x:-
Pcounter for NetWare Bindery version development has been
discontinued:
The Pcounter for NetWare 5.2x versions support NDS queues and
NDPS only. Version 5.13 is available for Bindery mode only - for
this release there will be no new features and only page counting
fixes will be issued.
|
I
am about to buy a new printer - will Pcounter work with it:-
I have installed a new printer - Pcounter doesn't seem to work
with it:-
Pcounter counts pages printed on any PostScript or PCL printer,
from all major manufacturers such as HP, Xerox, KonicaMinolta,
Lexmark, Canon and more. Also included are Ricoh RPCS, Canon
BubbbleJet, Epson (ESC/P, ESC/P2) inkjet and Epson (ESC/Page)
AccuLasers. This covers most lasers, inkjets and multi-function
devices on the market today. Support for TIFF printing is included
and Pcounter also tracks plot size on HPGL/2 and PostScript
plotters.
Note:
Any WPS (Windows Printing System) or GDI (sometimes also call
Host-based) printers - including some of the low-end models from the
above manufacturers - or printers not able to support the above
languages are not currently supported except
counting by job.
If you are unsure of the printer's support, please check the
Manufacturer's web pages for full protocol/emulation details.
|
Upgrading
from version 3 or 4:-
Summary of major differences and new features:
- Pcounter.nlm and Qcounter.nlm have been combined into one
NLM.
- Queues serviced are restricted to server where NLM is
running.
- Print server is required for bindery version.
- Log file can be written to any volume on any file server.
- Log file can be automatically renamed periodically.
- Default queue configurations on file servers can be used as a
template for new configurations and/or for existing queues.
- Cross platform (LPD/Mac) print jobs - map file is no longer
needed, Pcounter can search bindery or NDS tree for matching
usernames.
- Broadcast messages are editable and customizable.
- Popup information is stored in FoxPro DBF, new support for
subcodes, 20 selection memory. (Was called Pmax, now called
PPopup.)
- Waccount is replaced by PAdmin (Pcounter Administrator).
- PPopup and Wbalance are internationalized in English, French,
German, Spanish, Portuguese, Italian, Finnish, Dutch, and
Swedish.
NDS/Schema extensions: the Pcounter 4.x schema
extensions (from version 4.20 and later) are still in use. It is
necessary to apply the new schema extensions before saving Pcounter
5.x configurations. There are no problems with running Pcounter 5.x
on some servers & Pcounter 4.x on other servers but Do Not run
both on the same server.
Pcounter.log: the format of fields have changed. Rename any
existing logs to avoid mixing new and old entries. The Readable
format has been discontinued.
Queues: Configuration settings will migrate from 3.x to 5.x
Bindery and from 4.x to 5.x NDS. However, rules and paper size
prices did not exist in 3.x or 4.x - use default server settings for
all queues or define them for individual queues. Custom schema
balances may be applied to individual queues (instead of one per
print server) to enable multiple balances for multiple printers more
easily.
Printers: Many unnecessary or outdated settings have been
removed. Jetdirect (TCP) and TCP/IP Printer port
settings from 3.x/4.x will migrate to AppSocket on 5.x.
Server global and popup settings: all settings should
migrate directly.
On all upgrades: make sure that the Pcounter print server is
listed as a queue operator for all queues in service.
From Qcounter 3.x to Pcounter 5.x (Bindery): this list does
not migrate directly. On the Printing tab, select Queue monitor
mode, right click, and select Import Qcounter 3.x queue
list.
From Pcounter 3.x to Pcounter 5.x (Bindery): the printing
configuration will migrate directly along with the print server
being used for Pcounter.nlm.
From Qcounter 4.x to Pcounter 5.x (NDS): the queues counted
list will migrate directly along with the print server being used
for Qcounter.nlm.
From Pcounter 4.x to Pcounter 5.x (NDS): the printing
configuration will migrate directly along with the print server
being used for Pcounter.nlm.
Banners: some of the fields from versions 3.x and 4.x are no
longer used. If predefined banners were being used, please select
one of the new ones. If custom banners have been created, they may
need to be defined again.
|
