This document provides a list of error messages that you may see when using the Configuration Manager to per- form task such as: configuring, assembling, deploying, bootstrapping LiveCycle products. The error messages are organized based on message type:
Internal messages: These messages occur during the installation of a LiveCycle product.
Configuration messages: These messages occur when you are running Configuration Manager to complete the configuration of products and required components.
Assembly messages: These messages occur when you are running Configuration Manager to complete the configuration of a LiveCycle product.
Database initialization messages: These messages occur when you are completing the database initializa- tion with Configuration Manager to assemble product EAR files.
Turnkey messages: These messages occur during the turnkey deployment of products.
Internal messages
Configuration Manager Error Messages
Number Error
message
Possible Cause Action
LCMerror Unexpected error occurred.
An unexpected error occurred.
Review the Configuration Manager log files. The lcm.log file is located in the LiveCycle root/
configurationManager/ directory.
If you cannot solve the problem, send the log file to customer support.
LCMerror1 Configuration manager could not be initialized. An invalid state may be present.
File names or contents may have been modified or deleted since the original installation. Affected files and directories could include Configuration Manager con- figuration files, the LiveCycle root/configurationManager/
scripts directory, the LiveCycle root/configurationManager/
deploy directory, or the LiveCycle root/configurationManager/
lib directory.
The log files should provide details to determine the exact cause.
Reinstall the LiveCycle product.
Review the Configuration Manager log files. The lcm.log file is in the LiveCycle root\
configurationManager\ directory.
If you cannot solve the problem, send the log file to customer support.
LCMerror100 Configuration manager scripts could not be copied to working directory.
Either the LiveCycle source files could not be found or the target files could not be written.
If the problem is with the source files (LiveCycle root/
configurationManager/scripts), reinstall the LiveCycle product.
If the problem is with the target files (LiveCycle root/
configurationManager/working), there may be an issue with disk space and disk privileges.
LCMerror101 LiveCycle modules compo- nent could not be copied to working directory.
Either the LiveCycle
product component source files could not be found or the target files could not be written.
If the problem is with the source files (LiveCycle root/
configurationManager/scripts), reinstall the LiveCycle product.
If the problem is with the target files (LiveCycle root/
configurationManager/working), there may be an issue with disk space and disk privileges.
LCMerror102 Product license information required for assembly could not be generated.
Either the LiveCycle product license source files could not be found or the target files could not be written.
If the problem is with the source files (LiveCycle root/
configurationManager/scripts), reinstall the LiveCycle product.
If the problem is with the target files (LiveCycle root/
configurationManager/working), there may be an issue with disk space and disk privileges.
LCMerror103 Working directory could not be cleaned.
Some of the files in the LiveCycle root/configuration- Manager/ working directory may be open or in use.
Restarting or closing other ap- plications may release these files and allow them to be cleaned.
To verify the source of the prob- lem, refer to the Configuration Manager log files. The lcm.log file is in the LiveCycle root/configura- tionManager/ directory. Also, look at the files that remain and, of these, the ones that are open.
LCMerror1000 Configuration of module(s) could not be completed successfully.
Either the LiveCycle product source files could not be found or the target files could not be written.
Review the Configuration Man- ager log files. The lcm.log file is located in the LiveCycle root/con- figurationManager directory.
If you cannot figure out the prob- lem, send the log file to support.
LCMerror1001 Configuration of
module(s) using advanced configurations could not be completed successfully.
Either the LiveCycle product source files could not be found or the target files could not be written.
Configurations are defined in LiveCycle root/configuration- Manager/advComponent- Configurations.xml.
If the problem is with the source files (LiveCycle root/
configurationManager/scripts), reinstall the LiveCycle product.
If the problem is with the target files (LiveCycle root/
configurationManager/working), there may be an issue with disk space and disk privileges.
LCMerror1002 Configuration of DataManager Module service could not be com- pleted successfully.
Either the LiveCycle product source files could not be found or the target files could not be written.
If the problem is with the source files (LiveCycle root/configura- tionManager/working/csa/app server/war/DataManagerSer- vices.war), reinstall the LiveCycle product.
LCMerror1003 Configuration of FontManager Module could not be completed successfully.
Either the LiveCycle product source files could not be found or the target files could not be written.
If the problem is with the source files (LiveCycle root/
configurationManager/working/
fontmanager/appserver/
FontManager.war), reinstall the LiveCycle product.
If the problem is with the target files (LiveCycle root/
configurationManager/working/
fontmanager/appserver/
FontManager.war), there may be an issue with disk space and disk privileges.
Ensure that you have the recom- mended 1 GB of disk space.
LCMerror1004 Configuration of Reader Extensions module could not be completed successfully.
Either the LiveCycle product source files could not be found or the target files could not be written.
If the problem is with the source files, reinstall the LiveCycle product.
If the problem is with the target files, there may be an issue with disk space and disk privileges.
Configuration Manager messages
Assembly messages
LCMerror2000 Assembly of product(s) could not be completed successfully.
Either the LiveCycle product source files may be missing for assembly or the target files could not be written.
If the problem is with the source files (LiveCycle root/
configurationManager/scripts), reinstall the LiveCycle product.
If the problem is with the target files (LiveCycle root/
configurationManager/working), there may be an issue with disk space and disk privileges.
Database initialization messages LCMerror3000 Bootstrapping of
product(s) could not be completed successfully.
Uunexpected bootstrapping error occurred.
Review the Configuration Man- ager log files. The lcm.log file is in the LiveCycle root/
configurationManager/ directory.
You should also review the server log files.
If you cannot solve the problem, send the log file to customer support.
LCMerror3001 Bootstrapping of product(s) could not be completed successfully.
Could not connect to bootstrap application:
Host not found.
Incorrect host information was entered during configu- ration. Database initialization failed due to the incorrect host information.
Run the Configuration Manager again and ensure that you enter the correct server name, and then continue on to database initializa- tion.
LCMerror3002 Bootstrapping of product(s) could not be completed success- fully. Could not connect to bootstrap application:
Invalid bootstrap request.
Error is internal. This error is internal and should not occur.
Run the Configuration Manager again and ensure that you enter the correct host and port infor- mation, and then continue on to database initialization.
LCMerror3003 Bootstrapping of product(s) could not be completed successfully.
Bootstrapping request failed on server. {0} boost- rapper failed.
The database initialization failed. There may be a prob- lem with your system envi- ronment, or the LiveCycle.ear file may not be deployed.
Verify that the LiveCycle product deployed properly and is avail- able to initialize the database.
Using Administrator, restart the LiveCycle.ear file. If the problem is not resolved, restart the applica- tion server.
LCMerror3004 Bootstrapping of product(s) could not be completed successfully.
Could not connect to bootstrap application:
Bootstrapping applica- tion not found on server;
deployment of bootstrap application may not have been successful.
The database initialization failed because the LCMBoot- strapper.war file was not deployed successfully.
Verify the deployment of the LCMBootstrapper.war file and the expected web context of the file.
For a turnkey installation, check the error logs for deployment errors.
For a manual installation, check the application server status utili- ties and log files.
LCMerror3005 Bootstrapping of product(s) could not be completed success- fully. Could not connect to bootstrap application: Port may be invalid.
Incorrect port information was entered during configu- ration. Database initialization failed due to the incorrect host information.
Run the Configuration Manager again and ensure that you enter the correct port information (ap- plication server computer port that hosts the LiveCycle product), and then continue on to database initialization.
LCMerror3006 Bootstrapping of product(s) could not be completed successfully.
Bootstrapping request failed on server: {0} boot- strapper is invalid.
Bootstrapping failed because the Configuration Manager attempted to bootstrap an unknown component.
This error is internal and should not occur.
Run the Configuration Manager again and ensure that you enter the correct information, and then continue on to database initializa- tion.
LCMerror3007 Bootstrapping of product(s) could not be completed successfully.
Could not establish a valid connection to server. Port may not be SSL enabled or certificates may not be trusted.
Invalid port or certificate information was entered dur- ing the configuration.
Run the Configuration Manager again and ensure that you enter the correct port and certificate information (application server computer port that hosts the LiveCycle product), and then con- tinue on to database initialization.
LCMerror3008 Bootstrapping of product(s) could not be completed successfully.
Error during SSL commu- nication with server.
SSL keystore and password information may be incor- rect, or the SSL port may not be available.
Run the Configuration Manager again and ensure that you enter the correct SSL information, and then continue on to database initialization.
LCMerror3009 Bootstrapping of product(s) could not be completed successfully.
Could not establish a valid connection to server.
Invalid port information was entered during configura- tion, or the server is down.
Ensure that the server is running, run the Configuration Manager again, and enter the correct port information, and then continue on to database initialization.
Turnkey messages
LCMerror9001 Turnkey service {0} does not exist.
Service does not exist. The installer may have failed to create the service or it was removed.
Check the Microsoft Windows service for the status of the service.
Reinstall the LiveCycle product using the turnkey or manual process.
LCMerror9003 Failed to stop turnkey service {0}.
Service may not be respond- ing to the stop command.
Verify the status of the service us- ing the Windows service and then stop the service manually.
LCMerror9004 Failed to stop turnkey service {0}. Ports are still active.
Service could not be stopped because the required ports are still in use.
Verify the status of the service us- ing the Windows service and then stop the service manually.
LCMerror9005 Failed to start turnkey {0}.
Ports already in use.
Service may not be respond- ing to the start command.
Verify the status of the service us- ing the Windows service and then start the service manually.
LCMerror9007 Failed to start turnkey service {0}.
Either the JBoss ports (8080, 8083, 1099, 1098, 4444, 4445, 8009, 1162, 8090, 8092, 8093)) or the MySQL service port (3306) are in use.
Verify that no other JBoss services are running or another applica- tion that may use the same port.
LCMerror9010 Failed to deploy {0} to turnkey JBoss.
There are two possible causes for this error. Either the source files could not be found or the target files could not be written.
Files are deployed from the LiveCycle root/configuration- Manager/export directory to the JBoss root/server/all/de- ploy directory.
If it is a problem with the source files, reinstall the LiveCycle prod- uct.
If it is a problem with the target files, there may be an issue with disk space and disk privileges.
LCMerror9020 JBoss default web applica- tion not ready and acces- sible. Failed to start up or timed out.
JBoss service may have failed, or the time out has expired.
Check the JBoss log file, sever.log, in the Jboss root/server/all/log/
directory for details.
LCMerror9021 LCMBootstrapper web application not ready and accessible. Failed to start up or timed out.
LCMBootstrapper.war de- ployment may have failed.
Check the JBoss log file, sever.log, in the Jboss root/server/all/log/
directory for details.
Useful information includes any error messages, exception logs, or JBoss logging.
Adobe Systems Incorporated • 345 Park Avenue, San Jose, CA 95110-2704 USA • www.adobe.com
Adobe, the Adobe logo, and “Better by Adobe.” are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. All other trademarks are the property of their respective owners.
Copyright 2005 Adobe Systems Incorporated. All rights reserved.
