Agent Error Messages 1052001 to 1054030
This document describes agent 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.
1052001 Error reading from server
Possible Problems
Essbase cannot read from OLAP Server, probably because OLAP Server
was stopped incorrectly.
Possible Solutions
- Check to see if OLAP Server is running.
- Make sure that the following environment
variables are set correctly:
ARBORPATH
(PC and UNIX)
PATH
(PC and UNIX)
LD_LIBRARY_PATH
(UNIX only)
- Make sure that OLAP Server and the Essbase client are installed correctly.
- Make sure that the license number is correct and that the license number
supports all the features that you are using. If you just migrated, make sure that
you followed the migration information correctly. Check the Essbase Installation
Guide.
- Increase the values for NETDELAY
and NETRETRYCOUNT.
- Check to see if the security file is
corrupt.
- If you are on a UNIX computer, check the
user limit profile.
- Check to see if any databases are
corrupt.
See Also
1006010
1052002
1052002 Error writing to server
Possible Problems
Essbase cannot write to OLAP Server, probably because OLAP Server
was stopped incorrectly.
Possible Solutions
- Check to see if OLAP Server is running.
- Make sure that the block size is
within the recommended range.
- Make sure that the license number is correct and that the license number
supports all the features that you are using. If you just migrated, make sure that
you followed the migration information correctly. Check the Essbase Installation
Guide.
- Check to see if the security file is
corrupt.
- Make sure that you have enough disk space.
- Check to see if any databases are
corrupt.
See Also
1052001
1052003 Timed out reading from server
Possible Problems
Essbase timed out before it could read from the server.
Possible Solutions
1052004 Timed out writing to server
Possible Problems
Essbase timed out before it could write to the server.
Possible Solutions
1052005 You have been forced to disconnect from the selected
application
Possible Problems
Essbase has no connection to the selected application.
Possible Solutions
You might have been disconnected because you were timed out, logged out by an
administrator, or the application stopped.
Connect to the selected application
again.
1053001 Cannot open object file: fileName
Possible Problems
Essbase cannot open the listed file.
Possible Solutions
- Make sure that you have the correct operating system privileges for the listed
file and directory.
- If the application was copied or deleted using file system controls (such as
Windows Explorer or the
cp
or rm
commands), create a
dummy application with the original name and use Essbase
copy or
delete the application correctly.
- Make sure that the block size is
within the recommended range.
- Make sure that the file name (including the entire path) is not more than 256
characters. If it is longer than 256 characters, the file name will be trunacted
in the error message.
- See if another user has locked the file.
- Make sure that the file exists. If the file does not exist,
restore the file from backups.
- Make sure that you have enough memory.
- If the listed file is
essbase.sec
, make sure that the security file is not
read-only at the operating system level.
- If the listed file is
essbase.sec
, make sure that the security file is not
corrupt.
- If you are using the
BEGINARCHIVE command,
specify a directory for the archive.
- Stop and restart OLAP Server.
See Also
1003022
1053002 Cannot create application directory: directoryName
operatingSystemErrorCode
Possible Problems
Essbase cannot create the listed application directory.
Possible Solutions
- Make sure that you have the correct operating system privileges for the listed
file and directory.
- Make sure that you have enough disk space.
- Make sure that the following environment
variables are set correctly:
ARBORPATH
(PC and UNIX)
PATH
(PC and UNIX)
LD_LIBRARY_PATH
(UNIX only)
1053003 Application directory does not exist:
directoryName
Possible Problems
Essbase cannot find the listed application directory.
Possible Solutions
- If the application was copied or deleted using file system controls (such as
Windows Explorer or the
cp
or rm
commands), create a
dummy application with the original name and use Essbase
copy or
delete the application correctly.
- Make sure that the directory exists in the correct location.
- Make sure that you have the correct operating system privileges for the listed
directory.
- See if another user has locked the directory.
- Make sure that the following environment
variables are set correctly:
ARBORPATH
(PC and UNIX)
PATH
(PC and UNIX)
LD_LIBRARY_PATH
(UNIX only)
- Make sure that the security file is not
corrupt.
- If you are using ESSCMD, make sure that the application directory specified in the
ESSCMD command is correct.
1053004 Cannot create database directory: directoryName
operatingSystemErrorCode
Possible Problems
Essbase cannot create the listed database directory.
Possible Solutions
- Make sure that you have the correct operating system privileges for the listed
file and directory.
- Make sure that you have enough disk space.
- Make sure that the following environment
variables are set correctly:
ARBORPATH
(PC and UNIX)
PATH
(PC and UNIX)
LD_LIBRARY_PATH
(UNIX only)
1053005 Database directory does not exist: directoryName
Possible Problems
Essbase cannot find the listed database directory.
Possible Solutions
- If the application was copied or deleted using file system controls (such as
Windows Explorer or the
cp
or rm
commands), create a
dummy application with the original name and use Essbase
copy or
delete the application correctly.
- Make sure that the directory exists in the correct location.
- Make sure that you have the correct operating system privileges for the listed
directory.
- See if another user has locked the directory.
- Make sure that the following environment
variables are set correctly:
ARBORPATH
(PC and UNIX)
PATH
(PC and UNIX)
LD_LIBRARY_PATH
(UNIX only)
- Make sure that the security file is not
corrupt.
- If you are using ESSCMD, make sure that the application directory used in the
ESSCMD command is correct.
1053006 Invalid object type
Possible Problems
Essbase cannot open the object because it is not a recognized type. Essbase
recognizes Essbase objects, such as applications, outlines, database files, alias tables,
rules files, and linked reporting objects. Essbase also recognizes some external
objects, such as spreadsheet files.
Possible Solutions
Make sure that OLAP Server and the client (such as Spreadsheet Add-in) are at
the same release level.
1053007 Cannot rename object originalName to
newName
Possible Problems
Essbase cannot rename the listed object.
Possible Solutions
- Make sure that you have the correct operating system privileges for the listed
object.
- Make sure that the new name is valid.
- Make sure that an object using the new name does not already exist.
1053008 Cannot create object objectName
Possible Problems
The operating system will not allow Essbase to create the listed object.
Possible Solutions
- Make sure that you have the correct operating system privileges for the listed
object.
- Make sure that the object name is valid.
- Make sure that the object name (including the entire path) is not more than 256
characters. If it is longer than 256 characters, the object name will be trunacted
in the error message.
1053009 Cannot delete object objectName
Possible Problems
The operating system will not allow Essbase to delete the listed object.
Possible Solutions
- Make sure that you have the correct operating system privileges for the listed
object.
- Make sure that the object name is valid.
1053010 Object objectName is already locked by
user userName
Possible Problems
The object you are trying to lock is locked by the listed user.
Possible Solutions
- Wait a few minutes to allow the other active user's process
to finish and retry the operation.
- If necessary, unlock the file.
- If this error happens frequently, make sure that users are logging off Essbase
correctly.
- Stop and restart OLAP Server.
1053011 Object objectName is not locked by
user userName
Possible Problems
Essbase cannot unlock the listed object because it is not locked.
Possible Solutions
1053012 Object objectName is locked by
user userName
Possible Problems
The listed object is locked by the listed user.
Possible Solutions
- Wait a few minutes to allow the other active user's process
to finish and retry the operation.
- If necessary, unlock the file.
- If this happens frequently, make sure that users are logging off Essbase
correctly.
- Stop and restart OLAP Server.
1053013 Object objectName unlocked by user
userName
This information message states that the listed object was unlocked
by the listed user. There is nothing wrong.
1053014 Object objectName does not exist
Possible Problems
Essbase cannot find the listed object.
Possible Solutions
- If the application was copied or deleted using file system controls (such as
Windows Explorer or the
cp
or rm
commands), create a
dummy application with the original name and use Essbase
copy or
delete the application correctly.
- If you are using partitions, make sure that the listed file exists at the
source and at the target.
- Check to see if the security file is
corrupt.
- Make sure that you have enough disk space.
1053015 Object objectName already exists
Possible Problems
Essbase cannot create the listed object because it already exists.
Possible Solutions
If the application was copied or deleted using file system controls (such as
Windows Explorer or the cp
or rm
commands), create a
dummy application with the original name and use Essbase
copy or
delete the application correctly.
1053016 Cannot open temporary file
Possible Problems
Essbase cannot open a temporary file to save the security file.
Possible Solutions
- Make sure that you have enough disk space.
- Make sure that you have the correct operating system privileges.
1053017 Cannot open log file for application
applicationName
Possible Problems
Essbase cannot open the application log file for the listed application.
Possible Solutions
- Make sure that you have the correct operating system privileges for the listed
application.
- Make sure that you have the correct Essbase
permissions for the listed file.
- Make sure that you have enough disk space.
- If the application was copied or deleted using file system controls (such as
Windows Explorer or the
cp
or rm
commands), create a
dummy application with the original name and use Essbase
copy or
delete the application correctly.
1053018 Operation not permitted on outline objects
Possible Problems
Essbase cannot perform the operation on outline objects.
Possible Solutions
You cannot delete, copy, or rename an outline. Instead you must
delete, copy,
or rename the database.
1053019 Cannot rename directory: oldDirectoryName
operatingSystemErrorCode
Possible Problems
Essbase cannot rename the listed directory.
Possible Solutions
1053020 Error writing file: fileName
Possible Problems
Essbase cannot write the listed file.
Possible Solutions
- Make sure that you have enough disk space.
If you do not have enough disk space, consider
spanning disk volumes.
- Make sure that the virtual memory is two to three times larger than the
physical memory.
- If the listed file is
essbase.sec
, check to see if the
security file is corrupt.
1053021 Cannot copy object objectName to itself
Possible Problems
Essbase cannot copy the listed object to itself.
Possible Solutions
Check the syntax of the ESSCMD commands.
1053022 Database databaseName is in read-only mode for
backup
Possible Problems
The listed database is in read-only mode because the administrator issued the BEGINARCHIVE
command to back up the database.
Possible Solutions
Wait until the archival process, starting with the
BEGINARCHIVE command and
ending with the ENDARCHIVE command,
is finished. If the archival process has finished, be sure to issue the ENDARCHIVE command.
1053023 User's log message: messageText
This information message was created using
EssWriteToLogFile. There
is nothing wrong.
1053024 Cannot create temporary file
Possible Problems
Essbase cannot open a temporary file. Essbase needs to open
the temporary file to create an object, such as a rules file, before
saving the object to the remote OLAP Server computer.
Possible Solutions
- Make sure that you have enough disk space.
- Make sure that you have the correct operating system privileges to create the temporary
file.
- If you are on a UNIX computer and are using the
TMPDIR
environment
variable, make sure that the full path to the TMPDIR
directory is
not more than 15 characters.
1054001 Cannot load application applicationName with
error number number - see server log file
Possible Problems
Essbase cannot load the listed application because of the listed error.
Possible Solutions
- Check the OLAP Server log for more details
about the listed error.
- Check to see if the listed application is
corrupt.
- Increase the values for NETDELAY
and NETRETRYCOUNT.
- Make sure that the block size is
within the recommended range.
- Make sure that the following environment
variables are set correctly:
ARBORPATH
(PC and UNIX)
PATH
(PC and UNIX)
LD_LIBRARY_PATH
(UNIX only)
- Make sure that OLAP Server and the Essbase client are installed correctly.
- Run
REGISTER.EXE
again to make sure that your license number is
correct and that your ports are activated. Consult the Essbase Installation
Guide.
- If the application was copied or deleted using file system controls (such as
Windows Explorer or the
cp
or rm
commands), create a
dummy application with the original name and use Essbase
copy or
delete the application correctly.
1054002 Loading application applicationName is not currently permitted
Possible Problems
Essbase cannot load the listed application.
Possible Solutions
See Also
1054009, 1054011
1054003 Error number loading application: applicationName
Possible Problems
Essbase cannot load the listed application.
Possible Solutions
- Stop and restart OLAP Server.
- Copy the
$ARBORPATH/app/applicationName/databaseName/databaseName.dbb
file
to $ARBORPATH/app/applicationName/databaseName/databaseName.db
.
- Check to see if the database is corrupt.
- Run only one application at a time.
- Delete the
$ARBORPATH/app/applicationName/databaseName/databaseName.esm
file,
stop and restart OLAP Server, and try to open the application again.
1054004 Application applicationName is not loaded
Possible Problems
Essbase tried to perform an operation on the listed application, but the application was not loaded.
Possible Solutions
Make sure that you load an application before you use
it.
1054005 Shutting down application applicationName
This information message states that Essbase shut down the listed
application. There is nothing wrong.
1054006 Cannot terminate application applicationName
Possible Problems
Essbase cannot stop the listed application.
Possible Solutions
Make sure that OLAP Server is running.
1054007 Application applicationName not responding
Possible Problems
Essbase cannot connect to the listed application.
Possible Solutions
- Make sure that Essbase is installed correctly. If necessary, reinstall Essbase.
- Make sure that the following environment
variables are set correctly:
ARBORPATH
(PC and UNIX)
PATH
(PC and UNIX)
LD_LIBRARY_PATH
(UNIX only)
- Stop and restart OLAP Server.
- Make sure that the block size is in the recommended range.
- Increase the data cache size to hold at least 100 blocks.
- Increase the values for NETDELAY and NETRETRYCOUNT.
- Check for the
$ARBORPATH/app/applicationName/databaseName/databaseName.db
file. If
there is no databaseName.db
file, rename the databaseName.dbb
file to
databaseName.db
.
- Check for the
$ARBORPATH/app/applicationName/databaseName/databaseName.app
file. If
there is no databaseName.app
file, rename the databaseName.apb
file to
databaseName.app
.
- Check to see if the database is corrupt.
1054009 Application applicationName is currently not accepting connections
Possible Problems
Users cannot log on to the listed application.
Possible Solutions
In Application Manager, make sure that Allow Connects is checked.
In ESSCMD, make sure that you are using the ENABLELOGIN command correctly.
See Also
1054002, 1054011
1054010 Application applicationName is currently not accepting user commands
This information message states that the listed application is performing an operation that
requires exclusive control, such as a calculation. There is nothing wrong.
1054011 Loading database databaseName is not currently permitted
Possible Problems
Essbase cannot load the listed database.
Possible Solutions
In Application Manager, make sure that Allow Database to Start is checked.
See Also
1054002, 1054009
1054012 Invalid syntax in filter line incorrectFilter
Possible Problems
The security filter had a syntax error.
Possible Solutions
Make sure that you created the filter correctly.
See Also
1054013
1054013 Syntax error loading filters - operation canceled
Possible Problems
Essbase cannot load the security filters.
Possible Solutions
Make sure that you created the filters correctly.
See Also
1054012
1054014 Database databaseName loaded
This information message states that the listed database loaded correctly. There is nothing wrong.
1054016 Invalid file name fileName. operation aborted
Possible Problems
Essbase cannot create the listed index or page file.
This error occurs when Essbase tries to create the nth index or page file for an
application where n is greater than 5 digits, that is, greater than 99999.
Possible Solutions
Contact Hyperion Technical Support.
1054017 Cannot read from file with handle number, operation failed
Possible Problems
Essbase cannot perform the listed operation.
Possible Solutions
Check to see if the database is corrupt.
1054018 RECEIVED ABNORMAL SHUTDOWN COMMAND - ESSBASE TERMINATING
Possible Problems
Essbase shut down because it received an invalid shutdown command.
Possible Solutions
- Do not close the OLAP Server window by clicking the "X" in the title bar.
- Make sure that the Essbase computer has enough resources. Consult the
Essbase Installation Guide for a list of system requirements. If a
resource-intensive application, such as a relational database, is running on the same computer,
the resource-intensive application may be using the resources that Essbase needs.
- After you restart OLAP Server, check to see if the database is corrupt.
1054019 Cannot modify settings for application applicationName while
application is loaded and user who has modified the settings is logged in
Possible Problems
Essbase cannot modify the settings for the listed application.
Possible Solutions
- Log off other users.
- Unload the application.
- Reload the application.
- Change the settings. Make sure you are using the
SETAPPSTATE command
correctly.
1054020 *** Missing command line password!
Possible Problems
Essbase cannot start because the command line password was not issued.
Possible Solutions
When you start Essbase to run in the background (using the -b
switch), make sure to enter the system
password on the command line.
1054021 Cannot modify settings for application
applicationName. See server log for more information
Possible Problems
The listed application was not loaded.
Possible Solutions
Issue the UNLOADAPP and
LOADAPP commands before the
ENABLELOGIN command.
Look in the
applicationName.log
file for more information.
1054022 Cannot copy application applicationName while
database databaseName is in archive or read only mode
Possible Problems
The database was in read-only mode because someone was archiving the database.
Possible Solutions
Wait until the archival process, starting with the
BEGINARCHIVE command and
ending with the ENDARCHIVE command,
is finished. If the archival process is finished, be sure to issue the ENDARCHIVE command.
1054023 Cannot modify settings for application applicationName while
database databaseName is in archive or read only mode
Possible Problems
The database was in read-only mode because someone was archiving the database.
Possible Solutions
Wait until the archival process, starting with the BEGINARCHIVE command and
ending with the ENDARCHIVE command,
is finished. If the archival process is finished, be sure to issue the ENDARCHIVE command.
1054025 Cannot rename application applicationName while
database databaseName is in archive or read only mode
Possible Problems
The database was in read-only mode because someone was archiving the database.
Possible Solutions
Wait until the archival process, starting with the BEGINARCHIVE command and
ending with the ENDARCHIVE command, is
finished. If the archival process is finished, be sure to issue the ENDARCHIVE command.
1054026 Cannot create a new database in application applicationName while
database databaseName is in archive or read only mode
Possible Problems
The database was in read-only mode because someone was archiving the database.
Possible Solutions
Wait until the archival process, starting with the BEGINARCHIVE command and
ending with the ENDARCHIVE command,
is finished. If the archival process is finished, be sure to issue the ENDARCHIVE command.
1054027 Application applicationName started with process id number
This information message states the process ID assigned to the listed application by
the operating system. There is nothing wrong.
1054029 Invalid parameter values for database file information request.
Possible Problems
The API or ESSCMD command did not supply enough information about the Essbase database.
Possible Solutions
Make sure that each ESSCMD command or API command contains correct information.
Make sure that each ESSCMD command or API command contains all required parameters.
1054030 Select for application applicationName failed, error number
Possible Problems
Essbase cannot select the listed application.
Possible Solutions
- Make sure that you are using the SELECT command correctly.
- Make sure that the listed application is running and that you can select it from Application Manager. If not, make
sure that OLAP Server is running on the listed computer.