You are here: Getting Started > Problems with Working Papers Installation
-- Reference --


If you encountered issues installing Working Papers:

  • Ensure that you have write privileges in the directories specified for the installation, and
  • Ensure that there is enough free disk space on the hard drive to meet the system requirements.
Issue Resolution
  • Error 1904. Module C:\Program Files\CaseWare\CWPCore.dll failed to register. HRESULT -2147220473. Contact your support personnel.
  • The program can’t start because MSVCR100.dll is missing from your computer.


This problem may occur when installing Working Papers using the.msi file instead of the setup.exe file.

  1. Uninstall Working Papers and reboot your computer.
  2. Reinstall CaseWare Working Papers using setup.exe.
Working Papers does not launch after installing.

This problem may occur when installing Working Papers on a computer with accented letters in the computer name. Example: André.

  • Remove any accented letter from the computer name.

You can only have one version of Working Papers installed on your machine (Working Papers or Working Papers SmartSync ). You can install Working Papers SmartSync over your existing version of Working Papers. Users on SmartSync can work on regular Working Papers files without activating SmartSync.

We highly recommend that SmartSync users do NOT share any SmartSync engagement files with users of regular (non-SmartSync) Working Papers. Accessing SmartSync engagement files in regular Working Papers can cause adverse effects to SmartSync. If you do open a SmartSync file in regular Working Papers you must immediately do the following:

  1. Delete the synchronized copy that shared the SmartSync engagement file with the non-SmartSync version of Working Papers.
  2. Open the associated Parent file and abandon the deleted synchronized copy in Step 1.

If you do not wish to install SmartSync over your existing Working Papers version, perform the SmartSync installation on a Virtual Machine (VM).

We recommend running antivirus software at both the server and desktop level. However, some virus-checking software may conflict with CaseWare and other database products. If you are experiencing problems that are related to anti-virus software please contact your anti-virus software vendor for the latest upgrades and service packs.

Please test all anti-virus software in a lab environment prior to installing company wide.

Anti-Virus software can cause issues with Working Papers Data Store functionality by locking required files as it scans them. The suggestions below address this issue. These tasks should be completed both on workstations running CaseWare files and on the servers that host these files.

  • If your virus scanner can exclude files by their extensions then all Working Papers files should be excluded. The following extensions are associated with Working Papers and can be excluded from virus scans: *.dbf, *.cdx, *.fpt, *.cvw, *.ac, and *.ac_.
  • If your virus scanner can exclude applications, exclude the following executable files in the Working Papers root installation folder: CWIN32.EXE, CVWIN32.EXE, CWCS.EXE.

If you are using Norton AntiVirus and running Working Papers, you may receive a warning from Norton of a malicious script being detected. This warning tells users that a program running is creating documents on their system. Since this is how Working Papers generates many of its files, Norton AntiVirus identifies Working Papers as a potential problem. Within this message, the user is provided with 5 (five) options. The first time that the message appears, the user should select the final of the five options - "Authorize this Script." to tell Norton that Working Papers is a trusted application. This prevents any future alerts when using the program. Note the activities by the FileSystemObject continue to be monitored, so any worms using this object will be detected still.


Related Topics