Unregistered Serial Key

Issue Description

From within the Chronicall Status window, the following error message is displayed:

Unregistered Serial Key! Not Logging!

Cause

The Chronicall serial key is associated with the unique hardware profile of the server on which Chronicall is installed. This hardware profile is used to generate a Chronicall Info Hash. Whenever the known Info Hash for a particular Serial Key does not match the current hardware profile of the machine running Chronicall, the Chronicall Status window will display an error and logging will stop. 

Resolution

Remove the Old Serial Key

If the old machine is still available, you can unregister the Serial Key allowing the new hardware to be registered. See the steps below.

Reset the Info Hash

If the old machine is no longer available, the Info Hash associated with the Serial Key will need to be reset by contacting the Xima Care Support Team. Have your Serial Key handy to expedite this process.

How To Remove the Old Serial Key

1. From the previous Chronicall server, navigate to Admin(System) > System Settings > Basic Settings > Serial Key. 
   • Note the Chronicall Serial Key shown here.
2. Select"Unregister". 
   • A prompt will ask you to verify that you want to unregister the serial key. 
   • Click Yes to unregister the serial key. 
     • You may receive a second prompt saying that the serial key couldn't be unregistered but that it will be removed from the settings.
3. You should now see that the serial key is no longer in the serial key box. 
4. Click on SAVE at the bottom of the System Settings page. 
   • This will take you back to the Chronicall Main Menu.

How To Register a New Serial Key

1. Navigate to Admin(System) > System Settings > Basic Settings > Serial Key. 
2. Enter the Serial Key.
3. Click on "Register". 
   • The serial key should register successfully. 
   • If not, call Xima to reset your info-hash on the back end. 
4. Click on SAVE at the bottom of the System Settings page.
5. Relaunch Chronicall
   • Exit and then Reopen
6. You should now see that Chronicall is back up and logging again.