Configuration Manager Error Messages

Transcription

1 Adobe Enterprise & Developer Support Knowledge Article ID: c4698 bc Configuration Manager Error Messages This document provides a list of error messages that you may see when using the Configuration Manager to perform 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 initialization with Configuration Manager to assemble product EAR files. Turnkey messages: These messages occur during the turnkey deployment of products. Internal messages Number LCMerror Error message Unexpected error occurred. Possible Cause An unexpected error occurred. Action 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 configuration files, the LiveCycle root/configurationmanager/ scripts directory, the LiveCycle root/configurationmanager/ deploy directory, or the LiveCycle root/configurationmanager/ lib directory. 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. The log files should provide details to determine the exact cause.

2 Configuration Manager Error Messages 2 LCMerror100 Configuration manager scripts could not be copied to working directory. source files could not be found or the target files could not be written. LCMerror101 LCMerror102 LiveCycle modules component could not be copied to working directory. Product license information required for assembly could not be generated. product component source files could not be found or the target files could not be written. product license source files could not be found or the target files could not be written. 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 applications may release these files and allow them to be cleaned. To verify the source of the problem, refer to the Configuration Manager log files. The lcm.log file is in the LiveCycle root/configurationmanager/ directory. Also, look at the files that remain and, of these, the ones that are open.

3 Configuration Manager Error Messages 3 Configuration Manager messages LCMerror1000 module(s) could not be Review the Configuration Manager log files. The lcm.log file is located in the LiveCycle root/configurationmanager directory. If you cannot figure out the problem, send the log file to support. LCMerror1001 LCMerror1002 LCMerror1003 module(s) using advanced configurations could not be DataManager Module service could not be completed FontManager Module could not be completed Configurations are defined in LiveCycle root/configuration- Manager/advComponent- Configurations.xml. configurationmanager/working/csa/app server/war/datamanagerservices.war), reinstall the LiveCycle product. configurationmanager/working/ fontmanager/appserver/ FontManager.war), reinstall the LiveCycle product. configurationmanager/working/ fontmanager/appserver/ FontManager.war), there may be an issue with disk space and disk privileges. Ensure that you have the recommended 1 GB of disk space. LCMerror1004 Reader Extensions module could not be completed files, reinstall the LiveCycle product. files, there may be an issue with disk

4 Configuration Manager Error Messages 4 Assembly messages LCMerror2000 Assembly of product(s) could not be completed product source files may be missing for assembly or the target Database initialization messages LCMerror3000 Uunexpected bootstrapping error occurred. Review the Configuration Manager 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 Could not connect to bootstrap application: Host not found. Incorrect host information was entered during configuration. Database initialization failed due to the incorrect host information. the correct server name, and then continue on to database initialization. LCMerror3002 LCMerror3003 product(s) could not be Could not connect to bootstrap application: Invalid bootstrap request. Bootstrapping request failed on server. {0} boostrapper failed. Error is internal. The database initialization failed. There may be a problem with your system environment, or the LiveCycle.ear file may not be deployed. This error is internal and should not occur. the correct host and port information, and then continue on to database initialization. Verify that the LiveCycle product deployed properly and is available to initialize the database. Using Administrator, restart the LiveCycle.ear file. If the problem is not resolved, restart the application server.

5 Configuration Manager Error Messages 5 LCMerror3004 LCMerror3005 LCMerror3006 LCMerror3007 LCMerror3008 LCMerror3009 Could not connect to bootstrap application: Bootstrapping application not found on server; deployment of bootstrap application may not have been successful. product(s) could not be Could not connect to bootstrap application: Port may be invalid. Bootstrapping request failed on server: {0} bootstrapper is invalid. Could not establish a valid connection to server. Port may not be SSL enabled or certificates may not be trusted. Error during SSL communication with server. Could not establish a valid connection to server. The database initialization failed because the LCMBootstrapper.war file was not deployed Incorrect port information was entered during configuration. Database initialization failed due to the incorrect host information. Bootstrapping failed because the Configuration Manager attempted to bootstrap an unknown component. Invalid port or certificate information was entered during the configuration. SSL keystore and password information may be incorrect, or the SSL port may not be available. Invalid port information was entered during configuration, or the server is down. 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 utilities and log files. the correct port information (application server computer port that hosts the LiveCycle product), and then continue on to database initialization. This error is internal and should not occur. the correct information, and then continue on to database initialization. the correct port and certificate information (application server computer port that hosts the LiveCycle product), and then continue on to database initialization. the correct SSL information, and then continue on to database initialization. Ensure that the server is running, run the Configuration Manager again, and enter the correct port information, and then continue on to database initialization.

6 Configuration Manager Error Messages 6 Turnkey messages LCMerror9001 LCMerror9003 LCMerror9004 Turnkey service {0} does not exist. Failed to stop turnkey service {0}. Failed to stop turnkey service {0}. Ports are still active. LCMerror9005 Failed to start turnkey {0}. Ports already in use. LCMerror9007 LCMerror9010 Failed to start turnkey service {0}. Failed to deploy {0} to turnkey JBoss. Service does not exist. The installer may have failed to create the service or it was removed. Service may not be responding to the stop command. Service could not be stopped because the required ports are still in use. Service may not be responding to the start command. Either the JBoss ports (8080, 8083, 1099, 1098, 4444, 4445, 8009, 1162, 8090, 8092, 8093)) or the MySQL service port (3306) are in use. 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/deploy directory. Check the Microsoft Windows service for the status of the service. Reinstall the LiveCycle product using the turnkey or manual process. Verify the status of the service using the Windows service and then stop the service manually. Verify the status of the service using the Windows service and then stop the service manually. Verify the status of the service using the Windows service and then start the service manually. Verify that no other JBoss services are running or another application that may use the same port. If it is a problem with the source files, If it is a problem with the target files, there may be an issue with disk LCMerror9020 LCMerror9021 JBoss default web application not ready and accessible. Failed to start up or timed out. LCMBootstrapper web application not ready and accessible. Failed to start up or timed out. JBoss service may have failed, or the time out has expired. LCMBootstrapper.war deployment may have failed. Check the JBoss log file, sever.log, in the Jboss root/server/all/log/ directory for details. 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 USA 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.