Applicable Versions: v4.C.3.3 and before
Problem: When there are a series of power outages spaced at the right interval, it can cause corruption to a configuration file within RaPTr Server. The timing is just right such that RaPTr Server is booting after the first blip in power, it begins to look at and edit the configuration file, and then a second blip in power occurs, causing RaPTr Server to shut off while it had opened and edited a file. On the next boot, RaPTr Server likely is not licensed since the configuration file is no longer correct.
Solution: Reach out to Artemis Vision support by calling or messaging. A tech within Artemis Vision will help you recover the configuration file and restore system operation.
NOTE: This issue has been fixed as of v4.D.0.0