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.
Showing posts with label Agent Errors. Show all posts
Showing posts with label Agent Errors. Show all posts
Tuesday, October 23, 2007
1054018 RECEIVED ABNORMAL SHUTDOWN COMMAND - ESSBASE TERMINATING
Possible Problems
Analytic Services shut down because it received an invalid shutdown command.
Possible Solutions
Do not close the Analytic Server window by clicking the "X" in the title bar.
Make sure that the Analytic Services computer has enough resources. Consult the Analytic Services 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 Analytic Services needs.
After you restart Analytic Server, check to see if the database is corrupt.
Analytic Services shut down because it received an invalid shutdown command.
Possible Solutions
Do not close the Analytic Server window by clicking the "X" in the title bar.
Make sure that the Analytic Services computer has enough resources. Consult the Analytic Services 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 Analytic Services needs.
After you restart Analytic Server, check to see if the database is corrupt.
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.
The security filter had a syntax error.
Possible Solutions
Make sure that you created the filter correctly.
1054011 Loading database databaseName is not currently permitted
Possible Problems
Analytic Services cannot load the listed database.
Possible Solutions
In Administration Services, make sure that Allow Database to Start is checked.
Analytic Services cannot load the listed database.
Possible Solutions
In Administration Services, make sure that Allow Database to Start is checked.
1054009 Application applicationName is currently not accepting connections
Possible Problems
Users cannot log on to the listed application.
Possible Solutions
In Administration Services, make sure that Allow Connects is checked.
In ESSCMD, make sure that you are using the ENABLELOGIN command correctly.
Users cannot log on to the listed application.
Possible Solutions
In Administration Services, make sure that Allow Connects is checked.
In ESSCMD, make sure that you are using the ENABLELOGIN command correctly.
1054007 Application applicationName not responding
Possible Problems
Analytic Services cannot connect to the listed application.
Possible Solutions
Make sure that Analytic Services is installed correctly. If necessary, reinstall Analytic Services.
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 Analytic 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.
Analytic Services cannot connect to the listed application.
Possible Solutions
Make sure that Analytic Services is installed correctly. If necessary, reinstall Analytic Services.
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 Analytic 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.
1054006 Cannot terminate application applicationName
Possible Problems
Analytic Services cannot stop the listed application.
Possible Solutions
Make sure that Analytic Server is running.
If Analytic Server is not running, restart Analytic Server.
If Analytic Server crashed, follow the procedures for an abnormal shutdown.
If Analytic Server is frozen, stop Analytic Server and follow the procedures for an abnormal shutdown. If you cannot stop Analytic Server using the standard methods, end the task.
Analytic Services cannot stop the listed application.
Possible Solutions
Make sure that Analytic Server is running.
If Analytic Server is not running, restart Analytic Server.
If Analytic Server crashed, follow the procedures for an abnormal shutdown.
If Analytic Server is frozen, stop Analytic Server and follow the procedures for an abnormal shutdown. If you cannot stop Analytic Server using the standard methods, end the task.
1054004 Application applicationName is not loaded
Possible Problems
Analytic Services 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.
Analytic Services 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.
1054003 Error number loading application: applicationName
Possible Problems
Analytic Services cannot load the listed application.
Possible Solutions
Stop and restart Analytic 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 Analytic Server, and try to open the application again.
Analytic Services cannot load the listed application.
Possible Solutions
Stop and restart Analytic 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 Analytic Server, and try to open the application again.
1054002 Loading application applicationName is not currently permitted
Possible Problems
Analytic Services cannot load the listed application.
Possible Solutions
In Administration Services, make sure that Allow users to start application is selected.
Delete all essXXXX.tmp files in the $ARBORPATH\APP\applicationName\databaseName directory.
Check to see if the database is corrupt.
Analytic Services cannot load the listed application.
Possible Solutions
In Administration Services, make sure that Allow users to start application is selected.
Delete all essXXXX.tmp files in the $ARBORPATH\APP\applicationName\databaseName directory.
Check to see if the database is corrupt.
1054001 Cannot load application applicationName with error number number - see server log file
Possible Problems
Analytic Services cannot load the listed application because of the listed error.
Possible Solutions
Check the Analytic 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 Analytic Server and the Analytic Services 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 Analytic Services 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 Analytic Services copy or delete the application correctly.
Analytic Services cannot load the listed application because of the listed error.
Possible Solutions
Check the Analytic 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 Analytic Server and the Analytic Services 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 Analytic Services 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 Analytic Services copy or delete the application correctly.
1053024 Cannot create temporary file
Possible Problems
Analytic Services cannot open a temporary file. Analytic Services needs to open the temporary file to create an object, such as a rules file, before saving the object to the remote Analytic 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.
Analytic Services cannot open a temporary file. Analytic Services needs to open the temporary file to create an object, such as a rules file, before saving the object to the remote Analytic 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.
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.
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.
1053021 Cannot copy object objectName to itself
Possible Problems
Analytic Services cannot copy the listed object to itself.
Possible Solutions
Check the syntax of the ESSCMD commands.
Analytic Services cannot copy the listed object to itself.
Possible Solutions
Check the syntax of the ESSCMD commands.
1053020 Error writing file: fileName
Possible Problems
Analytic Services 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.
Analytic Services 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.
1053019 Cannot rename directory: oldDirectoryName operatingSystemErrorCode
Possible Problems
Analytic Services cannot rename the listed directory.
Possible Solutions
See if another user has locked the file.
Make sure there is not another directory with the same name as the new directory.
Make sure that you have the correct operating system privileges for the old and new directories.
Make sure that you have the correct Analytic Services permissions for the listed old directory.
Check to see if the security file is corrupt.
Stop and restart the application. If that does not work, stop and restart Analytic Server.
Make sure that you have enough disk space.
Close Windows Explorer. Sometimes Explorer can hold the directory open, which can lead to the error.
If none of these suggested solutions work, create a new application and database and copy the outline and other objects to the new application and database. When you are finished, make sure that the new application and database are not corrupt.
Make sure the OLAP Server is running.
If Analytic Server is not running, restart Analytic Server.
If Analytic Server crashed, follow the procedures for an abnormal shutdown.
If Analytic Server is frozen, stop Analytic Server and follow the procedures for an abnormal shutdown. If you cannot stop Analytic Server using the standard methods, end the task.
Analytic Services cannot rename the listed directory.
Possible Solutions
See if another user has locked the file.
Make sure there is not another directory with the same name as the new directory.
Make sure that you have the correct operating system privileges for the old and new directories.
Make sure that you have the correct Analytic Services permissions for the listed old directory.
Check to see if the security file is corrupt.
Stop and restart the application. If that does not work, stop and restart Analytic Server.
Make sure that you have enough disk space.
Close Windows Explorer. Sometimes Explorer can hold the directory open, which can lead to the error.
If none of these suggested solutions work, create a new application and database and copy the outline and other objects to the new application and database. When you are finished, make sure that the new application and database are not corrupt.
Make sure the OLAP Server is running.
If Analytic Server is not running, restart Analytic Server.
If Analytic Server crashed, follow the procedures for an abnormal shutdown.
If Analytic Server is frozen, stop Analytic Server and follow the procedures for an abnormal shutdown. If you cannot stop Analytic Server using the standard methods, end the task.
1053018 Operation not permitted on outline objects
Possible Problems
Analytic Services 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.
Analytic Services 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.
1053017 Cannot open log file for application applicationName
Possible Problems
Analytic Services 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 Analytic Services 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 Analytic Services copy or delete the application correctly.
Analytic Services 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 Analytic Services 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 Analytic Services copy or delete the application correctly.
1053016 Cannot open temporary file
Possible Problems
Analytic Services 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.
Analytic Services 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.
1053015 Object objectName already exists
Possible Problems
Analytic Services 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 Analytic Services copy or delete the application correctly.
Analytic Services 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 Analytic Services copy or delete the application correctly.
Subscribe to:
Posts (Atom)