Network Error Messages 1040002 to 1042025
This document describes network 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.
1040002 Too many arguments supplied for this request
Possible Problems
The actual number of buffers to be sent is not the same as the number of buffers predicted at
the start of the session. In the networking layer, make sure that the number of buffers predicted to be sent in
this session is correct.
Possible Solutions
This is an internal error. Contact Hyperion Technical Support.
1040003 No length specified for data type
Possible Problems
The network cannot determine the length of the network buffer based on the type of the buffer.
In the networking layer, specify the length of the buffer explicitly.
Possible Solutions
This is an internal error. Contact Hyperion Technical Support.
1040004 Invalid structure type. An application protocol error might exist between server and
client processes.
Possible Problems
Essbase encountered data with an incorrect data type.
Possible Solutions
Make sure that the client computer and the server computer are running the same release
of ODBC.
Increase the values for NETDELAY and
NETRETRYCOUNT.
1040006 No message database specified
Possible Problems
Essbase did not have a message database defined.
Possible Solutions
This is an internal error. Contact Hyperion Technical Support.
1040007 Cannot find message database fileName, which is required for normal operations.
Make sure your PATH and ARBORPATH variables are pointing to the correct directories. Make sure
that databaseName exists in the $ARBORPATH\bin directory
Possible Problems
Essbase cannot find the message database file, $ARBORPATH/bin/essbase.mdb
.
Possible Solutions
- Make sure that your
PATH
, ARBORPATH
, and
ARBORMSGPATH
environment variables are set correctly.
- Make sure that the network is up and running correctly.
- Hyperion recommends that the file descriptor limit
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
Possible Problems
Essbase cannot read the message database file, $ARBORPATH/bin/essbase.mdb
.
Possible Solutions
Make sure that you are using the correct release of the message database file,
$ARBORPATH/bin/essbase.mdb
. If you are not sure,
reinstall Essbase.
1040010 Invalid data type for conrelease
Possible Problems
Essbase encountered an invalid data type while creating a message string.
Possible Solutions
This is an internal error. Contact Hyperion Technical Support.
1040011 NULL network context passed to message function
Possible Problems
Essbase did not have a valid network context to use to create a message.
Possible Solutions
This is an internal error. Contact Hyperion Technical Support.
1040012 Invalid structure type
Possible Problems
Essbase cannot read the information in the data structure.
Possible Solutions
This is an internal error. Contact Hyperion Technical Support.
1040013 Invalid structure field type
Possible Problems
Essbase cannot read the fields inside the data structure.
Possible Solutions
Make sure that OLAP Server and the Essbase client are installed correctly.
1040014 RegOpenKeyEx() Failed
Possible Problems
Essbase cannot find the host name in the registry.
Possible Solutions
Make sure that your registry is set up correctly. Consult the Windows-specific documentation.
1040015 RegQueryInfoKey() Failed
Possible Problems
Essbase cannot retrieve the registry key.
Possible Solutions
Make sure that your registry is set up correctly. Consult the Windows-specific documentation.
1040016 RegEnumValue() Failed
Possible Problems
Essbase cannot retrieve values from the registry.
Possible Solutions
Make sure that your registry is set up correctly. Consult the Windows-specific documentation.
1040017 Host Name Not Available
Possible Problems
Essbase cannot find the specified host name.
Possible Solutions
Make sure that the host name is correct.
1040018 Bad hostname to adNetIsLocalHost()
Possible Problems
Essbase cannot find the host name.
Possible Solutions
Make sure that the host name is correct.
1040019 Message code message; see server log for message
text
Possible Problems
The listed error occurred.
Possible Solutions
Check the application and OLAP 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
Possible Problems
Essbase cannot create the named pipe because of the listed error.
Possible Solutions
The listed error is not an Essbase error. Consult the networking documentation.
1041002 Network error: Timed out waiting for connection, Error
Code:message
Possible Problems
Essbase cannot connect to the named pipe.
Possible Solutions
- Check to see if the
$ARBORPATH/bin/essnet.dll
files match on the client
computer and the server computer.
- If the
$ARBORPATH/bin/essnet.dll
files do not match, reinstall
the networking protocol. Be sure to
select named pipes as the networking protocol. Consult the Essbase
Installation Guide.
- If the
$ARBORPATH/bin/essnet.dll
files match, consult the
networking documentation.
- Increase the values for NETDELAY and
NETRETRYCOUNT.
1041003 Network error message: Cannot disconnect named
pipe
Possible Problems
Essbase cannot disconnect from the named pipe.
Possible Solutions
This is not an Essbase error. Consult the networking documentation.
1041004 Network error message: Cannot send data
Possible Problems
Essbase cannot send data over the network using named pipes.
Possible Solutions
Increase the values for NETDELAY and
NETRETRYCOUNT.
Check the index cache size,
data cache size,
and block size to make sure 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.
Possible Problems
The Essbase network API timed out before receiving data from the named pipe.
Possible Solutions
Increase the values for NETDELAY and NETRETRYCOUNT.
1041006 Network error: Timed out waiting to receive message
Possible Problems
Essbase timed out before receiving data from the named pipe.
Possible Solutions
Increase the values for NETDELAY and NETRETRYCOUNT.
1041007 Network error: Cannot locate connect information for namedPipe
Possible Problems
Essbase cannot find the named pipe.
Possible Solutions
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
Possible Problems
The Essbase client, such as Essbase Spreadsheet Add-in, cannot connect to OLAP Server.
Possible Solutions
Make sure that the installation is correct.
- Did you select named pipes as the protocol when you installed?
- Are you using the correct release of the
$ARBORPATH/bin/essnetw.dll
file? If you are not sure, reinstall the
networking protocol. Be sure to select named pipes as the networking protocol. Consult the Essbase Installation Guide.
Make sure that OLAP Server is running correctly. If necessary,
stop and restart
OLAP Server.
1041009 Network error: Cannot connect to server serverName
Possible Problems
Essbase API cannot complete the OpenOutline function.
Possible Solutions
- Make sure that OLAP Server is running.
- Make sure that the network is running.
- Make sure that the client can connect to OLAP Server.
- Check the return values from EssOtlOpenOutline() and
EssOtlVerifyOutline().
1041011 Network error message:InitializeSecurityDescriptor failed
Possible Problems
Essbase cannot initialize and set the security descriptor for the named pipe.
Possible Solutions
This is not an Essbase error message. Consult the operating system documentation and
the networking
documentation.
1041012 Network error message: SetSecurityDescriptorDacl failed
Possible Problems
Essbase cannot initialize and set the security descriptor for the named pipe.
Possible Solutions
This is not an Essbase error message. Consult the operating system documentation and networking
documentation.
1041013 Network error: Timed out sending data
Possible Problems
Essbase timed out before sending data to the named pipe.
Possible Solutions
1041014 Network error: NodeName required in essbase.cfg for Named Pipe
Possible Problems
The NODENAME setting was not specified in the $ARBORPATH/bin/essbase.cfg
file.
Possible Solutions
- If you do not have an
$ARBORPATH/bin/essbase.cfg
file on
the server computer in the $ARBORPATH\bin
directory, create one using a
text editor.
- In the
$ARBORPATH/bin/essbase.cfg
file, set NODENAME.
- Stop and restart OLAP Server.
1042002 Network error message: Cannot Terminate Socket
Possible Problems
Essbase cannot close the socket.
Possible Solutions
Close the socket manually. Consult the networking documentation.
1042003 Network Error message: Unable To Locate serverName In Hosts File
Possible Problems
Essbase cannot locate the server computer name.
Possible Solutions
- 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 there is no entry, add one. For example, add the following 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 there is no entry, add one. For example, add the following 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
Make sure the .rhosts
file is included in your path.
- Increase the values for 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 Essbase Installation Guide.
- Are you using a stand-alone computer with no network interface card? Consult the Essbase Installation
Guide.
1042004 Network Error message: Unable To Create Local Socket
Possible Problems
The Essbase client cannot create a TCP/IP socket.
Possible Solutions
Make sure that you have the correct release of $ARBORPATH/bin/essnetw.dll
and $ARBORPATH/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.
Possible Problems
Essbase Application Manager can find the server computer but cannot connect to OLAP Server.
Possible Solutions
- Are you trying to connect to the correct server computer? Are there typographical errors?
- Is OLAP Server running on the listed computer?
- Are the network protocols installed correctly on the server computer and the client computer? Consult the
Essbase Installation Guide.
- Are the ports for OLAP Server open and running? If not, specify non-default ports.
- Increase the values for NETDELAY and NETRETRYCOUNT.
- If you are using ESSCMD, make sure 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 the following 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
Possible Problems
The TCP/IP socket of the server computer cannot be listened on.
Possible Solutions
This is not an Essbase message. Check the operating system and networking documentation.
1042008 Network Error message: Unable To Accept Connections
Possible Problems
The server computer cannot accept more requests from the client.
Possible Solutions
This is not an Essbase message. Check the operating system and networking documentation.
1042009 Network Error message: Unable To Create Host Server Socket
Possible Problems
The server computer cannot create a TCP/IP socket.
Possible Solutions
Are the network protocols installed correctly on the server computer and the client computer? Is TCP/IP bound to the
network adapter? Consult the Essbase Installation Guide.
Is the hosts file correct?
- Windows: Check the
HOSTS
file for an entry for the server name.
If there is no entry, add one. For example, add the following 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 there is no entry, add one. For example, add the following 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
Make sure the .rhosts
file is included in your path.
1042010 Network Error message: Unable to Bind Host Server Socket On Port number
Possible Problems
Essbase cannot bind a server socket on the listed port.
Possible Solutions
Is OLAP Server running on the listed computer?
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 OLAP Server, OLAP Server
cannot process requests. If necessary, reboot the server computer and start OLAP Server before other applications.
1042011 Network error message: Cannot Close Socket
Possible Problems
Essbase cannot close the socket.
Possible Solutions
Close the socket yourself. Consult the networking documentation.
1042012 Network error message: Cannot Send Data
Possible Problems
Essbase cannot send data over the network using named pipes.
Possible Solutions
Increase the values for NETDELAY and NETRETRYCOUNT.
Check the index cache size, data cache size,
and data block size to make sure that they are within the recommended ranges.
1042013 Network error message: Cannot Receive Data
Possible Problems
Essbase cannot receive data from the other end of a TCP/IP connection.
Possible Solutions
- Increase the values for NETDELAY and NETRETRYCOUNT.
- Make sure that OLAP Server and the client are running.
- If OLAP Server receives this message, make sure that the client you are trying to connect to is running.
- If a client receives this message, make sure that the OLAP Server you are trying to connect to is running.
- If OLAP Server froze, stop OLAP Server and follow the procedures for
an abnormal shutdown. If you cannot stop OLAP Server using the standard
methods, end the task.
- Check to see if the database is corrupt.
1042015 Network error: Cannot Locate Connect Information For APICommand
Possible Problems
The active application and database are not set.
Possible Solutions
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.
Possible Problems
The server computer or client computer cannot receive data using a TCP/IP network connection.
Possible Solutions
1042018 Network error: Timed out waiting to send message
Possible Problems
Essbase cannot send all of the data before timing out.
Possible Solutions
Increase the values for NETDELAY and NETRETRYCOUNT.
1042019 Network error message: Cannot initialize windows sockets
Possible Problems
Essbase cannot initialize the Windows sockets.
Possible Solutions
This is not an Essbase error message. Consult the operating system documentation.
1042020 Network error message: Cannot initialize windows sockets
Possible Problems
Essbase cannot initialize the Windows 3.0 sockets.
Possible Solutions
This is not an Essbase error message. Consult the operating system documentation.
1042022 Network error message: Cannot Get Host Name
Possible Problems
Essbase cannot find the local host name. Make sure that the buffer that holds the returned name is a
valid address. Make sure that the buffer size is a positive number.
Possible Solutions
This is not an Essbase error message. Consult the networking or operating system
documentation.
1042023 Network Error: file descriptor limit per process has
been reached
Possible Problems
Essbase has reached the file descriptor limit. The file descriptor limit determines how
many files an application can open at any one time.
Possible Solutions
Hyperion recommends that the file descriptor limit
setting be 1024 files.
1042024 Network Error: file descriptor limit in the system has
been reached
Possible Problems
Essbase has reached the file descriptor limit. The file descriptor limit determines how
many files an application can open at any one time.
Possible Solutions
Hyperion recommends that the file descriptor limit
setting be 1024 files.
1042025 Network error errorCode: Cannot Get Host
Address
Possible Problems
The getpeername network system call failed.
Possible Solutions
Consult the networking documentation to determine the cause of the listed
error code.