1040002 to 1042025: Network Messages

Table 10 lists network error and informational messages.

Table 10. Network Messages 1040002 to 1042025

Message NumberMessagePossible CausePossible Solution

1040002

Too many arguments supplied for this request

The number of buffers to be sent does not match the number of buffers predicted at the start of the session. In the networking layer, ensure that the number of buffers predicted to be sent in this session is correct.

This is an internal error. Contact Oracle Support.

1040003

No length specified for data type

The network cannot determine the network buffer length based on the buffer type. In the networking layer, specify the length of the buffer explicitly.

This is an internal error. Contact Oracle Support.

1040004

Invalid structure type. An application protocol error might exist between server and client processes.

Essbase encountered data with an incorrect data type.

Ensure that the client computer and the server computer run the same release of ODBC. Increase the values for NETDELAY and NETRETRYCOUNT (see Setting NETDELAY and NETRETRYCOUNT).

1040006

No message database specified

Essbase did not have a message database defined.

This is an internal error. Contact Oracle Support.

1040007

Cannot find message database fileName, which is required for normal operations. Make sure your PATH and ESSBASEPATH variables are pointing to the correct directories. Make sure that databaseName exists in the ESSBASEPATH/bin directory

Essbase cannot find the message database file, ESSBASEPATH/bin/essbase.mdb.

Ensure that your PATH and ESSBASEPATH, and environment variables (see Setting Environment Variables) are set correctly.

Ensure that the network is up and running correctly.

Hyperion recommends that the file descriptor limit (see Checking the User Limit Profile) setting be 1024 files.

1040008

Error reading message database fileName. fileName could be corrupted, or it could be the wrong release. Make sure that the file you are using is from the same Essbase release level as the .exe and .dll files

Essbase cannot read the message database file, ESSBASEPATH/bin/essbase.mdb.

Ensure that you are using the correct release of the message database file, ESSBASEPATH/bin/essbase.mdb. If you are not sure, reinstall Essbase.

1040010

Invalid data type for conversion

Essbase encountered an invalid data type while creating a message string.

This is an internal error. Contact Oracle Support.

1040011

NULL network context passed to message function

Essbase did not have a valid network context to use to create a message.

This is an internal error. Contact Oracle Support.

1040012

Invalid structure type

Essbase cannot read the information in the data structure.

This is an internal error. Contact Oracle Support.

1040013

Invalid structure field type

Essbase cannot read the fields inside the data structure.

Ensure that Essbase Server and the Essbase client are installed correctly.

1040014

RegOpenKeyEx() Failed

Essbase cannot find the host name in the registry.

Ensure that your registry is set up correctly. Consult your Windows documentation.

1040015

RegQueryInfoKey() Failed

Essbase cannot retrieve the registry key.

Ensure that your registry is set up correctly. Consult your Windows documentation.

1040016

RegEnumValue() Failed

Essbase cannot retrieve values from the registry.

Ensure that your registry is set up correctly. Consult your Windows documentation.

1040017

Host Name Not Available

Essbase cannot find the specified host name.

Ensure that the host name is correct.

1040018

Bad hostname to adNetIsLocalHost()

Essbase cannot find the host name.

Ensure that the host name is correct.

1040019

Message code message; see server log for message text

The listed error occurred.

Check the application and Essbase Server logs for more details about the error that occurred. The listed error is not an Essbase error. Check the operating system documentation or networking documentation.

1041000

Network error message: Cannot Create Named Pipe

Essbase cannot create the named pipe because of the listed error.

The listed error is not an Essbase error. Consult the networking documentation.

1041002

Network error: Timed out waiting for connection, Error Code: message

Essbase cannot connect to the named pipe.

Determine whether the ESSBASEPATH/bin/essnet.dll files match on the client computer and the server computer.

  • If the ESSBASEPATH/bin/essnet.dll files do not match, reinstall the networking protocol. Be sure to select named pipes as the networking protocol. Consult the Oracle Hyperion Enterprise Performance Management System Installation Start Here.

  • If the ESSBASEPATH/bin/essnet.dll files match, consult the networking documentation.

Increase the values for NETDELAY and NETRETRYCOUNT (see Setting NETDELAY and NETRETRYCOUNT).

1041003

Network error message: Cannot disconnect named pipe

Essbase cannot disconnect from the named pipe.

This is not an Essbase error. Consult the networking documentation.

1041004

Network error message: Cannot send data

Essbase cannot send data over the network using named pipes.

Increase the values for NETDELAY and NETRETRYCOUNT (see Setting NETDELAY and NETRETRYCOUNT).

Check the index cache size, data cache size, and block size to Ensure that they are within the recommended ranges.

1041005

Network error message: The Network API timed out waiting to receive data from the Named Pipe. Increase the NetRetryCount and/or NetDelay values in your essbase.cfg file. Make sure you update this file on both client and server, if they exist on different computers. Restart the client and try again.

The Essbase network API timed out before receiving data from the named pipe.

Increase the values for NETDELAY and NETRETRYCOUNT (see Setting NETDELAY and NETRETRYCOUNT).

1041006

Network error: Timed out waiting to receive message

Essbase timed out before receiving data from the named pipe.

Increase the values for NETDELAY and NETRETRYCOUNT (see Setting NETDELAY and NETRETRYCOUNT).

1041007

Network error: Cannot locate connect information for namedPipe

Essbase cannot find the named pipe.

Create the named pipe. Consult the networking documentation.

1041008

Network error: Cannot locate Essbase on server serverComputerName. Verify that the serverComputerName is accessible using the Named Pipe and that the Essbase Agent is running on the server

The Essbase client, such as Essbase Spreadsheet Add-in, cannot connect to Essbase Server.

Ensure that the installation is correct.

  • Did you select named pipes as the protocol when you installed?

  • Are you using the correct release of ESSBASEPATH/bin/essnetw.dll? If you are not sure, reinstall the networking protocol. Be sure to select named pipes as the networking protocol. Consult the Oracle Hyperion Enterprise Performance Management System Installation Start Here.

Ensure that Essbase Server is running correctly. If necessary, stop and restart Essbase Server.

1041009

Network error: Cannot connect to server serverName

Essbase API cannot complete the OpenOutline function.

Ensure that Essbase Server is running.

Ensure that the network is running.

Ensure that the client can connect to Essbase Server.

Check the return values from EssOtlOpenOutline and EssOtlVerifyOutline.

1041011

Network error message:InitializeSecurityDescriptor failed

Essbase cannot initialize and set the security descriptor for the named pipe.

This is not an Essbase error message. Consult the operating system documentation and the networking documentation.

1041012

Network error message: SetSecurityDescriptorDacl failed

Essbase cannot initialize and set the security descriptor for the named pipe.

This is not an Essbase error message. Consult the operating system documentation and networking documentation.

1041013

Network error: Timed out sending data

Essbase timed out before sending data to the named pipe.

Ensure that Essbase Server is running.

Ensure that the network is running.

Increase the values for NETDELAY and NETRETRYCOUNT (see Setting NETDELAY and NETRETRYCOUNT).

1041014

Network error: NodeName required in essbase.cfg for Named Pipe

The NODENAME setting was not specified in the ESSBASEPATH/bin/essbase.cfg file.

  1. If ESSBASEPATH/bin/essbase.cfg does not exist on the server computer in the ESSBASEPATH/bin directory, create one using a text editor.

  2. In the ESSBASEPATH/bin/essbase.cfg file, set NODENAME.

  3. Stop and restart Essbase Server.

1042002

Network error message: Cannot Terminate Socket

Essbase cannot close the socket.

Close the socket manually. Consult the networking documentation.

1042003

Network Error message: Unable To Locate serverName In Hosts File

Essbase cannot locate the server computer name.

Increase the values for NETDELAY and NETRETRYCOUNT (see Setting NETDELAY and NETRETRYCOUNT).

Are the server computer and the client computer running the same network protocols?

Are you using the TCP/IP or named pipes network protocol? These are the only two network protocols supported by Essbase.

Is the network protocol installed correctly? Consult the Oracle Hyperion Enterprise Performance Management System Installation Start Here.

Are you using a stand-alone computer with no network interface card? Consult the Oracle Hyperion Enterprise Performance Management System Installation Start Here.

Is the server name you entered correct? Are there typographical errors?

Is the hosts file correct?

  • Windows: Check the HOSTS file for an entry for the server name. If no entry exists, add one. For example, add this line to the HOSTS file to add a server named aspen with the IP address of 127.0.0.1:

    127.0.0.1 aspen 
  • UNIX: Check the .rhosts file for an entry for the server name. If no entry exists, add one. For example, add this line to the .rhosts file to add a server named aspen with the IP address of 127.0.0.1:

    127.0.0.1 aspen

    Ensure that the .rhosts file is included in your path.

1042004

Network Error message: Unable To Create Local Socket

The Essbase client cannot create a TCP/IP socket.

Ensure that you have the correct release of ESSBASEPATH/bin/essnetw.dll and ESSBASEPATH/bin/winsock.dll. If you are not sure, reinstall the Essbase client.

If reinstalling the Essbase client does not solve the problem, look up the listed message text in the networking documentation.

1042006

Network Error message: Unable To Connect To serverName. The client timed out waiting to connect to the Essbase Agent using TCP/IP. Check your network connections. Also please make sure that Server and Port values are correct.

Administration Services can find the server computer but cannot connect to Essbase Server.

Are you trying to connect to the correct server computer? Are there typographical errors?

Is Essbase Server running on the listed computer?

  • If Essbase Server is not running, restart Essbase Server.

  • If Essbase Server crashed, follow the procedures for an abnormal shutdown.

  • If Essbase Server has frozen, stop Essbase Server and follow the procedures for an abnormal shutdown. If you cannot stop Essbase Server using the standard methods, end the task (see Ending the Server Task).

Are the network protocols installed correctly on the server computer and the client computer? Consult the Oracle Hyperion Enterprise Performance Management System Installation Start Here.

Are the ports for Essbase Server open and running? If not, specify non-default ports.

Increase the values for NETDELAY and NETRETRYCOUNT (see Setting NETDELAY and NETRETRYCOUNT).

If you are using ESSCMD, ensure that you are using the correct server name (not an alias) and that the server name, user name, and password are all enclosed in quotation marks. For example, use this command to log on a user named Max to a server named ASPEN:

LOGIN "ASPEN" "Max" "PASSWORD";

1042007

Network Error message: Unable To Listen For Connections

The TCP/IP socket of the server computer cannot be listened on.

This is not an Essbase message. Check the operating system and networking documentation.

1042008

Network Error message: Unable To Accept Connections

The server computer cannot accept more requests from the client.

This is not an Essbase message. Check the operating system and networking documentation.

1042009

Network Error message: Unable To Create Host Server Socket

The server computer cannot create a TCP/IP socket.

Are the network protocols installed correctly on the server computer and the client computer? Is TCP/IP bound to the network adapter? Consult the Oracle Hyperion Enterprise Performance Management System Installation Start Here.

Is the hosts file correct?

  • Windows: Check the HOSTS file for an entry for the server name. If no entry exists, add one. For example, add this line to the HOSTS file to add a server named aspen with the IP address of 127.0.0.1:

    127.0.0.1 aspen
  • UNIX: Check the .rhosts file for an entry for the server name. If no entry exists, add one. For example, add this line to the .rhosts file to add a server named aspen with the IP address of 127.0.0.1:

    127.0.0.1 aspen

Ensure that the .rhosts file is included in your path.

1042010

Network Error message: Unable to Bind Host Server Socket On Port number

Essbase cannot bind a server socket on the listed port.

Is Essbase Server running on the listed computer?

  • If Essbase Server is not running, restart Essbase Server.

  • If Essbase Server crashed, follow the procedures for an abnormal shutdown.

  • If Essbase Server has frozen, stop Essbase Server and follow the procedures for an abnormal shutdown. If you cannot stop Essbase Server using the standard methods, end the task (see Ending the Server Task).

Is another application using the Essbase port? The Essbase agent listens on TCP/IP port 1423 for incoming requests. If another application assigns that port before you start Essbase Server, Essbase Server cannot process requests. If necessary, reboot the server computer and start Essbase Server before other applications.

1042011

Network error message: Cannot Close Socket

Essbase cannot close the socket.

Close the socket yourself. Consult the networking documentation.

1042012

Network error message: Cannot Send Data

Essbase cannot send data over the network using named pipes.

Increase the values for NETDELAY and NETRETRYCOUNT (see Setting NETDELAY and NETRETRYCOUNT).

Check the index cache size, data cache size, and data block size to Ensure that they are within the recommended ranges.

1042013

Network error message: Cannot Receive Data

Essbase cannot receive data using the TCP/IP connection.

Increase the values for NETDELAY and NETRETRYCOUNT (see Setting NETDELAY and NETRETRYCOUNT).

Ensure that Essbase Server and the client are running.

  • If Essbase Server receives this message, ensure that the client you are trying to connect to is running.

  • If a client receives this message, ensure that the Essbase Server you are trying to connect to is running.

  • If Essbase Server has frozen, stop Essbase Server and follow the procedures for an abnormal shutdown. If you cannot stop Essbase Server using the standard methods, end the task (see Ending the Server Task).

Determine whether the database is corrupt (see Checking for Database Corruption).

1042015

Network error: Cannot Locate Connect Information For APICommand

The active application and database are not set.

If you are using the C API, use the EssSetActive function to set the active application and database.

If you are using the Visual Basic API, use the EsbSetActive function to set the active application and database.

1042017

Network error: The client or server timed out waiting to receive data using TCP/IP. Check network connections. Increase the NetRetryCount and/or NetDelay values in the essbase.cfg file. Update this file on both client and server. Restart the client and try again.

The server computer or client computer cannot receive data using a TCP/IP network connection.

Increase the values for NETDELAY and NETRETRYCOUNT (see Setting NETDELAY and NETRETRYCOUNT).

Ensure that Essbase Server and the client are running.

  • If Essbase Server receives this message, ensure that the client you are trying to connect to is running.

  • If a client receives this message, ensure that the Essbase Server you are trying to connect to is running.

  • If Essbase Server has frozen, stop Essbase Server and follow the procedures for an abnormal shutdown. If you cannot stop Essbase Server using the standard methods, end the task (see Ending the Server Task).

If you are spanning disk volumes, ensure that you have enough space.

Determine whether the security file is corrupt.

Determine whether the database is corrupt (see Checking for Database Corruption).

1042018

Network error: Timed out waiting to send message

Essbase cannot send all data before timing out.

Increase the values for NETDELAY and NETRETRYCOUNT (see Setting NETDELAY and NETRETRYCOUNT).

1042019

Network error message: Cannot initialize windows sockets

Essbase cannot initialize the Windows sockets.

This is not an Essbase error message. Consult the operating system documentation.

1042020

Network error message: Cannot initialize windows sockets

Essbase cannot initialize the Windows 3.0 sockets.

This is not an Essbase error message. Consult the operating system documentation.

1042022

Network error message: Cannot Get Host Name

Essbase cannot find the local host name.

This is not an Essbase error message. Consult the networking or operating system documentation.

Ensure that the buffer that holds the returned name is a valid address. Ensure that the buffer size is a positive number.

1042023

Network Error: file descriptor limit per process has been reached

Essbase has reached the file descriptor limit. The file descriptor limit determines how many files an application can open simultaneously.

Hyperion recommends that the file descriptor limit (see Checking the User Limit Profile) setting be 1024 files.

1042024

Network Error: file descriptor limit in the system has been reached

Essbase has reached the file descriptor limit. The file descriptor limit determines how many files an application can open simultaneously.

Hyperion recommends that the file descriptor limit (see Checking the User Limit Profile) setting be 1024 files.

1042025

Network error errorCode: Cannot Get Host Address

The getpeername network system call failed.

Consult the networking documentation to determine the cause of the listed error code.