Troubleshooting

BARR/SPOOL

This topic contains solutions to common problems that you might experience with BARR/SPOOL.

See also:


Software starts in demo mode

Cause: The Barr Enterprise Print Server software was installed while the USB hardware key was installed. Because the Sentinel System Driver is automatically installed with the software, the USB hardware key must be removed during installation. According to Rainbow Technologies' Sentinel Driver Help file, "All USB Sentinel SuperPro keys need to be REMOVED before installing or removing the Sentinel System Driver. Otherwise, the USB portion of the installation might fail."

Solution: Reinstall the Sentinel System Driver without the hardware key installed.

  1. Remove the hardware key from the USB port.

  2. Open Add or Remove Programs utility and remove the Sentinel System Driver.

  3. Reinstall the Sentinel System Driver.

  1. Open Windows Explorer and browse to the \\Program Files\Barr\Spooler\Sentinel folder.

  2. Double-click Setup.exe.

  3. Follow the instructions in the Sentinel System Driver - InstallShield Wizard.

  4. Restart the computer.

Changes to user rights aren't taking effect

Cause: Changes to user rights do not immediately take effect unless the computer has been restarted. User rights will update automatically within one hour. This applies to changes made directly from the User Rights Configuration utility or changes to the users defined in Windows.

Solution: Wait approximately one hour and the rights will automatically update, or restart your computer for them to change immediately.

Receiving an error while attempting to upgrade the software

Cause: The product options you are trying to select do not match the key code options. Depending on your Barr Enterprise Print Server version, this could be related to BARR/SPOOL module enhancements.

Cause: The key upgrade was already applied successfully. Attempting to upgrade again will generate an error. There is no dialog box or message for this, but the Update number will increment.

Solution: Try one of the following methods to resolve your upgrade problem. For more information on Key Client, see the Using Key Client topic.

If the code still does not work, contact Barr Technical Support. In some cases, a special code can be generated to correct problems for older keys.

Receiving printing errors when the BARR SpoolCore service is started or upon exiting the Configuration Utility

Cause: The BARR SpoolCore service is attempting to send an initialization file to the printer, and Windows is displaying an error message because the printer is not available or not ready. An initialization file is sent to the printer when the BARR SpoolCore service is started or when the Configuration Utility is closed after configuring a printer to use an initialization file.

Solution: Do not respond to the pop-up error messages on the screen. The error message will disappear when you change the printer state to ready so that the initialization file can be sent to the printer.

Received files are not appearing in the Spool Window

Cause 1: The Spool and Retain folders are mapped to a Novell server.

Cause 2: The Spool directory is set to a mapped network drive. Drive mappings are specific to user profiles. When a new user logs on, the Spool directory will be invalid unless the mapping set is identical. If this user restarts the Barr SpoolCore service, all files in the Spool Window will disappear. This is because, although the Spool Window closes, the Barr SpoolCore service does not restart when a user logs off and another user logs on. Once the Barr SpoolCore service restarts, it checks the folder and receives an invalid name for that user profile.

Solution: Change the Spool and Retain folders to a non-mapped drive. Change the default folders by opening the Configuration Utility's Spool and Retain tab, browsing to Network Neighborhood, and selecting the desired folder. The name of the folder will now resemble \\SERVERNAME\Folder\Subfolder. This naming convention will work correctly.

Cannot remove the Barr software

Solution 1

Cause: The install.dll might be damaged or missing.

Solution: Complete the following steps to obtain and install a new install.dll file.

  1. Contact Technical Support at Barr Systems, LLC to obtain a new install.dll file.

  2. Open Windows Explorer. Navigate to the directory where the Barr software is installed and paste the new install.dll file into this folder. The default directory is \\Program Files\Barr\Spooler\Exe, unless an alternate path was specified during installation.

  3. From the taskbar, click Start | Run.

  4. In the Open box, type the directory where the new install.dll file is located, followed by the command Rundll32 Install.dll,UnInstallAll.

  5. Click OK. The uninstall program will begin.

If you are still unable to remove the Barr software, manually remove the Barr software.

Solution 2

Cause: An incorrect user might be attempting to remove the software.

Solution: If the software was originally installed on a network drive, the required install.dll file will exist in the user profile for the user that installed the software. You will need to log on and remove the software as the original user that installed the software.

Solution 3

Cause: The Barr Enterprise Print Server registry information might be corrupted.

Solution: Manually remove the Barr software.

After removing there is still an entry in the Microsoft Add/Remove Programs utility

Cause: Every time the Barr Enterprise Print Server is installed it adds an entry to the Microsoft Uninstall list in the system's registry. When it is removed, however, the uninstall program only removes the current entry. Therefore, if the product is upgraded to a newer version without first removing the previous version, there will be multiple version entries in this list and only one will be removed during the next install.

Solution: Complete the following steps to remove the old Barr entry key from the Microsoft Uninstall list.

  1. On the taskbar, click Start | Run.

  2. Type REGEDT32, and then click OK. The Registry Editor displays.

  3. Select HKEY_LOCAL_MACHINE | SOFTWARE | Microsoft | Windows | CurrentVersion | Uninstall.

  4. Delete the Barr version entries from the Uninstall key.

  5. Exit Regedt32 and restart your computer.

These steps require you to use the Windows Registry Editor. 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, we do not recommend that you perform this procedure. Please contact Barr Systems Technical Support and reference this topic to be walked through this procedure.

Windows stops responding and displays blue screens when BARR/SPOOL starts

Cause: This could be caused by BARR/SPOOL sending invalid or corrupt data to a Ready printer during Barr SpoolCore service startup. The potential for this problem exists when there are files in the spooler that are sent to printers as soon as the software starts.

Solution: To solve this problem, restart your computer, open the Windows Explorer, and remove all files from the Spool and Retain directories. In a default installation, this means deleting or moving all files and folders inside the following locations:

\\Program Files\Barr\Spooler\Spool\
\\Program Files\Barr\Spooler\Retain\

The system stops responding when attempting to print

Cause: One or more of the printers configured in the Spool Window are not physically connected. The Spool Window runs a check on all printers before printing, the system can stop responding if it does not locate all the printers.

Solution: Reconnect the printers, or remove the printers from the Spool Window if they are no longer connected. To remove a printer, highlight the printer on the Configuration Utility's Spool Printers tab, then click Remove.

BARR SpoolCore service monopolizes the central processing unit

Cause: There are too many files in the Retain folder. Windows will usually perform poorly if a folder contains an excessive number of files (for example, more than 2000 files).

Solution: Delete excessive files from the Retain Window. Modify the retain period so that files are stored less time in the Retain folder before purging. It is the number of files, not the size of files, that affects computer performance. If it is necessary to keep files for an extended number of days, consider backing up the retain folder in another location, and then deleting the jobs' folders from the Retain directory.

See also: Retain Window overview

Cannot find the Barr diagnostics file after running the Diagnostics utility

Cause: The default directory for the Barr diagnostics file is hidden. The Diagnostics utility writes the diagnostics file to the system-configured temporary directory. In later operating systems, the path for the diagnostics file is C:\Documents and Settings\Username\Local Settings\Temp\Barrdiag.bct. By default, Windows hides the Local Settings directory. Hidden directories cannot be viewed.

Solution: After you capture diagnostics, save the Barrdiag.bct file to a user-defined location by clicking Save As.

You can also use one of the following methods to make the hidden folders viewable.

Changing your viewing settings:

  1. Open Windows Explorer.

  2. Select Tools | Folder Options.

  3. On the View tab, select Show hidden files and folders.

  4. Click OK.

Using the Windows Run option:

  1. From the taskbar, select Start | Run. The Run dialog box displays.

  2. Type %temp%.

  3. Click OK. The Temp folder displays. The Barrdiag.bct file will be listed.

See also: Capturing diagnostics