System Call Error Messages 1008001 to 1008152

This document describes system call error messages and information messages. The discussions of error messages include possible causes and possible solutions for each problem, with links to the Essbase Database Administrator's Guide and the Essbase Technical Reference for more information on how to fix errors.

Click an error message number to view information about that error message.
1008001 1008039 1008112 1008127 1008142
1008006 1008089 1008113 1008128 1008143
1008009 1008090 1008114 1008129 1008144
1008010 1008091 1008115 1008130 1008145
1008021 1008092 1008116 1008131 1008146
1008022 1008093 1008117 1008132 1008147
1008023 1008099 1008118 1008133 1008148
1008024 1008100 1008119 1008134 1008149
1008025 1008101 1008120 1008135 1008150
1008028 1008106 1008121 1008136 1008151
1008029 1008107 1008122 1008137 1008152
1008030 1008108 1008123 1008138
1008031 1008109 1008124 1008139
1008036 1008110 1008125 1008140
1008037 1008111 1008126 1008141

1008001 Unable to Allocate Memory

Possible Problems
Essbase cannot allocate enough memory to perform the operation.

Possible Solutions

1008006 Unable to Free Memory for memoryToBeFreed in funtionName

Contact Hyperion Technical Support.


1008009 Pointer is NULL - Free Canceled: variableName in functionName

Possible Problems
Essbase cannot free the listed memory.

Possible Solutions
Contact Hyperion Technical Support.

1008010 Read Failed

Possible Problems
Essbase cannot read a calculation script located on the client.

Possible Solutions
  1. Run the calculation script again.
  2. Restart the client and then run the calculation script again.
  3. Copy the calculation script to the server and then run the calculation script again.

1008021 Named Pipe Create Failed

Possible Problems
Essbase cannot create the named pipe.

Possible Solutions
Consult the networking documentation.


1008022 Pipe Create Failed

Possible Problems
Essbase cannot create the pipe.

Possible Solutions
Consult the networking documentation.


1008023 Named Pipe Connect Failed

Possible Problems
Essbase cannot connect to the named pipe.

Possible Solutions
Consult the networking documentation.


1008024 Named Pipe Disconnect Failed

Possible Problems
Essbase cannot disconnect from the named pipe.

Possible Solutions
Consult the networking documentation.


1008025 Named Pipe Peek Failed

Possible Problems
Essbase cannot peek to the named pipe.

Possible Solutions
Consult the networking documentation.


1008028 Pipe Read Error

Possible Problems
Essbase cannot read from the named pipe.

Possible Solutions
Check to see if OLAP Server is running.

1008029 Pipe Write Error

Possible Problems
Essbase cannot write to the named pipe.

Possible Solutions
Consult the networking documentation.


1008030 Pipe Open Failed

Possible Problems
Essbase cannot open the named pipe.

Possible Solutions
Consult the networking documentation.


1008031 Pipe Close Failed

Possible Problems
Essbase cannot close the named pipe.

Possible Solutions
Consult the networking documentation.


1008036 Incorrect # of Bytes Written To Pipe

Possible Problems
Essbase cannot finish writing to the named pipe.

Possible Solutions
Consult the networking documentation.


1008037 Find Next Failed

Possible Problems
Essbase cannot find the next file in the sequence.

Possible Solutions
This might occur if Essbase is processing multiple files, such as during a copy or a load. If you can determine which file is missing, restore it from backups.


1008039 Find Close Failed

Possible Problems
Essbase cannot close the next file in the sequence.

Possible Solutions
This might occur if Essbase is processing multiple files, such as during a copy or a load. If you can determine which file is having problems, restore it from backups.


1008089 Error receiving data from Agent

Possible Problems
Essbase cannot receive data from the Agent.

Possible Solutions
Check to see if OLAP Server is running.

1008090 Timed out receiving data from Agent

Possible Problems
Essbase cannot receive data from the Agent.

Possible Solutions
Check to see if OLAP Server is running.

1008091 Error sending data to Agent

Possible Problems
Essbase cannot send data to the Agent.

Possible Solutions
Contact Hyperion Technical Support.


1008092 Timed out sending data to Agent

Possible Problems
Essbase cannot send data to the Agent.

Possible Solutions
Contact Hyperion Technical Support.


1008093 Invalid data type for conversion

Contact Hyperion Technical Support.


1008099 HALLOC: Possible duplicate memory allocation! variableName in functionName

Contact Hyperion Technical Support.


1008100 HFREE: Pointer already freed! variableName in functionName

Contact Hyperion Technical Support.


1008101 HFREE: Likely memory overwrite! variableName in functionName

Possible Problems
The original memory allocation was overwritten by a newer allocation to the same pointer.

Possible Solutions
Contact Hyperion Technical Support.


1008106 Exception error log errorLogName.XCP is being created...

Possible Problems
Essbase is generating an exception log just before it shuts down abnormally.

Possible Solutions
  1. Search the exception log for information about what caused the shut down.
  2. Check to see if the database is corrupt.
  3. Contact Hyperion Technical Support.

1008107 Exception error log completed -- please contact technical support and provide them with this file

Possible Problems
Essbase finished generating the error log. Now Essbase will shut down.

Possible Solutions
  1. Search the exception log for information about what caused the shut down.
  2. Check to see if the database is corrupt.
  3. Contact Hyperion Technical Support.

1008108 Essbase Internal Logic Error logicErrorNumber

Possible Problems
Essbase encountered a logic error and shut down abnormally.

Possible Solutions

1008109 Unable to Reallocate Memory for pointerName in functionName

Possible Problems
Essbase cannot reallocate memory to the listed function.

Possible Solutions
Make sure that you have enough memory.


1008110 Unable to Allocate Memory. Refer to the Application Log for details.

Possible Problems
Essbase cannot allocate memory.

Possible Solutions

1008111 Unable to Reallocate Memory for pointerName in functionName. Refer to the Application Log for details.

Possible Problems
Essbase cannot reallocate memory.

Possible Solutions

1008112 Memory Allocation error codes: O/S error = errorCode, O/S return code = errorNumber

Possible Problems
Essbase could not allocate memory.

Possible Solutions
Make sure that you have enough memory.
Look up the operating system error code and the operating system return code in the operating system documentation for more information.


1008113 Memory Reallocation error codes: O/S error = errorCode, O/S return code = errorNumber

Possible Problems
Essbase could not reallocate memory.

Possible Solutions
Make sure that you have enough memory.
Look up the operating system error code and the operating system return code in the operating system documentation for more information.


1008114 Allocation request for number bytes of virtual memory. Percentage of memory in use is number %.

This is an information message stating the number of bytes of virtual memory requested and the percentage of virtual memory currently being used by Essbase. There is nothing wrong.


1008115 Total physical memory is number bytes. Available physical memory is number bytes.

This is an information message stating the total number of bytes of physical memory and the number of bytes of available physical memory. There is nothing wrong.


1008116 Total swap space is number bytes. Available swap space is number bytes.

This is an information message stating the total number of bytes of swap space and the number of bytes of available swap space. There is nothing wrong.

1008117 Total virtual memory is number bytes. Available virtual memory is number bytes.

This is an information message stating the total number of bytes of virtual memory and the number of bytes of available virtual memory. There is nothing wrong.

1008118 Memory page size is number bytes. Allocation granularity is number bytes.

This is an information message stating the total number of bytes of memory page size and the size that memory is allocated in. There is nothing wrong.

1008119 Memory page size is number bytes

This is an information message stating the total number of bytes of memory page size. There is nothing wrong.

1008120 Unable to Allocate Physical Memory for pointerName in functionName

Possible Problems
Essbase cannot allocate physical memory to the listed function.

Possible Solutions
Make sure that you have enough physical memory.


1008121 Unable to Allocate Physical Memory for pointerName in functionName for reallocation

Possible Problems
Essbase cannot reallocate physical memory to the listed function.

Possible Solutions
Make sure that you have enough physical memory.


1008122 Unable to Lock the Allocated Memory for pointerName in functionName

Possible Problems
Essbase cannot lock the needed memory.

Possible Solutions

1008123 Unable to Lock the Allocated Memory for pointerName in functionName for reallocation

Possible Problems
Essbase cannot lock the needed memory.

Possible Solutions

1008124 Unable to Lock the Allocated Memory pointerName in functionName, because of insufficient quota

Possible Problems
Essbase does not have enough physical memory to lock the memory.

Possible Solutions
Check the OLAP Server memory requirements. If necessary, increase the physical memory.


1008125 Unable to Lock the Allocated Memory pointerName in functionName, because of insufficient privilege

Possible Problems
Essbase is not assigned the correct operating system privileges to lock the memory.

Possible Solutions
Make sure that the Agent is assigned the correct operating system privileges.


1008126 Unable to Lock the Allocated Memory pointerName in functionName for reallocation, because of insufficient quota

Possible Problems
Essbase does not have enough physical memory to lock the memory.

Possible Solutions
Check the OLAP Server memory requirements. If necessary, increase the physical memory.


1008127 Unable to Lock the Allocated Memory pointerName in functionName for reallocation, because of insufficient privilege

Possible Problems
Essbase is not assigned the correct operating system privileges to lock the memory.

Possible Solutions
Make sure that the Agent is assigned the correct operating system privileges.


1008128 Unable to Allocate Physical Memory for pointerName in functionName. Refer to the Application Log for details.

Possible Problems
Essbase does not have enough physical memory to lock the memory.

Possible Solutions

1008129 Unable to Allocate Physical Memory for pointerName in functionName for reallocation. Refer to the Application Log for details.

Possible Problems
Essbase does not have enough physical memory to lock the memory.

Possible Solutions

1008130 Unable to Lock the Allocated Memory for pointerName. Refer to the Application Log for details.

Possible Problems
Essbase cannot lock the needed memory.

Possible Solutions

1008131 Unable to Lock the Allocated Memory for pointerName in functionName for reallocation. Refer to the Application Log for details.

Possible Problems
Essbase cannot lock the needed memory.

Possible Solutions

1008132 Unable to Lock the Allocated Memory pointerName in functionName, because of insufficient quota. Refer to the Application Log for details.

Possible Problems
Essbase does not have enough physical memory to lock the memory.

Possible Solutions

1008133 Unable to Lock the Allocated Memory pointerName in functionName, because of insufficient privilege. Refer to the Application Log for details.

Possible Problems
Essbase is not assigned the correct operating system privileges to lock the needed memory.

Possible Solutions

1008134 Unable to Lock the Allocated Memory pointerName in funtionName for reallocation, because of insufficient quota. Refer to the Application Log for details.

Possible Problems
Essbase does not have enough physical memory to lock the memory.

Possible Solutions

1008135 Unable to Lock the Allocated Memory pointerName in functionName for reallocation, because of insufficient privilege. Refer to the Application Log for details.

Possible Problems
Essbase is not assigned the correct operating system privileges to lock the needed memory.

Possible Solutions

1008136 Unable to Free Locked Memory for pointerName in functionName

Possible Problems
Essbase cannot free the memory, probably because an invalid pointer was passed to the function that frees the memory.

Possible Solutions
Contact Hyperion Technical Support.


1008137 Unable to Free Memory for pointerName in functionName in reallocation

Possible Problems
Essbase cannot free the memory, probably because an invalid pointer was passed to the function that frees the memory.

Possible Solutions
Contact Hyperion Technical Support.


1008138 Unable to Free Memory for pointerName in functionName in reallocation. Refer to the Application Log for details.

Possible Problems
Essbase cannot free the memory, probably because an invalid pointer was passed to the function that frees the memory.

Possible Solutions
Look in the applicationName.log log for more information.
Contact Hyperion Technical Support.


1008139 Unable to Allocate Aligned Memory for pointerName in functionName

Possible Problems
Essbase does not have enough virtual memory to allocate the memory to the listed pointer.

Possible Solutions
Check the OLAP Server virtual memory requirements. If necessary, increase the virtual memory and restart OLAP Server.


1008140 Unable to Free Aligned Memory for pointerName in functionName

Possible Problems
Essbase cannot free the memory, probably because an invalid pointer was passed to the function that frees the memory.

Possible Solutions
Contact Hyperion Technical Support.


1008141 Unable to Allocate Aligned Memory for pointerName in functionName for reallocation

Possible Problems
Essbase does not have enough virtual memory to allocate the memory to the listed pointer.

Possible Solutions
Check the OLAP Server virtual memory requirements. If necessary, increase the virtual memory and restart OLAP Server.


1008142 Unable to Free Aligned Memory for pointerName in functionName in reallocation

Possible Problems
Essbase cannot free the memory, probably because an invalid pointer was passed to the function that frees the memory.

Possible Solutions
Contact Hyperion Technical Support.


1008143 Unable to Allocate Aligned Memory for pointerName in functionName. Refer to the Application Log for details.

Possible Problems
Essbase does not have enough virtual memory to allocate the memory to the listed pointer.

Possible Solutions

1008144 Unable to Allocate Aligned Memory for pointerName in functionName for reallocation. Refer to the Application Log for details.

Possible Problems
Essbase does not have enough virtual memory to allocate the memory to the listed pointer.

Possible Solutions

1008145 Unable to Free Aligned Memory for pointerName in functionName in reallocation. Refer to the Application Log for details.

Possible Problems
Essbase cannot free the memory, probably because an invalid pointer was passed to the function that frees the memory.

Possible Solutions
Look in the applicationName.log log for more information.
Contact Hyperion Technical Support.


1008146 Unable to Unlock the Allocated Memory pointerName in functionName

Possible Problems
Essbase cannot free the memory, probably because an invalid pointer was passed to the function that frees the memory.

Possible Solutions
Contact Hyperion Technical Support.


1008147 Unable to Allocate Memory for pointerName in functionName

Possible Problems
Essbase does not have enough virtual memory to allocate the memory to the listed pointer.

Possible Solutions
Check the OLAP Server virtual memory requirements. If necessary, increase the virtual memory and restart OLAP Server.


1008148 Unable to Allocate Memory for pointerName in functionName. Refer to the Application Log for details.

Possible Problems
Essbase does not have enough virtual memory to allocate the memory to the listed pointer.

Possible Solutions

1008149 Abnormal shutdown request entered Are you sure you want to forcibly shutdown the application [1-yes,2-no]?

Possible Problems
This is an information message that is dispayed in the Agent window when you try to shut down OLAP Server incorrectly.

Possible Solutions
If possible, always stop OLAP Server correctly.
  1. Enter 2 and try to stop OLAP Server correctly.
  2. If you cannot stop OLAP Server correctly, enter 1 to stop OLAP Server.
  3. If this does not work, end the task.
  4. After you stop OLAP Server, follow the procedures for an abnormal shutdown.

1008150 The abnormal shutdown request is aborted, the application will continue processing

This is an information message stating that the administrator aborted an abnormal shutdown request, probably by answering no to message 1008149.


1008151 System is busy. The application will re-attempt the abnormal shutdown request.

This is an information message stating that OLAP Server is performing an important task, such as writing to the index. When OLAP Server completes this task, OLAP Server will try to shut down again.


1008152 System is still busy. The abnormal shutdown request is aborted, try again later.

This is an information message stating that OLAP Server is performing an important task, such as writing to the index. OLAP Server aborted the abnormal shutdown request to finish this task. If possible, wait a few minutes and stop OLAP Server correctly. If you cannot stop OLAP Server correctly, end the task.

After you stop OLAP Server, follow the procedures for an abnormal shutdown.