This topic contains solutions to common problems that you might experience with Print Utility.
Unable to use Print Utility to pull files from a Novell directory
Errors occur when importing files that require ASCII to EBCDIC conversion
Cannot receive data using Print Utility or BARR/PRINT TCP/IP
Receiving an error message in Print Utility while spooling a file
Characters are printing in the wrong font, upside down, or backward
Cause: This problem could have a variety of causes. All of the symptoms, however, deal with how the user is defined to the network and specifically the rights that are given to that user.
Solution: All of the following items must be checked to ensure that the BARR Print Utility service will be able to properly access files on your Novell Server.
The BARR Print Utility service must be set to log on to the Novell Server as a user and not a system account. The user name and password that is used must have full access rights, (read, write, and delete), to the Novell folder where the files are kept. Please note that some Novell clients such as Novell IntranetWare Client for Windows allow users to specify different log ons for their Windows server and for their Novell server. The user name and password that you specify in the BARR Print Utility service must have logon access to the computer that you are working on, your Windows server (if you have one), and your Novell server to which you are trying to gain access.
If you are using the same user name and password for the BARR Print Utility service that you used to log on to Windows, then your user account must support multiple connections on the Novell server. Ask your Novell administrator if your account supports multiple connections.
Make sure there are enough licenses available on the Novell server, or the BARR Print Utility service will not be able to log on.
See also: Services overview
Cause: The necessary code pages are no longer properly registered in Windows.
Solution: Check the code page settings in the Print Utility, LPD, or TCP/IP socket setup. Generally if you are receiving standard ASCII files, text files with ASA carriage control, or files originally spooled using Barr DOS products, the incoming code page value must be 437 and the outgoing code page must be 37. If these values are not included in the drop-down list, they are no longer registered correctly with Windows.
First, check to make sure the proper code page file is present in the \Winnt\System32 directory. The file for code page 37 is C_037.NLS, other code pages follow the same naming convention. If the file is present, but still not appearing in the list, it has probably been removed from the Windows registry. To reregister it, the correct key needs to be added to the Windows registry.
The system registry contains information about how
your computer runs, and your computer might not work if there is an error
in your registry. If you are unfamiliar with the Registry Editor, please
contact Barr Systems Technical
Support and reference this topic to be walked through this procedure.
Cause: SYSIN data included after the //SYSIN DD *. JCL files are treated as 80 byte files when designated as SYSIN files in Print Utility.
Solution: Send the JCL file with an embedded command A command placed in a text, graphics, or other document file, often used for printing or page-layout instructions. Make sure you use the /An format, where n is the record length. The record length value can vary from 1 to 255.
Cause: The file’s input format is set incorrectly in Print Utility.
Solution: On Print Utility’s Format tab, select the correct input format for the file being spooled.
Cause: Fonts may be incorrectly converted when data is received by LPD or read with Print Utility. By viewing the job in the Spool Window and verifying the hexadecimal values of the first data byte of each line, you can determine if fonts were incorrectly converted. If the hexadecimal values of the first data byte of each line are not the expected values, translation has taken place.
Solution: Code pages determine the translations that take place within the Barr software. Use the Code Page Editor to set up a custom code page for jobs received by LPD or read with Print Utility.