4. Database
4.1. Errors during backup
CCMUI has encountered a problem and needs to close.

Scenarios where the issue occurs:-
  1. This issue occurs while taking the database backup.
  2. If the Dotnet framework version is on Higher Version.
How to Identify the issue:-

Steps that help us to identify the issue are as follows:

  1. While taking a backup you will get an Error saying that “CCMUI has encountered a problem and needs to close. We are sorry for the inconvenience”.
Solution Provided:-

Steps to resolve the issue are as follows:

  1. Open the cafe manager console and try to take a backup of the database.
  2. The database backup can be taken in 3 ways:
    1. In the Cafe Manager Console click on File > Backup.
    2. While Closing the cafe manager and Clicking on Take Backup and close
    3. Scheduled Backups.
  3. Now while running the backup if you get the error message as “CCMUI has encountered a problem and needs to close. We are sorry for the inconvenience” then follow the below mentioned steps
    1. Close the Cafe Manager Console
    2. Repair the Dotnet components.
    3. For repairing the Dotnet Component go to C:\ProgramFiles\Ideacts\Clinck Cyber Café Manager.
    4. From the list of folder given their please select Dotnet fx2.0.exe
    5. Double Click on the Dotnetfx2.0.exe, once we double click on the same it will give us two options Repair and Uninstall.
    6. Select Repair and then Click on next
    7. This will repair the Dotnet (the process will take about 5 to 10 min)
    8. Once Dot net is repaired click on Finish. Now restart the Clinck Cyber Cafe manager.
    9. This should resolve the issue
  4. While opening the Dotnetfx2.0.exe if it asks only for installation then there is a possibility of a higher version of Dotnet present in the system.
  5. So in such scenario follow the steps:
    1. Go to Start > Control Panel > Add and Remove > Uninstall the Dotnet versions.
    2. After the uninstallation Go to C:\ProgramFiles\Ideacts\Clinck Cyber Cafe Manager and open the Dotnetfx2.0.exe and install the same.
This should resolve the issue with reference to a scenario where higher version of Dotnet is present.