Common Issues in TCMS V3 / Ingress Software After Database Migration

Common Issues in TCMS V3 / Ingress Software After Database Migration

Occasionally, users might be facing some issues while using TCMS V3 or Ingress software after
migrating the database from TCMS V2. Below are some examples of common issues that arise after
the migration process.
Issue 1: Failed or Invalid Device Activation
To prevent any activation issues, please do not use TCMS V2 product key when activating TCMS V3
or Ingress software. If your PC has an Internet connection, opt for Online Activation in order to
activate the device after the migration process.

However, if your PC do not have any Internet connection, you will need to carry out offline activation.
Go to this site to retrieve the product key for your
device(s) and insert the product key manually to activate.

Issue 2: Different Schedule ID
Schedule ID in TCMS V3 and Ingress is different from TCMS V2. TCMS V2 Schedule ID starts from
0, while TCMS V3 and Ingress Schedule ID starts from 1. Thus, you might see a different set of
Schedule ID in TCMS V3 or Ingress after the database migration. For example, in TCMS V2, your
Schedule IDs are 0 - 4; however, once you migrated to TCMS V3 or Ingress, the Schedule IDs will
be labelled as 1 - 5. Don’t worry, this is not a bug, it happens because of the difference in software

After Migration:

Issue 3 - Open Schedule Differences in TCMS V2 and TCMS V3/Ingress
After migrating the database from TCMS V2, you might encounter certain issues related to Open
Schedule roster in TCMS V3 or Ingress. Open Schedule roster configuration in TCMS V2 slightly
differs with TCMS V3 or Ingress. Shift Roster is used to create Open Schedule for TCMS V2, but for
TCMS V3/Ingress, you will have to use Weekly Roster to configure an Open Schedule. Note that you will have to reconfigure the roster in TCMS V3/Ingress after the migration. Otherwise, the data
will not be allocated correctly in the software.
Open Schedule settings in TCMS V2:

After Migration:
In TCMS V3/Ingress, there is no option for you to configure the Open Schedule within the migrated
shift roster. To ensure that Open Schedule roster works in TCMS V3 or Ingress, we suggest that you
create a new Open Weekly Roster and re-configure the Open Schedule configuration. Note that you
can still use the existing migrated Schedule ID in the new Weekly Open Roster.
To create Open Schedule Roster in TCMS V3/Ingress:
1) Go to Group Duty Roster > Click Add Roster > Configure the roster name and set the roster as
Weekly > OK

2) Select the new roster and click Edit > Auto Schedule > Set the Day Type and add the Open
Schedule ID
Note: If some of the screenshots or steps viewed here are different from the ones in the current system, this is due to our continuous effort to improve our system from time to time. Please notify us at, we will update it as soon as possible.

    • Related Articles

    • Migration Wizard Smoothen Data Migration from TCMSv2 into Ingress

      Introduction Setting up of a new system can be cumbersome when it involves a lot of staff, departments, different working hours and conditions, and other variables. In view of this, FingerTec has created a wizard that can migrate database from TCMSv2 ...
    • How to perform Database Migration from Ingress/TCMS V3 to TimeTec TA

      Introduction- TimeTec has introduced a new feature to assist in moving your current Windows-Based data to our Smart Solution: TimeTec TA via migration tool. The ‘Export’ function for migration to TimeTec TA is ONLY available in the latest version of ...
    • 5 Common Errors in TCMS V3/ Ingress Software and How to Fix It

      Introduction Occasionally, you might encounter into some errors when using TCMS V3 or Ingress software. Don’t close the program just yet. Here we have compiled 5 common errors in the software and how to solve it. Problem 1 - Empty Attendance Sheet ...
    • Navigate Ingress Better | Avoid These 5 Common Mistakes

      Introduction Ingress is FingerTec’s bundled software with every purchase of FingerTec door access hardware. Over time, we have compiled common mistakes users made while using Ingress that have caused unnecessary frustration and wrong outcomes. Let’s ...
    • How To Fix Crash During Migration of Data from TCMS V2 to TCMS V3/Ingress

      INTRODUCTION - Lately, we have been receiving feedback from some TCMS V3/Ingress Software users, whereby their PCs suddenly crash during the migration process and inadvertently cause the data to not be fully migrated from TCMS V2 database into TCMS ...