Could not | Failed to Allocate memory ***
Description
Memory resources not available to process request.
Notes
Could be due to limited resources, or anti-virus interference.
Could not | Failed to Allocate memory ***
Memory resources not available to process request.
Could be due to limited resources, or anti-virus interference.
audio|close|command|connect|create|http|receive|recv|soap|socket|select|send|stream error #number#
Standard networking socket error codes.
In Windows they are usually 5 digits. In Linux, 3 digits.
Call to GetAdaptersInfo found no available network interfaces ***.
No network adapters found.
May be unsupported hardware configuration or anti-virus interference.
Config update failure – failed to allocate device object.
The config XMl could not be updated.
Root drive may be full, or anti-virus interference.
Invalid incoming alarm XML.
The config XMl may be corrupt.
Reload previously exported config or delete and let the plugin recreate a new one.
Invalid config update XML.
The config XML may be corrupt.
Reload previously exported config or delete and let the plugin recreate a new one.
Allocation failure while processing *** XML.
Insufficient resources when attempting to update the config XML.
The root drive may be full or anti-virus may be interfering.
Failed to open plugin.
A necessary resource for EventPI was not loaded successfully. There may be related logs to troubleshoot why.
The Event Linking option will not show up in the Client.
Invalid event database – ***
The EventPI database may be corrupted. The database is located in the Server folder as “eventpi.db”.
The database files are located in the Server folder and start with: eventpi.db .
Stop the Server service, delete the files and restart to recreate the database.
Failed call to GetAdaptersInfo in buffer 0E897B98. Return Code=998
Windows Socket Leak.
Windows Socket Leak. See the following Microsoft KB http://support.microsoft.com/kb/2577795