3. BCS-2 Installation
add chapter

3.1 Why are my jobs disappearing?
add section

The logged on user does not have the required write permissions. In a standard installation, the BCS-2 configuration, job and license files are stored under C:/ProgramData/Imageware. If a user does NOT have the necessary write rights for this folder, the jobs created by the user are only available temporarily (after restarting the PC, the jobs “disappeared”). When installing the software, it must always be ensured that the appropriate write rights are assigned by the administrator (see installation requirements).

3.2 Can I run BCS-2 Office and BCS-2 Professional on a virtual machine (VM)?
add section

BCS-2 Office and BCS-2 Professional can be operated on virtual machines with the Windows operating systems W10 and W11. Size the PC according to our installation requirements. For the connection and integration of third-party devices (e.g. scanners, multifunction copiers, payment systems), it must be ensured that their drivers/dongles/API etc. run under the VM so that BCS-2 recognizes them. This is not the case with some ABBYY OCR functions and TWAIN scanners. Please check this by installing the software provided by the device manufacturer on the VM. If the device can be controlled with it, it should also be possible to integrate it into BCS-2.

3.3 Details on installing the new BCS-2 V6 version 6.6
add section

3.3.1 Notes

Call up data, programme, licence and job directories in BCS-2 via the “Help” >> “About BCS-2” tab:

Be sure to process all old orders. Delete all orders manually that BCS-2 does not delete automatically after transfer.

3.3.2 Prerequisites

Please note when changing from BCS-2 version 6.2. to 6.6: As a new online registration must take place, the licence certificate must be available. If the certificate is not already stored on the computer, copy it from the BCS-2 licence folder: C:\ProgramData\ImageWareComponents\BCS2_V6_64\licence.

When updating from version 6.4x to version 6.6. there is no need to register online again.

3.3.3 Upgrade from V6.4.0 to V6.6

We recommend the following procedure for upgrading BCS-2 version 6.4.8 to 6.6:

  1. Export of settings (Configurator and Administrator)
  2. Uninstall the old version
  3. Retain the existing file folders of the uninstalled version: Configuration and licence files under C:\ProgramData\ImageWareComponents\BCS2_V6_OFFICE_64.
  4. Start the installation file bcs2_V6_ofc_6_6_11_64.exe
  5. Reject the update message “BCS-2 seems to be already installed, do you want to perform an update?” by clicking on “NO”. You will receive this message because the registry entry for the deleted installation still exists.
  6. Confirm the following message “The folder C:* already exists, do you still want to install in this folder?” by clicking on “YES”.
  7. Carry out the installation.
  8. Start BCS-2-Administrator or BCS-2-Configurator.
  9. Carry out the online registration. If BCS-2 sends a licence error message, exit and restart BCS-2.
  10. Adjust workflows (e.g. activate dynamic masks, configure mask colours).
  11. BCS-2 is ready for a restart.

3.3.4 Upgrade from V6.0/V6.1/V6.2 to V6.6

We recommend the following procedure for upgrading from versions older than BCS-2 6.4.0:

  1. Export the settings (administrator or configurator)
  2. Uninstalling the old version
  3. Delete all configuration and licence files remaining on your hard drive under:
    • C:\ProgramData\ImageWareComponents\BCS2_V6_OFFICE_64
    • C:\Program Files\ImageWareComponents\BCS2_V6_OFFICE_64.
  4. Start the installation file bcs2_V6_ofc_6_6_11_64.exe.
  5. Reject the update message “BCS-2 seems to be already installed, do you want to perform an update?” by clicking on “NO”. You will receive this message because the registry entry for the deleted installation still exists.
  6. Carry out the installation.
  7. Start the BCS-2 administrator or configurator and complete the online registration.
  8. Import the settings exported in step 1. BCS-2 closes automatically during this process.
  9. Start BCS-2-Administrator or BCS-2-Configurator and carry out the online registration.
  10. Adjust workflows (e.g. activate dynamic masks, configure mask colours).
  11. BCS-2 is ready for a restart.

3.4 Installing the 6.6.x version of BCS-2 – dll error message
add section

With the current 6.4.x und 6.6.x versions of BCS-2 Office and Professional, there might be an error message after a new installation when starting the software for the first time (Configurator, Administrator and Application). This message refers to the lack of a DLL file that is needed for BCS-2 to run. The file MSVCP140.dll or MSVCP140_1.dll is required.

The MSVCP140.dll file requires Windows to run programs written in C++. It is one of the runtime components of the Microsoft software Visual C++ Redistributable for Visual Studio 2015, which is automatically installed when BCS-2 is reinstalled. 

Unfortunately, the latest redistributable version of Microsoft 2015-2019 no longer includes these files. This DLL file is still required for BCS-2, as we support common – even older – hardware in the customer field that requires these program libraries. We have no influence on the program libraries of Microsoft’s redistributable packages.

Installation instructions

To resolve the “MSVCP140.dll missing” error, first install the vcredist_x64.exe file for 64-bit systems or vcredist_x86.exe for 32-bit systems. BCS-2 stores the redistributable locally during installation (Programs > ImageWareComponents > BCS-2 > ms_redist). If you have decided not to install the redistributable during installation, this is also possible without downloading.

If BCS-2 still shows that the file “MSVCP140.dll” is missing at startup, install the Redistributable vc_redist_2014_x86.exe as well. All files are available for download on our BCS-2 platform via the links above.

When installing the redistributables, make sure that you start with the lowest version. Each redistributable package checks for a newer version. If so, the package will not be installed. The safest way to do this is to uninstall all installed redistributables and restore them starting with the lowest version.

Alternative

Copy the MSVCP140.dll file from another PC to the C:WindowsSystem32 folder. To do this, you need to remove the write protection for the folder in the short term.

to indexprevious chapternext chapter
to overviewnext manual