Most 7490 - 7499 errors are the result of memory corruption on the host machine. Although these errors are rare, they can be serious. In most cases, restarting FairCom DB will clear a transient memory error. If these errors repeat, please contact your application vendor.
Table 1. Error codes 7490 - 7499
| Value | Description |
|---|---|
| 7490 | Indicates a request for memory is beyond reasonable limits. |
| 7491 | Indicates the user was attempting to return memory that carried an unreasonable large length value in its control header. |
| 7492 | Indicates an invalid "availability" counter was encountered during a sub-allocator get operation. |
| 7493 | Indicates an invalid "availability" counter was encountered while returning a block of memory. |
| 7494 | Indicates there is an update flag inconsistency between the index file header and the buffer status information. |
| 7495 |
A list connected with FairCom DB’s memory sub-allocator has become invalid or corrupted. For single-user, check your parameters that are passed to our functions. For a server, this is usually a bug. This error has been seen in V11.2.2. due to bad Unicode data. V11.2.3 has been patched to catch bad data and log it instead of passing it into the code, causing a crash. |
| 7496 | Indicates there was a failure in the memory swapping operation. |
| 7497 | Indicates the user was attempting to return memory that carried a zero length in its control header. |
| 7498 | Indicates an invalid semaphore owner was encountered while getting memory. |
| 7499 | Indicates an invalid semaphore owner was encountered while returning memory. |