NetStaff CS

Using the FileCabinet CS Virtual Office Print Driver

After downloading and installing the FileCabinet CS Virtual Office print driver, you can print from locally installed applications to FileCabinet CS in the Virtual Office CS or SaaS environment.

To print to FileCabinet CS in Virtual Office CS or SaaS, select FileCabinet CS Virtual Office as your printer when printing from locally installed applications. If FileCabinet CS is open in Virtual Office CS/SaaS, the FileCabinet CS Document Names dialog will open, which enables you to choose the drawer, the document name, and the document folder(s) in Virtual Office CS or SaaS. If you do not have any applications open in the Virtual Office CS or SaaS environment, you will receive the following message.

The document is successfully printed to Virtual Office, however... The document is not yet stored in FileCabinet CS. The transfer will occur when you are connected to Virtual Office running FileCabinet CS.

The next time you open FileCabinet CS through Virtual Office CS or SaaS from this workstation, FileCabinet CS will recognize that a document has been queued to print, and the FileCabinet CS Document Names dialog will open.

• Automatically accept printed documents after countdown
• Automatically accept printed documents (no countdown)

Troubleshooting tips

If you are running FileCabinet CS through Virtual Office CS or SaaS and receive a message stating that the job was printed and will finish the next time you open FileCabinet CS through Virtual Office CS or SaaS, follow these steps.

1. Verify that the CSVOXfr_client.dll is located in the C:\Program Files (x86)\citrix\ica client folder.  If this file is missing or in the wrong spot, you may get a message that the document was successfully printed to FileCabinet CS on Virtual Office CS but the document will not be stored in FileCabinet CS.  Reinstalling the print driver should create the CSVOXfr_client.dll file if it is missing.  If the file exists and you are still having trouble, then continue to step 2.  
2. Stop the print spooler by opening a command prompt (enter cmd in the Windows search field), entering Net Stop Spooler, and pressing ENTER.
3. Delete the following files from the C:\Windows\System32\Spool\prtprocs\w32x86\ folder.

   Notes

   • Do not delete any files that start with CSA; these files are for Engagement CS.
   • If you are running a 64-bit operating system, the files will be in the C:\Windows\System32\Spool\prtprocs\x64 folder.
   • csintprt.dll
   • csintprt.pdb
4. Start the print spooler by entering Net Start Spooler in the command prompt.
5. Test printing again to see if the issue is resolved before continuing to the next steps.
6. Uninstall the following items through Add/Remove Programs.
   • FileCabinet CS Virtual Office Print Driver
   • VO Citrix

     Note: If VO Citrix is not listed look for Citrix Receiver.

7. Remove any lingering ICA files and driver files.
   • Delete the following folders.
     • C:\Program Files (x86)\Citrix
     • C:\Users\%username%\AppData\Local\Citrix
     • C:\Users\%username%\AppData\Local\ICAClient
     • C:\Users\%username%\AppData\Roaming\Citrix
     • C:\Users\%username%\AppData\Roaming\ICAClient
8. Reinstall applications in the following order. (We recommended that you set your Windows User Account Control settings to "Never Notify").

   Note: If you are on a Windows 10 operating system, refer to Citrix Receiver and upgrading to Windows 10.

   • Citrix ICA Client
   • FileCabinet CS Virtual Office Print Driver

All attempts at prior printing will appear unless you clear the temp files. When you print to the FileCabinet CS Virtual Office Print Driver but you are not running FileCabinet CS through Virtual Office CS or SaaS, the print job is temporarily stored in the C:\Users\<username>\AppData\Local\Temp\CSVOXfr_workdir folder.

If the documents dialog won't open and you've completed the steps above, try entering regsvr32 "C:\WINCSI\CABINET\VOClient\CSVO_Cabinet_PageAdder_Client.dll" in the command prompt.

If you are still experiencing issues, see the Troubleshooting printing to FileCabinet CS from non-CS Suite applications topic for additional troubleshooting steps.

Share This