Troubleshooting printing to FileCabinet CS from non-CS Suite applications

Alerts and notices
Leave feedback

Internal Employees: Submit feedback

Contact information (optional):

Leave this blank:

Please tell us how we can make this information more helpful.


Characters left:

Through the use of the optionally installed FileCabinet CS Print Driver, you are able to print to FileCabinet from non-CS Suite applications, like Microsoft Office products, Adobe, your web browser, and more. Occasionally, you may run into issues where you are unable to print to FileCabinet from these non-CS Professional Suite applications.

This can manifest itself in a few ways:

There are few different local issues on your machine that can cause this to occur. Below are some troubleshooting steps you can go through to attempt to resolve this issue.

Clear Print Jobs and Temporary Files

If FileCabinet sees any pending print activity, it will give you the option to reset it.

Reset Pending activity

  1. Click on the FileCabinet icon in your computer's system tray or in FileCabinet, go to Help > Repair > Misc.

    Note: These options will not be available if FileCabinet does not recognize there is pending activity.

  2. Click on the button to Reset Print Jobs.
  3. Once that completes, attempt to print the non-CS documents to FileCabinet again.

Delete temporary FileCabinet print files

Even if the pending activity isn't showing in FileCabinet, there may still be temporary files that exist that can be cleared manually to resolve the issue:

  1. Browse out to X:\WinCSI\FcabSys\TmpPrn (where X:\ represents the drive where the program was installed)
  2. In this directory, delete the <UserID> folder if it exists (where <UserID> represents the ID of the user experiencing the printing issue). On future print jobs, the program will recreate this folder automatically as needed.
  3. Attempt to print the non-CS documents to FileCabinet again.

Restart the Print Spooler

In some cases, it may be helpful to clear the print spooler on your workstation, which can be done by stopping and starting the service.

  1. Go to Administrative Tools on the workstation and then select Services.
    • To access this on Windows 7, open the Start menu and in the search field, enter in Administrative Tools.
    • In Windows 8, click the Windows key + S, and in the search field, enter in Administrative Tools.
  2. In the Services window, scroll down to Print Spooler.
  3. Right-click on it and select Stop. Once it is stopped, right-click on it again and select Start.

Clear the local temp folders

Part of general workstation maintenance is occasionally clearing out the local temp folders. As these folders are a part of the process, it may be helpful to clean it out if you are experiencing issues printing to FileCabinet.

  1. Close all open programs.
  2. In the File Explorer on your machine, browse out to C:\Users\<UserID>\AppData\Local\Temp.
  3. Note: The AppData folder is hidden by default. You may need to make hidden folders visible on your machine in order to select it, or you can manually type the path in the address bar in the file explorer to get to the folder.

  4. In that directory, select all (Control key + A) and then delete.  If you receive any messages that a file cannot be delete because it is in use, select "Skip to all."
  5. In the file explorer, browse out to C:\Windows\Temp and repeat step #4 for this directory.
  6. Once the deletion is completed for both folders, ignore any remaining files in those location and then close out of the file explorer.  Be sure to empty your Recycle Bin afterwards.

User Preferences

There are certain settings in FileCabinet CS that can make it appear as if the the print job is failing, and in some cases, a corrupt user preference file may indeed cause it to truly fail. To resolve user preference related issues:

Disable "Automatically accept printed documents"

  1. To disable this setting in FileCabinet, go to Setup > User Preferences and click on the Misc tab.
  2. In that window, clear the two checkmark boxes for Automatically accept printed documents (for both after countdown and no countdown).
  3. Click the OK button and re-attempt to print the non-CS document to FileCabinet again.

Rename the FileCabinet CS user control file

If that doesn't resolve the issue, try renaming the FileCabinet user preference file for the user having the issue. To do this:

  1. Have the user close FileCabinet.
  2. Browse out to X:\WinCSI\FcabSys (where X:\ represents where you installed the program).
  3. Rename the file ZFCUMSC.<UserID>.
  4. Launch FileCabinet and attempt to print the non-CS document to FileCabinet again.

Default Printer

When printing to FileCabinet CS, the FileCabinet Print Driver references your workstation's default printer and driver in order to render the documents properly. As it may be related to any failures in this process, make sure you are using the manufacturer's most up to date driver, and/or consider switching your default printer to a different device or driver. For instructions on changing your Windows default print driver, see the following Microsoft topics for your appropriate operating system:

FileCabinet CS Print Service

Part of the install for the FileCabinet print driver is a print service. If the print service has been stopped or if it is not pointing to the correct executable file, this will cause any print jobs to FileCabinet to fail.

Start the FileCabinet Print Service

  1. Go to Administrative Tools on the workstation and then select Services.
    • To access this on Windows 7, open the Start menu and in the search field, enter in Administrative Tools.
    • In Windows 8, click the Windows key + S, and in the search field, enter in Administrative Tools.
  2. Once in the Services window, scroll down until you find FileCabinet CS Print Service and confirm it is started and that the Startup Type is set to Automatic.
    • If it needs to be started, right click on the service, and select the option for Start.
    • If the Startup Type needs to be updated, right click on the service, select Properties, and on the General tab of the next window, click on the drop down for Startup Type and select Automatic, and then click OK.
  3. If the service needed to be updated, attempt to print the non-CS document to FileCabinet again.

Verify "Path to executable"

If the service did not need to be updated, or if doing so did not resolve the issue, the service may not be pointing to the correct location:

  1. From the same services window, right-click on the FileCabinet CS Print Service and select Properties.
  2. In the General tab of the next window, confirm that the "Path to executable" is pointing to C:\windows\csifcsvc.exe.
  3. If it is not, this can be updated by launching the registry editor and correcting the path in the registry key HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\services\FCPrintService.

    Editing the registry should only be performed by your qualified IT professional as doing so incorrectly can cause critical issues with your operating system.

Reinstalling the FileCabinet Print Driver

If the above troubleshooting steps have not resolved the printing issues, the FileCabinet CS print driver may need to be reinstalled. Depending on the extent of the issue, this may need to be done multiple times and in multiple ways until printing to FileCabinet is successful again:

  1. First, with FileCabinet CS closed, launch the Control Panel on your computer and open Programs and Features.
  2. Once all the application list load, right-click on the FileCabinet CS Print Driver and select Uninstall.
  3. This will launch a FileCabinet CS Setup window. Follow the prompts in this window next until it states the print driver has been uninstalled successfully. When you return to the Program and Features, the FileCabinet CS Print Driver should be gone.
  4. Close that window, and through your computer's File Explorer, browse out to X:\WinCSI\CABINET\DESKTOP (where X:\ represents where the program is installed) and run the Setup.exe file there.

    Note: If on a terminal server, be sure to place the machine in Install mode before launching this file.

  5. This will again launch a FileCabinet Setup window to reinstall the desktop version of FileCabinet. Continue through this process, and during one of the prompts, be sure to checkmark the box for FileCabinet CS Print Driver under Other Installation options.
  6. Once this completes, print driver should be reinstalled and you can attempt to print the non-CS document to FileCabinet again.

If this reinstall was not successful, you may need to delete some FileCabinet CS Print Driver files manually first. After step 3 of the above process, delete any of the referenced files that you are able to find on your workstation in these locations:

Directory Path File Name
C:\Windows\System32\spool\drivers\x64\3 fcdrv.bud
fcdrv.dll
fcdrv.gpd
C:\Windows\System32\spool\prtprocs\x64 csintprt.dll
csintprt.pdb

Notes:

  • If on a 32-bit machine, rather than x64, the folder for each path will be W32X86.
  • You may need to stop the Print Spooler Service before deleting the above files. 

Once these files have been removed, restart the Print Spooler Service and continue the process above at step #4.

Manually register cscabsv.dll

When running the desktop setup, certain .dll files (including ones critical to printing to FileCabinet) are registered on the workstation. In some cases, especially if printing from CS Suite applications is also not working, you may have to manually register the .dll file responsible for integration:

  1. On the workstation having the issue, open on the Command Prompt as an admin.
    • On Windows 7, open the Start menu and in the search field, enter in Command Prompt. Right-click on it and select Run as administrator.
    • In Windows 8, click the Windows key + S, and in the search field, enter in Command Prompt. Right-click on it and select Run as administrator.
  2. In the Command prompt, type in the command regsvr32 "X:\WinCSI\Cabinet\cscabsv.dll" (with the quotations included and where X:\ represents where you installed the program) and then press the Enter key.
  3. If this command is successfully, you will get a pop-up message that states "X:\WinCSI\Cabinet\cscabsv.dll succeeded." When you receive this, you may attempt to print to FileCabinet again.

Note: If this command fails, either the .dll file does not exist, or the Windows user doesn't have the proper permissions to register the file (which could point to a bigger permissions issues).

Other Troubleshooting Tips

If printing to FileCabinet CS from non-CS Suite applications is still failing after following these steps, there are few possible steps and causes to consider:

Share This