1051002

Unrecognized command: command name

Most likely indicates a version mismatch between Essbase Server and client.

Ensure that the Essbase Server and client versions are compatible.

1051003

Error error number processing request name of failed request -- disconnecting

The request that failed.

Requests generally fail due to an error condition that exists before the request is issued.

Review your log, and find and correct the error that precedes the failed request.

1051004

Logins are currently not permitted

Maintenance is being performed on the database and logins are not permitted during maintenance.

Try logging in later or see your Essbase system administrator.

1051006

Disconnecting user user name from application appName

You exited an application.

Generally this occurs when you log on to another application.

1051009

Setting application appName active for user user name

You are logged on to an application.

1051011

System timed out error number

Most likely, too many users are on the system, or there may be other resource constraints.

Try logging in later or see your Essbase system administrator.

1051012

User user name does not exist

You are attempting to perform maintenance or administrative processes on a user that does not exist.

You are attempting to log in with an invalid user ID.

Verify the user name.

1051013

User/group user name/group name does not exist

You are attempting to perform maintenance or administrative processes on a user that does not exist.

Verify the user or group name.

1051014

User/group user name/group name already exists

You are attempting to create a user or group with a name already assigned to a user or group.

Use another user name or group name.

1051016

Cannot rename yourself!

Your privileges are insufficient to rename yourself.

See your Essbase system administrator.

1051017

Cannot delete yourself!

Your privileges are insufficient to delete yourself.

See your Essbase system administrator.

1051018

Cannot rename to same name!

You are attempting to change a user name to their current name.

Use another user name.

1051019

Cannot alter your own access level

Your privileges are insufficient to alter your access level.

See your Essbase system administrator.

1051020

Cannot log yourself out!

Message intended for administrators.

Your privileges are insufficient to log yourself out.

See your Essbase system administrator.

1051021

You have been logged out due to inactivity or explicitly by the supervisor.

The system logged you off because of extended inactivity.

Your system administrator or supervisor has logged you off.

Log in to the system and resume your processes.

See your system administrator or supervisor.

1051022

Password too short -- must be at least number characters

The password you created does not meet the minimum number of characters. This number is set by your system administrator. The default value is six.

Create a password that contains more characters.

1052001

Related Topics

1006010

1052002

Error reading from server

Essbase cannot read from Essbase Server, probably because Essbase Server was stopped incorrectly.

Determine whether Essbase Server is running:

Ensure that these environment variables are set correctly (see Setting Environment Variables):

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

If you just migrated, ensure that you followed the migration information correctly. Check the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.

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

Determine whether the security file is corrupt.

If you are on a UNIX computer, check the user limit profile (see Checking the User Limit Profile).

Determine whether any databases are corrupt (see Checking for Database Corruption).

1052002

Related Topics

1052001

Error writing to server

Essbase cannot write to Essbase Server, probably because Essbase Server was stopped incorrectly.

Determine whether Essbase Server is running:

Ensure that the block size is within the recommended range.

If you just migrated, ensure that you followed the migration information correctly. Check the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.

Determine whether the security file is corrupt.

Ensure that disk space is adequate.

Determine whether any databases are corrupt (see Checking for Database Corruption).

1052003

Timed out reading from server

Essbase timed out before it could read from the server.

Ensure that the block size is within the recommended range.

Ensure that these environment variables are set correctly (see Setting Environment Variables):

Ensure that the network is functioning correctly. Check the previous messages in the application log for network error messages (see 1040002 to 1042025: Network Messages).

Stop and restart Essbase Server.

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

Increase the values for AGENTDELAY.

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

Determine whether any databases are corrupt (see Checking for Database Corruption).

1052004

Timed out writing to server

Essbase timed out before it could write to the server.

Ensure that the block size is within the recommended range.

Ensure that these environment variables are set correctly (see Setting Environment Variables):

Ensure that the network is functioning correctly. Check the previous messages in the application log for network error messages (see 1040002 to 1042025: Network Messages).

Stop and restart Essbase Server.

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

Increase the values for AGENTDELAY.

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

Determine whether any databases are corrupt (see Checking for Database Corruption).

1052005

You have been forced to disconnect from the selected application

Essbase has no connection to the selected application.

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

Related Topics

1003022

Cannot open object file: fileName

Essbase cannot open the listed file.

Ensure that your operating system privileges are correct 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 to copy or delete the application correctly.

Ensure that the block size is within the recommended range.

Ensure that the file name (including the entire path) 256 characters or less. If the length exceeds 256 characters, the file name is truncated in the error message.

See if another user has locked the file (see Unlocking Objects).

Ensure that the file exists. If the file does not exist, restore the file from backups.

Ensure that memory is adequate.

If the listed file is essbase.sec:

If you are using the BEGINARCHIVE command, specify a directory for the archive.

Stop and restart Essbase Server.

1053002

Cannot create application directory: directoryName operatingSystemErrorCode

Essbase cannot create the listed application directory.

Ensure that your operating system privileges are correct for the listed file and directory.

Ensure that disk space is adequate.

Ensure that these environment variables are set correctly (see Setting Environment Variables):

1053003

Application directory does not exist: directoryName

Essbase cannot find the listed application 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 to copy or delete the application correctly.

Ensure that the directory exists in the correct location.

Ensure that your operating system privileges are correct for the listed directory.

See if another user has locked the directory (see Unlocking Objects).

Ensure that these environment variables are set correctly (see Setting Environment Variables):

Ensure that the security file is not corrupt.

If you are using ESSCMD, ensure that the correct application directory is specified in the ESSCMD command.

1053004

Cannot create database directory: directoryName operatingSystemErrorCode

Essbase cannot create the listed database directory.

Ensure that your operating system privileges are correct for the listed file and directory.

Ensure that disk space is adequate.

Ensure that these environment variables are set correctly (see Setting Environment Variables):

1053005

Database directory does not exist: directoryName

Essbase cannot find the listed database 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 to copy or delete the application correctly.

Ensure that the directory exists in the correct location.

Ensure that your operating system privileges are correct for the listed directory.

See if another user has locked the directory (see Unlocking Objects).

Ensure that these environment variables are set correctly (see Setting Environment Variables):

Ensure that the security file is not corrupt.

If you are using ESSCMD, ensure that the correct application directory is used in the ESSCMD command.

1053006

Invalid object type

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.

Ensure that Essbase Server and the client (such as Spreadsheet Add-in) are at the same release level.

1053007

Cannot rename object originalName to newName

Essbase cannot rename the listed object.

Ensure that your operating system privileges are correct for the listed object.

Ensure that the new name is valid.

Ensure that an object using the new name does not exist.

1053008

Cannot create object objectName

The operating system is not allowing Essbase to create the listed object.

Ensure that your operating system privileges are correct for the listed object.

Ensure that the object name is valid.

Ensure that the object name (including the entire path) is not more than 256 characters. If it is longer than 256 characters, the object name is truncated in the error message.

1053009

Cannot delete object objectName

The operating system is not allowing Essbase to delete the listed object.

Ensure that your operating system privileges are correct for the listed object.

Ensure that the object name is valid.

1053010

Object objectName is already locked by user userName

The object you are trying to lock is locked by the listed user.

Wait a few minutes to allow the other active user's process to finish and retry the operation.

If necessary, unlock the file (see Unlocking Objects).

If this error happens frequently, ensure that users are logging off Essbase correctly.

Stop and restart Essbase Server.

1053011

Object objectName is not locked by user userName

Essbase cannot unlock the listed object because it is not locked.

See if another user has locked the file (see Unlocking Objects).

Stop and restart Essbase Server.

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

1053012

Object objectName is locked by user userName

The listed object is locked by the listed user.

Wait a few minutes to allow the other active user's process to finish and retry the operation.

If necessary, unlock the file (see Unlocking Objects).

If this occurs frequently, ensure that users are logging off Essbase correctly.

Stop and restart Essbase Server.

1053013

Object objectName unlocked by user userName

The listed object was unlocked by the listed user.

Not applicable

1053014

Object objectName does not exist

Essbase cannot find the listed object.

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, ensure that the listed file exists at the source and at the target.

Determine whether the security file is corrupt.

Ensure that disk space is adequate.

1053015

Object objectName already exists

Essbase cannot create the listed object because it exists.

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

Essbase cannot open a temporary file to save the security file.

Ensure that disk space is adequate.

Ensure that your operating system privileges are correct.

1053017

Cannot open log file for application appName

Essbase cannot open the application log file for the listed application.

Ensure that your operating system privileges are correct for the listed application.

Make yourEssbase permissions are correct for the listed file.

Ensure that disk space is adequate.

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

Essbase cannot perform the operation on outline objects.

You cannot delete, copy, or rename an outline. Instead you must delete, copy, or rename the database.

1053019

Cannot rename directory: oldDirectoryName operatingSystemErrorCode

Essbase cannot rename the listed directory.

See if another user has locked the file (see Unlocking Objects).

Ensure that the new directory name does not match an existing directory name.

Make your operating system privileges are correct for the old and new directories.

Ensure that yourEssbase permissions are correct for the listed old directory.

Determine whether the security file is corrupt.

Stop and restart the application. If that does not work, stop and restart Essbase Server.

Ensure that disk space is adequate.

Close Windows Explorer. Sometimes Explorer can hold the directory open, which can lead to the error.

If the suggested solutions do not work, create a new application and database and copy the outline and other objects to the new application and database. When you are finished, ensure that the new application and database are not corrupt (see Checking for Database Corruption).

Ensure that the OLAP Server is running.

1053020

Error writing file: fileName

Essbase cannot write the listed file.

Ensure that disk space is adequate. If disk space is insufficient , consider spanning disk volumes.

Ensure that virtual memory is two to three times larger than physical memory.

If the listed file is essbase.sec, determine whether the security file is corrupt.

1053021

Cannot copy object objectName to itself

Essbase cannot copy the listed object to itself.

Check the syntax of the ESSCMD commands.

1053022

Database databaseName is in read-only mode for backup

The listed database is in read-only mode because the administrator issued the BEGINARCHIVE command to back up the database.

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

You created this message using EssWriteToLogFile.

Not applicable

1053024

Cannot create temporary file

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 Essbase Server computer.

Ensure that disk space is adequate.

Ensure that your operating system privileges are correct to create the temporary file.

If you are on a UNIX computer and are using the TMPDIR environment variable, ensure that the full path to the TMPDIR directory does not exceed 15 characters.

1054001

Cannot load application appName with error number number - see server log file

Essbase cannot load the listed application because of the listed error.

Check the Essbase Server log for more details about the listed error.

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

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

Ensure that the block size is within the recommended range.

Ensure that these environment variables (see Setting Environment Variables) are set correctly:

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

Run REGISTER.EXE again to ensure that ports are activated. Consult the Oracle Hyperion Enterprise Performance Management System Installation and Configuration 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

Related Topics

1054009

1054011

Loading application appName is not currently permitted

Essbase cannot load the listed application.

In Administration Services, ensure that “Allow users to start application” is selected.

Delete all essXXXX.tmp files in the ARBORPATH/app/appName/databaseName directory.

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

1054003

Error number loading application: appName

Essbase cannot load the listed application.

Stop and restart Essbase Server.

Copy the ARBORPATH/app/appName/databaseName/databaseName.dbb file to ARBORPATH/app/appName/databaseName/databaseName.db.

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

Run only one application at a time.

Delete the ARBORPATH/app/appName/databaseName/databaseName.esm file, stop and restart Essbase Server, and try to open the application again.

1054004

Application appName is not loaded

Essbase tried to perform an operation on the listed application, but the application was not loaded.

Ensure that you load an application before you use it.

1054005

Shutting down application appName

Essbase shut down the listed application.

Not applicable

1054006

Cannot terminate application appName

Essbase cannot stop the listed application.

Ensure that Essbase Server is running.

1054007

Application appName not responding

Essbase cannot connect to the listed application.

Ensure that Essbase is installed correctly. If necessary, reinstall Essbase.

Ensure that these environment variables (see Setting Environment Variables) are set correctly:

Stop and restart Essbase Server.

Ensure 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 (see Setting NETDELAY and NETRETRYCOUNT).

Check for the ARBORPATH/app/appName/databaseName/databaseName.db file. If databaseName.db does not exist, rename the databaseName.dbb file to databaseName.db.

Check for the ARBORPATH/app/appName/databaseName/databaseName.app file. If databaseName.app file does not exist, rename the databaseName.apb file to databaseName.app.

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

1054009

Related Topics

1054002

1054011

Application appName is currently not accepting connections.

Users cannot log on to the listed application.

In Administration Services, ensure that “Allow Connections” is selected.

In ESSCMD, ensure that you are using the ENABLELOGIN command correctly.

1054010

Application appName is currently not accepting user commands

The listed application is performing an operation that requires exclusive control, such as a calculation.

Not applicable

1054011

Related Topics

1054002

1054009

Loading database databaseName is not currently permitted

Essbase cannot load the listed database.

In Administration Services, ensure that “Allow Database to Start” is selected.

1054012

Related Topics

1054013

Invalid syntax in filter line incorrectFilter

The security filter had a syntax error.

Ensure that you created the filter correctly.

1054013

Related Topics

1054012

Syntax error loading filters - operation canceled

Essbase cannot load the security filters.

Ensure that you created the filters correctly.

1054014

Database databaseName loaded

The listed database loaded correctly.

Not applicable

1054016

Invalid file name fileName. operation aborted

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.

Contact Oracle Support.

1054017

Cannot read from file with handle number, operation failed

Essbase cannot perform the listed operation.

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

1054018

RECEIVED ABNORMAL SHUTDOWN COMMAND - ESSBASE TERMINATING

Essbase shut down because it received an invalid shutdown command.

Do not close the Essbase Server window by clicking the "X" in the title bar.

Ensure that the Essbase computer has enough resources. Consult the Oracle Hyperion Enterprise Performance Management System Installation Start Here for 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 Essbase Server, determine whether the database is corrupt (see Checking for Database Corruption).

1054019

Cannot modify settings for application appName while application is loaded and user who has modified the settings is logged in

Essbase cannot modify the settings for the listed application.

1054020

*** Missing command line password!

Essbase cannot start because the command line password was not issued.

When you start Essbase to run in the background (using the -b switch), ensure that you enter the system password on the command line.

1054021

Cannot modify settings for application appName. See server log for more information

The listed application was not loaded.

Issue the UNLOADAPP and LOADAPP commands before the ENABLELOGIN command.

See appName.log.

1054022

Cannot copy application appName while database databaseName is in archive or read only mode

The database was in read-only mode because someone was archiving the database.

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 appName while database databaseName is in archive or read only mode

The database was in read-only mode because someone was archiving the database.

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 appName while database databaseName is in archive or read only mode

The database was in read-only mode because someone was archiving the database.

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 appName while database databaseName is in archive or read only mode

The database was in read-only mode because someone was archiving the database.

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 appName started with process id number

Process ID assigned to the listed application by the operating system.

Not applicable

1054029

Invalid parameter values for database file information request.

The API or ESSCMD command did not supply enough information about the Essbase database.

Ensure that each ESSCMD command or API command contains correct information.

Ensure that each ESSCMD command or API command contains all required parameters.

1054030

Select for application appName failed, error number

Essbase cannot select the listed application.

Ensure that you are using the SELECT command correctly.

Ensure that the listed application is running and that you can select it from Oracle Essbase Administration Services. If not, ensure that Essbase Server is running on the listed computer.

1055041

Cannot create daemon thread.

The agent cannot initialize the daemon thread or one of its internal threads.

Available memory is insufficient to initialize the process.

Restart your process.