FileCabinet CS

FileCabinet CS: Application does not open or start

There are instances where FileCabinet CS will not open or start. Sometimes, no error message is displayed after attempting to launch FileCabinet CS. Many of these issues are due to interference from third-party applications within the workstation or server environment.

Troubleshooting Questions

In order to narrow down the cause that is preventing the application from launching, please answer the following troubleshooting questions and click on the links for details.

Does the application open from another workstation?

Can you launch the application using a different Windows profile?

Do you receive a specific error message?

Were you previously able to open the application?

Can you open other CS Professional Suite applications?

Network-wide Troubleshooting

If you are able to determine this issue is happening network-wide (on all workstations), see the items listed below:

Open files

Occasionally an open file stuck on the server may prevent FileCabinet CS from launching, and you may receive and error message referencing this.

To close open files on the server:

1. Have every user on the network close out of all CS Professional Suite and Microsoft Office applications. You may have to utilize task manager to make sure CS Connect Background Services are also no longer running.
2. On the machine where the data is located, access the Manage Open Files screen.
   • On Windows 7 and 8 - Right-click on Computer ("This PC" on Windows 8) in the start menu or on the desktop, then select Manage. In the Computer Management window, expand Shared Folders under System Tools and select Open Files.
   • In Windows Server 2008 - In the Control Panel, select Administrative Tools, then select Share and Storage Management. In the Actions pane on the right-hand side, select Manage Open Files.
   • On Windows Server 2012 - Click on the Start menu, and in the search field, type compmgmt.msc. In the console window, expand Shared Folders under System Tools and select Open Files.
3. Find any file that in its name or path references a CS Professional Suite, then select it and close it.

   Note: If the open files will not close or if closing them does not resolve the issue, try rebooting the server and possibly all workstations on the network.

Cltlist.cc$

CltList.cc$ contains drawer information for the data location you are in or trying to open. In rare cases, this file may get corrupted, which will potentially prevent users from opening FileCabinet to that data location. This often will be accompanied by an error which specifically references that file or another message that we have determined to be related to CltList.cc$.

For steps to resolve an issue caused by a corrupt CltList.cc$ file, see FileCabinet CS: Variant-persistent stream - invalid state (run-time) error.

User-specific Troubleshooting

Through troubleshooting, if you have narrowed down the issue as user-specific, see the items listed below that may resolve the issue of FileCabinet CS not opening.

Rename FileCabinet user files/folders

Have the user close out of all CS Professional Suite and Microsoft Office applications, and then rename or delete any of the following files or folders within FileCabinet CS' file structure:

Folder	File	Description
X:\WinCSI\FcabSys	ZFCUMSC.<UserID>	This is the user control file for FileCabinet that controls user preference settings. For the user experiencing the issue, rename this file by appending .old to the end (e.g. ZFCUMSC.user.old).
X:\WinCSI\FcabSys\TmpPrn		This directory contains folders for users that have printed documents to FileCabinet CS and it sometimes contains temporary files that have not been automatically cleared out properly. Delete the folder named for the user experiencing the issue (it will recreate itself as needed).
X:\WinCSI\FcabSys\UID	UID.<UserID>	This folder contains a lock for every user who has FileCabinet CS open. Look for one for the user experiencing the issue and delete it if found.
X:\WinCSI\FcabSys\$Ulock	U***.<UserID>, X***.<UserID>, L***.<UserID>	This folder contains multiple lock files for users depending on what integrated applications they have open. Look for any lock files referencing the user experiencing the issue and a delete them if found.
X:\WinCSI\FcabData\$sysdata	Zfcfocus.<UserID>	This file controls how the drawer list is focused for the specified data location and can sometimes cause significant slowness or other issues launching the application. For the user experiencing the issue, rename this file by appending .old to the end (Ex: Zfcfocus.user.old).
X:\WinCSI\FcabData\$Ulock.fcd	U***.<UserID>, X***.<UserID>, L***.<UserID>	This folder can also contain user lock files. Look for any lock files referencing the user experiencing the issue and a delete them if found.

Clearing the user's Temp directory

To manually clear a user's Temp directory:

1. Close all applications.
2. Go to the Start menu.
3. In the Search programs and files input, type %temp%. Then hit the Enter key on your keyboard. This will open your local Temp directory.
4. Select all (CTRL + A on your keyboard) the items in the directory, then hit the Delete key on your keyboard. Click Yes to the Delete Multiple Items dialog box.
   • If you are prompted with the File In Use or Folder In Use dialog box, mark the checkbox Do this for all current items and click Skip.
5. Attempt to launch the application.
   • If you are now able to launch the application, no further troubleshooting is required.
   • If you are not able launch the application, continue troubleshooting.

Permissions

If you are able to launch the application from a workstation as an admin, or while logged in as the local administrator or domain administrator but not as a user, then it indicates that there is a permissions issue for the user. Additionally, you may receive an error message that either states it is a permissions issue, or we have determined it to be related.

Example: FileCabinet CS Error: Class Csi_Core_Library.

To learn more about permissions, please see Permissions guidelines for CS Professional Suite applications.

Workstation and server-specific troubleshooting

Remove old scanners

Navigate to C:\Windows\twain_32 or twain_64 and delete any folders for old or unused scanners. 

Compatibility Mode

FileCabinet CS does not support operating systems that Microsoft no longer does, including Windows XP and Server 2003. In some cases, your machine may set a few critical FileCabinet CS files to be ran in compatibility mode for a different operating system than you are currently on. This may cause the application not to open as it will detect an unsupported OS, and you will often receive an error message stating this. For example, you may receive the error "setup has detected you are running an unsupported operating system".  To resolve this error:

1. Find the file(s) that may be in compatibility mode depending on your situation:
   • If this occurs during or immediately following installing FileCabinet CS on your network from CS.ThomsonReuters.com, save the file on your machine first rather than running it. The name of the file will be FCSdownload.exe.
   • If this occurs during or immediately following running a desktop setup for FileCabinet CS, browse out to X:\WinCSI\Cabinet\DESKTOP (where X:\ represents where the program was installed). The name of the file will be Setup.exe.
   • If this begins happening well after any install (or after running an install again after disabling the above files), browse out to X:\WinCSI\Cabinet (where X:\ represents where the program was installed). The files will be fcab.exe and fcabapp.exe.
2. Right-click on the file and select Properties.
3. Click on the Compatibility tab.
4. In this tab, there will be a section titled Compatibility mode with a check mark box for "Run this program in compatibility mode for:". If this option is checked, uncheck it and click OK to save the changes.

   Note: If the checkmark box is selected, but is grayed out, click on the button below for Change settings for all users, and then uncheck the box in the next window. If this option is not available, your user account may not have permissions to do this and a login with admin rights will be needed.

5. Attempt to launch the application or re-run the installation respective installation file to confirm if that resolved the issue. If it does not, or the file you selected did not have compatibility mode enabled, attempt this process with another of the listed files, or consider other potential causes of this issue.

Third-party applications

Listed below are examples of third-party applications that can prevent FileCabinet CS from opening.

Antivirus Applications

Antivirus applications are necessary to protect your workstation or server environmental from viruses, spyware, malware and other harmful and unknown threats. Thomson Reuters does not recommend running a machine without an antivirus program installed. At the same time, Thomson Reuters does not recommend a specific brand or type of antivirus application. What we do recommend is that the proper exclusions and exceptions are made within your antivirus application to prevent any potential interference with any CS application.

For more information, see Antivirus guidelines for CS Professional Suite applications.

Internet Explorer

In some network based applications, Internet Explorer's security settings can cause issues launching the application. If this occurs, it will often be in the form of a specific error message that can easily be bypassed to access the program without any further steps required. However, it potentially could prevent the FileCabinet CS from launching to a specific data location.

For more information on this error message and how to resolve it, see Error Opening Any CS Professional Suite Application - "Open file security warning, publisher could not be verified when launching".

Microsoft SQL Server

If you optionally set up a FileCabinet CS data location with Microsoft SQL Server (rather than the default standard format), there are other considerations to be aware of. Certain issues or settings (such as firewall, services, protocols, DNS, etc.) can cause the SQL data location for FileCabinet CS not to open for either one workstation or the entire network. See the following articles for assistance with any SQL related issues causing the application not to open:

• FileCabinet CS: There is a problem accessing the SQL server
• SQL Server best practices for CS Professional Suite applications

ToolBar Applications

Toolbars are a type of malware that comes in the form of a toolbar extension to your Internet browser. ToolBar programs that have been known to cause this error include iLivid Download Manager, iLivid Toolbar, Windows JZip ToolBar, Imesh ToolBar, Windows Search QU ToolBar, Page Rage Bar, Media Bar, Bandoo Toolbar, Search Results Toolbar, and in some instances, Google Desktop and Google Toolbar.

Windows Components

FileCabinet CS requires .NET Framework and Visual C++, two Windows operating system components, to run the application. If one of the Windows components is not installed or corrupt, it may prevent FileCabinet CS from opening.

For more information, see .NET Framework and Visual C++ Considerations for CS Professional Suite.

Uninstalling and reinstalling the application

If you have reached a point in troubleshooting where it is necessary to uninstall and reinstall the application, please make note of the following:

• If you have a network installation and uninstall FileCabinet CS from the Control Panel, it will uninstall FileCabinet CS from the network location for all users. This is not a recommended troubleshooting step if one user or more is still able to access the application.
• Uninstalling FileCabinet CS does not affect client data or application settings. As long as it is installed to the same directory (and all additional data locations are remapped if necessary), you will be able to access all of your existing data.
• When reinstalling the application, please make sure you are logged in as the administrator or that the installation is run as administrator (if on a terminal server, be sure to enable install mode first.
• When reinstalling the application, please make sure that your antivirus is disabled so it does not interfere with installation.
• If you reinstall the application and are still experiencing issues, as the next troubleshooting step, you may want to install FileCabinet CS to a different location to see if you experience the same or different behavior. For example, point the installation to your local C:\ drive or different network drive and attempt to launch the application.

Share This