Skip navigation
All Places > Knowledge Base & Downloads > Blog > 2013 > December > 19

When trying to install a package, the install fails with the error message "The printer driver is unknown".

The driver is included in the client installation package, and has installed successfully (no errors).
You can also create a printer manually with that print driver without any trouble.
This can happen if the driver's name string contains leading or trailing spaces in the .INF file.

Check your printer driver's .INF file to see if it contains leading or trailing spaces inside quotes.

If this is the case, you should be able to work around the problem by removing these spaces in every occurrence throughout the file.
Once this is done, reinstall the driver on the server and make sure your printers and queues are set to use the new driver.  It may be easier to remove the queues, printers, and the driver completely and re-create them to avoid mistakes.


NOTE: You'll need to rebuild the package.

A few different issues have recently been identified with Secure Release Here in the current 8.1 Print Server.

 

  • Jobs on one Print Server may not successfully delete from a station or terminal associated with another Print Server. Instead you receive this message:
    The print job is already being printed or deleted by the Print Server. Please refresh the view.
  • A color job on one Print Server may show with only the mono cost on a station or terminal associated with another Print Server.
  • A station or terminal on one Print Server that does not service any compatible queues may show jobs waiting in compatible queues from another Print Server. These jobs will not successfully release, however.

 

These problems have been fixed in the Print Server revision 60, available at Uniprint 8.1 Service Packs and Hot Fixes

What do I need to know about upgrading MSDE 2000 with Uniprint installed?

 

Before upgrading your MSDE installation, you should stop all Pharos services.


SQL Server 2000

On the Installation Selection page of the setup wizard, you should select the Upgrade option. If necessary, select the appropriate instance to upgrade. Typical MSDE installations will only have the default instance.


SQL Server Express

You must uncheck the "Hide advanced configuration options" checkbox on the Registration Information page of the installation wizard. Once you reach the Instance Name page, select the Default Instance radio button, and then check the box for your MSDE engine on the next page (in most cases, there will only be one checkbox). Continue through the wizard as per your requirements.


SQL Server 2005

Microsoft does not offer a direct upgrade path from MSDE 2000 to Server 2005. To move to 2005, you will need to first upgrade MSDE to either SQL Server 2000 or SQL Server Express as above.


Addional Information

Microsoft TechNet: Upgrading MSDE 2000 to SQL Server 2005 Express

When you print to a queue using an area charging job cost method, you may find the charge does not match expectations.

For example, an 8 inch long job on a 20 inch wide plotter will charge for 20 inches.

This is a limitation in the current area costing. As there is no way to determine which dimension of the job is the width versus the length, the system charges for the longest measurement.

A JobCost script can be used to alter this behavior, and an example is attached below. For sites that do not already use a costing script, this should be all that is required.

Note that the script requires some additional database setup - please read the documentation at the top of the script carefully.

Due to architectural changes in the job costing system, this workaround requires Uniprint 7.2.

I need to disable the SignUp Client on some of my workstations for maintenance, and don't want to uninstall.  How can I do this?

 

The process is different depending on the client operating system.

  • Windows XP clients:

    Change the following registry value to "MSGina.dll" instead of "NTGina.dll" and reboot.

    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\GinaDLL

    Change the value back to "NTGina.dll" to restore the client.

  • Vista and Windows 7 clients:

    Run this command as Administrator:

    regsvr32 "%PROGRAMFILES%\Pharos\Bin\SUCredentialProvider.dll" /u

    To re-enable the client, run:

    regsvr32 "%PROGRAMFILES%\Pharos\Bin\SUCredentialProvider.dll"

When the user tries to export a report in RTF format, they receive an error "Unable to export the report.  Failed to export the report".

 

Two Crystal Reports DLL files need to be registered using REGSVR32.

 

They are EXPMOD.DLL and CRTSLV.DLL, and are usually found in:

%PROGRAMFILES%\Seagate Software\Shared

Overview

 

The Pharos Omega PS150 can be configured with an optional magnetic swipe card reader. In some environments users have reported transient failures in card reader operation. This has been traced to RF interference between the card reader and other RF noise generating components in the environment (such as the PS150 SmartPAD and the MFP itself). It has been determined that grounding the Card Swipe Mounting Bracket used to attach the card swipe reader to the SmartPAD can significantly reduce this interference and resolve the problem. This document outlines the process of retrofitting an existing Omega PS150 with card reader to apply the grounding strap.

To obtain grounding straps please email support@pharos.com

Installation

Step 1: Remove one mounting bracket screw

 

Power off the Omega PS150 and unmount the Smart PAD. Turn the SmartPAD over to access the back. Remove the screw in the lower left that is used to mount the mounting bracket to the smart hub.

 

Step 2: Strip black coating from a screw hole on mounting bracket

 

Using a file or rotary tool expose the metal surface under the black finish coating around the opened hole. This ensures that the grounding strap makes electrical connection with the underlying metal. The black finish coat is an insulator.

 

Step 3: Attach flat connector of grounding strap

 

Using the screw removed in step 1, attach the flat connector of the grounding strap through the mounting bracket into the SmartHUB.

 

Step 4: Wind grounding strap wire on monitor cable

 

Wind the grounding strap wire loosely around the monitor cable.

 

Step 5: Connect bent connector of grounding strap to cable

Using the supplied screw, attach the bent connector of the grounding strap to the small screw hole in the monitor cable connector. You must disconnect the connector in order to access the screw hole. Once the grounding strap has been connected, reattach the monitor cable connector.

The problem occurs when a Pharos Station has an ITC magstrip reader (ITC1015) attached to debit funds from ITC cards.

Users can log on to the Pharos Station, see their jobs and see their correct unit balance. When a user clicks their job, it page counts correctly and displays the correct number of units to be debited.

The card is debited and the card goes out and comes back into the reader (for write verification).

At this point there is a pause, then the Pharos Station shows an error (Cannot write balance) that the card could not be debited and the job is NOT released. However the card is debited.
The ITC reader needs to be configured for use with a Pharos Station, rather than the ITC system.

Modifying the DIP switch settings inside the ITC card reader:

Dip Switch number 8 on Bank 3 needs to be in the OFF position for use with Uniprint.

Make this change and the ITC reader will work correctly with the Pharos Station.

The pagecounter returns "Custom" as the paper size for any paper sizes it does not recognize.'

If jobs are being reported as “Custom” when they should in fact be one of the standard paper sizes, you may need to create and configure the following registry key on your Print Servers:

HKEY_LOCAL_MACHINE\SOFTWARE\Pharos\Page Counter\Paper List

This string value can be set to a comma-delimited list of media sizes (e.g. “A3,A4,A5”) - only sizes in the list will be recognized. The order of the list is not important.

The reported size will be the smallest size on the list that is at least large enough to hold the page. If no size on the list is large enough, the media size will be reported as “Custom”.

1.  Obtain a copy of DebugView from this location:  http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx

2.  Run DbgView.exe on the Popup Client machine. Check the Capture menu, and be sure that "Capture Win32" and "Capture Events" are both enabled.

3.  Select "Log to File" from the File menu and provide a suitable filename.

The various Popup Client components will log to both the file and the DebugView window until DebugView is closed.

When adding a printer to a new Pharos Print Server, the Pharos Administrator might display the error message:

"Error adding printers in Administrator: Unable to load the list of print drivers. The RPC server is unavailable."

No network issues are apparent.
This occurs when the Printers folder is not visible on the network, because no printer has yet been shared on the system.

To resolve the issue, create a dummy printer on the new server and share it. The dummy printer can be deleted immediately, as long as the server is not rebooted before a real shared printer object (such as a Pharos Spool Queue) is added.

When you run the PharosLicenseUpgrader, you receive the following message:

The registry file name in [directory] doesn't look right.
Pharos License Upgrader cannot proceed.

 

This happens because the License Upgrader expects a site code of six letters followed by two digits. This error is shown when the upgrader finds a registry file that doesn't match this pattern. You might see this error in two cases:

1.  You have other registry files in either the same folder as PharosLicenseUpgrader.exe, or in your Pharos\Bin directory. In this case, it is recommended you move the upgrader executable and the correct license file to a new folder.

2.  You have a five letter site code. In this case, you can work around the issue by adding an extra letter to the registry filename.

For example: SCODE99.REG could be renamed to STCODE99.REG or SCODEX99.REG.

The filename must be exactly six letters, and two numbers.

Adding an additional letter to the registry file name will not affect your actual site code, and will not cause any trouble with license renewals in the future.

What impact do these orphaned spool files have, and how should I deal with them?

 

Sometimes the Windows Print Spooler service fails to delete a spool file when a job is removed, because some other process is still using the file.  The matching .SHD file is deleted, and the job is not displayed in the print queue, but the .SPL file still exists.

 

This has the potential to cause a problem when a new job is submitted via the Pharos LPD Server with the same ID.  The new job is created for the user, but the user receives the old job data instead.

 

This issue was addressed in Uniprint 8.1.  For older systems, a batch file can be scheduled to run periodically to detect and remove these orphaned jobs.  An example batch file is attached.

Clients can connect to Uniprint 8.1 services using the virtual server name or IP.

 

Clustered services that initiate outward connections will use the IP address of the active node as their source address, and not the virtual IP assigned to the cluster group.  Any firewalls that need to be configured (e.g. client firewalls allowing Cost Acceptance messages) will need to allow traffic from any of the individual nodes.

 

This is a known limitation of the current design, and is being reviewed for possible inclusion in a future release.

After an upgrade of the Popup Server, the Popup Client is upgraded but no longer works. A "connection timed out" error is displayed. Normal troubleshooting reveals no network connectivity problems.

 

The upgrade of the Popup Server may have failed. Check in the Windows Registry [HKEY_LOCAL_MACHINE\SOFTWARE\Pharos\..] for the Popup Server Installed Components key and verify that it is the correct build. Also, verify the version of the Popupsrv.exe file directly.


If not correct the upgrade failed and will need to be run again.

The 6.1 License Server fails to start after installation on a 2003 SP1 machine.


Logging returns only the message "caught a general exception" with no additional information.


The Data Execution Protection (DEP) feature in Windows 2003 SP1 is aborting the License Server process. This is covered in the Windows 2003 TechNote, but unfortunately not the one on the 6.1 documentation CD.


The LServer.exe must be configured as an exception to DEP (see the attached Windows 2003 TechNote for details).

After changing the Regional Settings for Currency, clients still receive Informed Print messages with the original format. How can I change Informed Print messages to use a different currency format?

 

The Pharos services by default run as LocalSystem. This account uses the Default User profile, so changes made while logged in as another user will not affect the services. The Default User profile can be adjusted by following these steps in the Regional and Language Options control panel applet, after you have made the required changes:

 

  • For Windows 2003 Server:
    i
    1. Select the Adminstrative tab.
    2. Enable the 'Apply all settings...' checkbox and click OK.
    3. Restart the Pharos Print Server service.
  • For Windows 2008 Server:
    1. Select the Administrative tab.
    2. Click 'Copy to Reserved Accounts'.
    3. Enable the checkbox for System Accounts and click OK.
    4. Restart the Pharos Print Server service.

The EDI URL changed in Uniprint 8.1.  Previously it was in this form:

http://server/PharosEdi/Pedi.asmx

 

The new form is:

http://server/PharosEdi/EdiService.asmx

 

Additionally, the pedi.wsdl file no longer exists.  The WSDL description of the service can be viewed through this URL:

http://server/PharosEdi/EdiService.asmx?wsdl

 

If your IMFP software does not allow you to specify an EDI URL, you may need to contact Pharos Support to obtain a newer version of the software.

When clients attempt to log on using the NT logon plug-in, they may be refused with a message saying the domain controller is unavailable. This may also be accompanied by unusual Kerberos errors in the event log, including a mention of KDC_ERR_BADOPTION.This can occur due to the emulation of NT4-style domains in a Windows 2000 or later Active Directory domain if the delegated NT4 authentication system is unavailable or cannot contact the AD domain controllers.

A good workaround is to switch to the Pharos Active Directory LDAP plug-in and bypass the NT4 system. Contact Pharos Support to obtain this plug-in.