See How to handle Out-of-Memory issue, and try to reduce your system loading in the meanwhile.
There are two possibilities:
- If the system crashed for some other reason, it will cause the recording file at the time-of-crash to be partially damaged. Our software is designed to automatically recover from this type of problem, so no worries.
- You might have a partially damaged disk. Keep the system under closer watch. Replace new disk if you think is necessary.
- See also: Error Detection: Storage Failure
It can be caused by a number of reasons as follows, but you might want to read user's manual in more details to understand our licensing mechanism.
- Your license might have been invalidated because of significant computer change. This is not allowed by design.
- You chose to let the license remain "online" while you're not able to keep the NVR server always keep connected to the Internet. Without Internet, online license will only remain valid for 3 days, and after that you receive this error. If this were the case, you should commit the license to "offline" to avoid this problem.
- You try to backup a license from a computer, and restore to a different one. This is not allowed by design.
Our license code, once committed to a hardware, cannot be transferred. You need to understand our online authorization mechanism more thoroughly. Following topics can help you do that:
This probably means you have problem with Internet connection to reach our license server.
I received "ERROR CODE: install_httperror/7" or "install_httperror/52"?
This probably means you have problem with Internet connection to reach our license server. It could also mean our license server is down temporarily, as sometimes it might happen under DDoS attack (but it should resume shortly).
You may want to check other Internet site (such as Google or Yahoo) to see if your Internet connection is working normally.
The target computer you are trying to install the license code to is having a incorrect computer time. You need to adjust it to correct time so license can be installed.
There are several possible causes for this:
- If you triggered "index build" for some reasons, it could take a while to rescan all storage files.
- If you have a partially damaged disk, the damaged point may stop the software from working correctly.
Hard disks are known to wear-out after prolonged usage. Building an NVR server with old disks is particularly risky because old disks may contains bad-sectors that may lead to data corruption. Some disks are equipped with self-repair function that automatically moves data from bad-sectors to good-sectors so it does not show damages in an obvious way, but the self-repairing mechanism takes time, and therefore reduces the overall bandwidth. The read-write-heads of a damaged disk could also cause the disk to become much slower.
To reduce this risk, you should periodically engage maintenance to your NVR system by measuring disk performances. If the performance is degraded since last measurement, it could mean a danger signal that the disk is about to be irreversibly damaged.