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 Analytic Services Database Administrator's Guide and the Essbase Analytic Services Technical Reference for more information on how to fix errors.
Click an error message number to view information about that error message.
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.
This is an internal error. Contact Hyperion Technical Support.
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.
This is an internal error. Contact Hyperion Technical Support.
Analytic Services encountered data with an incorrect data type.
Make sure that the client computer and the server computer are running the same release of ODBC. Increase the values for NETDELAY and NETRETRYCOUNT.
Analytic Services did not have a message database defined.
This is an internal error. Contact Hyperion Technical Support.
Analytic Services cannot find the message database file, $ARBORPATH/bin/essbase.mdb
.
PATH
, ARBORPATH
,
and ARBORMSGPATH
environment
variables are set correctly.Analytic Services cannot read the message database file, $ARBORPATH/bin/essbase.mdb
.
Make sure that you are using the correct release of the message database
file, $ARBORPATH/bin/essbase.mdb
. If you are not sure, reinstall
Analytic Services.
Analytic Services encountered an invalid data type while creating a message string.
This is an internal error. Contact Hyperion Technical Support.
Analytic Services did not have a valid network context to use to create a message.
This is an internal error. Contact Hyperion Technical Support.
Analytic Services cannot read the information in the data structure.
This is an internal error. Contact Hyperion Technical Support.
Analytic Services cannot read the fields inside the data structure.
Make sure that Analytic Server and the Analytic Services client are installed correctly.
Analytic Services cannot find the host name in the registry.
Make sure that your registry is set up correctly. Consult the Windows-specific documentation.
Analytic Services cannot retrieve the registry key.
Make sure that your registry is set up correctly. Consult the Windows-specific documentation.
Analytic Services cannot retrieve values from the registry.
Make sure that your registry is set up correctly. Consult the Windows-specific documentation.
Analytic Services cannot find the specified host name.
Make sure that the host name is correct.
Analytic Services cannot find the host name.
Make sure that the host name is correct.
The listed error occurred.
Check the application and Analytic Server logs for more details about the error that occurred. The listed error is not an Analytic Services error. Check the operating system documentation or networking documentation.
Analytic Services cannot create the named pipe because of the listed error.
The listed error is not an Analytic Services error. Consult the networking documentation.
Analytic Services cannot connect to the named pipe.
$ARBORPATH/bin/essnet.dll
files match on the client computer and the server computer. $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 Analytic
Services Installation Guide.$ARBORPATH/bin/essnet.dll
files match, consult the networking documentation. Analytic Services cannot disconnect from the named pipe.
This is not an Analytic Services error. Consult the networking documentation.
Analytic Services cannot send data over the network using named pipes.
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.
The Analytic Services network API timed out before receiving data from the named pipe.
Increase the values for NETDELAY and NETRETRYCOUNT.
Analytic Services timed out before receiving data from the named pipe.
Increase the values for NETDELAY and NETRETRYCOUNT.
Analytic Services cannot find the named pipe.
Create the named pipe. Consult the networking documentation.
The Analytic Services client, such as Analytic Services Spreadsheet Add-in, cannot connect to Analytic Server.
Make sure that the installation is correct.
$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
Analytic Services Installation Guide. Make sure that Analytic Server is running correctly. If necessary, stop and restart Analytic Server.
Analytic Services API cannot complete the OpenOutline function.
Analytic Services cannot initialize and set the security descriptor for the named pipe.
This is not an Analytic Services error message. Consult the operating system documentation and the networking documentation.
Analytic Services cannot initialize and set the security descriptor for the named pipe.
This is not an Analytic Services error message. Consult the operating system documentation and networking documentation.
Analytic Services timed out before sending data to the named pipe.
The NODENAME setting was not specified in the $ARBORPATH/bin/essbase.cfg
file.
$ARBORPATH/bin/essbase.cfg
file on the server computer in the $ARBORPATH\bin
directory,
create one using a text editor.$ARBORPATH/bin/essbase.cfg
file, set NODENAME.Analytic Services cannot close the socket.
Close the socket manually. Consult the networking documentation.
Analytic Services cannot locate the server computer name.
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
.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
.rhosts
file is included in your path.The Analytic Services client cannot create a TCP/IP socket.
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 Analytic Services client.
If reinstalling the Analytic Services client does not solve the problem,
look up the listed message text in the networking documentation.
Administration Services can find the server computer but cannot connect to Analytic Server.
LOGIN "ASPEN" "Max" "PASSWORD";
The TCP/IP socket of the server computer cannot be listened on.
This is not an Analytic Services message. Check the operating system and networking documentation.
The server computer cannot accept more requests from the client.
This is not an Analytic Services message. Check the operating system and networking documentation.
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 Essbase Analytic Services Installation Guide.
Is the hosts file correct?
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
.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
.rhosts
file is included in your path.Analytic Services cannot bind a server socket on the listed port.
Is Analytic Server running on the listed computer?
Is another application using the Analytic Services port? The Analytic Services agent listens on TCP/IP port 1423 for incoming requests. If another application assigns that port before you start Analytic Server, Analytic Server cannot process requests. If necessary, reboot the server computer and start Analytic Server before other applications.
Analytic Services cannot close the socket.
Close the socket yourself. Consult the networking documentation.
Analytic Services cannot send data over the network using named pipes.
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.
Analytic Services cannot receive data from the other end of a TCP/IP connection.
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.
The server computer or client computer cannot receive data using a TCP/IP network connection.
Analytic Services cannot send all of the data before timing out.
Increase the values for NETDELAY and NETRETRYCOUNT.
Analytic Services cannot initialize the Windows sockets.
This is not an Analytic Services error message. Consult the operating system documentation.
Analytic Services cannot initialize the Windows 3.0 sockets.
This is not an Analytic Services error message. Consult the operating system documentation.
Analytic Services 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.
This is not an Analytic Services error message. Consult the networking or operating system documentation.
Analytic Services has reached the file descriptor limit. The file descriptor limit determines how many files an application can open at any one time.
Hyperion recommends that the file descriptor limit setting be 1024 files.
Analytic Services has reached the file descriptor limit. The file descriptor limit determines how many files an application can open at any one time.
Hyperion recommends that the file descriptor limit setting be 1024 files.
The getpeername network system call failed.
Consult the networking documentation to determine the cause of the listed error code.