Troubleshooting printing to FileCabinet CS from non-CS Suite applications

Nothing occurs when printing and/or the FileCabinet CS Document Driver dialog does not open.
An error message related to printing is displayed.
The document does not appear in the appropriate location.
You are prompted to sign into FileCabinet CS each time you print. Refer to the Reinstalling the FileCabinet CS print driver section to resolve this issue.

Clear Print Jobs and Temporary Files

Select
Help
,
Repair
, then
Misc
.
Select
Reset Print Jobs
and attempt to print non-CS Suite documents again.
note
These options are not available if FileCabinet CS does not recognize that there is pending activity.

Browse to
X:\WinCSI\FcabSys\TmpPrn
, where X:\ is the drive to which FileCabinet CS is installed.
Delete the <UserID> folder if it exists, (where <UserID> represents the ID of the user experiencing the printing issue).
note
In future print jobs, FileCabinet CS recreates this folder automatically, as needed.
Print the non-CS documents again.

Open
Control Panel
.
Select
Administrative Tools
.
note
The options that are available depend on whether Control Panel is in Category, Small icons, or Large icons view mode.)
In Category view, select
System and Security
, and then
Administrative Tools
.
In the Small or Large icons view mode, choose
Administrative Tools
.
In Windows 11, Administrative Tools is called Windows Tools.
Select
Services
, and find
Print Spooler
in the list of services
Right-click
Print Spooler
and select
Stop
from the context menu.
When it's stopped, right-click again and select
Start
from the context menu.

Close all open applications.
Go to
C:\Users\<UserID>\AppData\Local\Temp
.
note
By default, the AppData folder is hidden, and you may need to make hidden folders visible on your workstation to select the folder, or you can manually type the path in the address bar in the file explorer.
Select all the files in the folder and then delete them. If you receive any messages that a file cannot be deleted because it is in use, select
Skip
.
You can use Ctrl+A to select all. You can select
Skip
after marking the checkbox for all current items.
Go to
C:\Windows\Temp
and repeat step 3 in this folder.
When the deletion is complete for both folders, empty your recycle bin and print to FileCabinet CS from a non-CS application.

Print driver isolation

Open
Control Panel
.
Select
Administrative Tools
.
note
The options that are available depend on whether Control Panel is in Category, Small icons, or Large icons view mode.)
In Category view, select
System and Security
, and then
Administrative Tools
.
In the Small or Large icons view mode, choose
Administrative Tools
.
In Windows 11, Administrative Tools is called Windows Tools.
Select
Print Management
from the list.
If
Print Management
is not available in Windows 11, you may need to take the following steps to install it:
Go to Windows
Settings
.
Select
Apps
.
Select
Optional features
.
Select
View features
next to
Add an optional feature
.
Enter
Print Management
to find it.
Mark the checkbox for
Print Management
and select
Next
.
Select
Install
.
In
Print Management
, select
All Drivers
.
Verify that the
Driver Isolation
column in the middle pane indicates
None
for the Filecabinet Solution driver.
If the driver does not show
None
, right-click the driver and select
Set Insolation
, then
None
.
If the driver indicates
None
, continue to the next troubleshooting step.

User Preferences

Select
Setup
,
User Preferences
, then the
Misc
tab.
Clear both the
Automatically accept printed documents
(
after countdown
and
no countdown
) checkboxes.
Select
OK
and print the non-CS document again.

Close FileCabinet CS on the workstation that is unable to print.
Go to to
X:\WinCSI\FcabSys
(where X represents the local drive on which the application is installed).
Rename the
ZFCUMSC.<UserID>
to
ZFCUMSC.<UserID>.old
file, or delete it.
Attempt to print the non-CS document again.

Default Printer

FileCabinet CS Print Service

Open
Control Panel
.
Select
Administrative Tools
(or
Windows Tools
if using Windows 11), the select
Services
.
Find the
FileCabinet CS Print Service
and confirm the startup type is set to
Automatic
, and the status is started or running.
If the Status is not started or running, right click the service, and select
Start
.
If the Startup Type needs to be updated:
Right-click the service and select
Properties.
On the
General
tab select
Automatic
from the
Startup Type
dropdown list, then
OK
.
If the service needed to be updated, attempt to print the non-CS document to FileCabinet CS again.

From the
Services
window, right-click
FileCabinet CS Print Service
and select
Properties
.
On the
General
tab, verify that the
Path to executable
is pointing to
C:\windows\csifcsvc.exe
.
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
.
note
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 CS Print Driver

Close FileCabinet CS if it's open.
Open
Control Panel
.
Choose
Programs and Features
.
Search for the
FileCabinet CS Print Driver
in the list of programs, and then right-click the item and select
Uninstall
.
Follow the prompts until the print driver has been uninstalled successfully. (The
FileCabinet CS Print Driver
should no longer appear in the list when the uninstall completes.)
Close the
Programs and Features
window, and then navigate to
X:\WinCSI\CABINET\DESKTOP
(where X represents the local drive where the application is installed) via Windows file explorer.
Right-click on the
Setup.exe
file, and choose
Run as Administrator
.
note
If you are running the application on a terminal server, be sure to place the server in Install mode prior to launching the
Setup.exe
file.
Follow the prompts to reinstall the desktop version of FileCabinet CS. Mark the checkbox for
FileCabinet CS Print Driver
in the Other Installation options.
When the installation is complete, the print driver should be reinstalled. Print the non-CS document to FileCabinet CS again.

On the workstation that is unable to print, open Windows
Start
menu and search for command prompt (cmd.exe).
Right-click the cmd.exe file and select
Run as Administrator
.
At the command prompt, enter the following command:
regsvr32 "X:\WinCSI\Cabinet\cscabsv.dll"
(quotations included, and where X:\ represents the local drive location where the application is installed), and press Enter.
You should receive the following message:
X:\WinCSI\Cabinet\cscabsv.dll succeeded.
When you receive this message, print to FileCabinet CS again.

Embeding vs. Printing

When you print a PDF to a CS Professional Suite application, the application generates an image for each page which may result in a substantial increase in file size. To avoid storage issues, we recommend that you embed PDFs in CS Professional Suite applications whenever possible. To embed a file from within FileCabinet CS, choose Object > Create from file.
When you print a PDF to a CS Professional Suite application or print an embedded PDF in an CS Professional Suite application to a printer, we recommend that you use the
Print as Image
option in Adobe's Advanced PDF print settings to ensure that all fonts are rendered properly.

Other troubleshooting tips

Reboot your computer and attempt to print again.
Verify that the server does not have disk quotas enabled. This can prevent documents from writing to file.
Permissions issues related to UAC, Local Administrator, and Windows file/folder permissions can affect printing to FileCabinet CS.
Verify permissions are set correctly.
note
If you are running the application on a terminal server, there are specific permissions and best practices to consider.
Third-party applications can cause a conflict that prevents the print process from completing successfully. Run Selective Startup using MSConfig to disable all non-Microsoft and startup services. Refer to the Perform a clean startup to determine whether background programs are interfering with your game or program article for further information.