Bookshelf Home | Contents | Index | PDF |
Siebel Application Deployment Manager Guide > Siebel ADM Logging Capabilities and Troubleshooting > Troubleshooting Siebel ADM Error MessagesThis topic provides troubleshooting tips and information about issues that can occur while you are using Siebel Application Deployment Manager (ADM). The error messages are listed alphabetically. ADM Packager (Admpkgr) Error: Definition of Data Type Not FoundIf the ADM Packager reports an error stating that the definition of a particular data type was not found, check the structure of the package. Also check the adm_registry.xml file to determine if the data type in question is supported by ADM. ADM Packager (Admpkgr) Is Not Functioning CorrectlyIf the ADM Packager is not functioning correctly, make sure that:
Backup Command HangsIf nothing happens after you run the
Cannot Add More Than One Siebel File System for Each Siebel Enterprise ServerIn a multiserver deployment, set FileSystem only at the enterprise level, and point it to the same location. Siebel Business Applications support a multipartitioned Siebel File System, but there must still be only one enterprise-shared value for FileSystem. CAUTION: If FileSystem is not set correctly, the deployment of ADM data types that use EAI as the deployment method might fail. Cannot Execute Workflow Process DefinitionThe following error appears in the ADM log file: Cannot execute workflow process definition 'ADM Deployment'.(SBL-BPR-00158) This error occurs when the ADM workflows are not activated before running deployment. Activate the ADM workflows from the application-level menu. Navigate to the Application Deployment Manager screen, then the Data Type Details view. In the Data Types list, click Menu, and then click Activate ADM Workflows. Redeploy. Cannot Run Two Management Servers on the Same MachineMultiple Management Servers cannot be run from the same machine at the same time. You can install multiple Management Servers on the same machine, but only one can run at a given time. This limitation exists due to a conflict in port numbers. The Management Server, Tomcat server, and ADM local database occupy certain ports on the machine. If you have two instances running, then these ports conflict. You can configure Management Server and Tomcat server to listen on different ports, but the database port cannot be changed. Copy Command Error: Multiple Matches for Integration Component User KeyIf you receive the error message: Multiple matches found for instance of integration component '<x>' using search specification '<x>' in the business component '<x>', based on user key '<x>'. (SBL-EAI-04390) Clean the duplicate records in the target environment before executing the deployment. Copy Command Error: Server Not OnlineIf you receive an error that the server is not online, make sure the servers in the list of deployment servers are online. Also make sure that ADMProc and ADMObjMgr_lang server components are running. Copy Command Error: Validation FailsIf the validation fails, make sure that the agent name under Copy Command HangsIf nothing happens after you run the Copy Fails Due to a FileSystem ErrorIf the copy fails and the log files for this package deployment (ADMProc*.log) in the Siebel Server log directory indicate a filesystem error, make sure the filesystem path exists and has read and write access from the server. Create Command Error: Server Name Not in Deploy Server List or Enterprise ProfileIf you receive the error message: The specified server is specified in the target server but not in the deploy server list or <EnterpriseTargetServerInformation>. Make sure that the server name in entprofile_enterprise_name.xml matches the server name in agentconfig.xml. The servers in the list of deployment servers must also match the agents under Create Command Error: Session Already Exists for the Current PackageIf you receive an error message stating that a session already exists for the current package after you run a Deployment Filter Can Return Zero Records While Exporting Database Data Types to Deployment UnitsIn situations where matching data is not present, the administrator might be creating filters to export the project when data becomes available. Thus, setting deployment filters that return zero records is not prohibited. Enterprise Name ErrorIf you receive the following error message in the ManagementServer.log or Agent.log the Siebel Enterprise Server name was not set properly in the Management Server: ManagementServer SEVERE 2006-10-03 03:27:03 Cannot create MBean [Siebel:name=ServerAdmin] of class [com.siebel.management.serveraccess.ServerAdmin](SBL-CMS-00201) You must change the Siebel Enterprise Server name in Management Server and Management Agent. To change the enterprise name in Management Server and Management Agent
Function Errors Occur After Successful DeploymentIf the deployment completes without errors (status is java.lang.IllegalStateException: AlertManager Already StartedThe following error appears in the ManagementServer.log file: MgmtServer INFO 2007-09-19 14:20:40 creating server connection to agent [ name=<name> Although this appears to be an error, this situation is acceptable as long as there is a final online message. Note this line that occurs in the message: url=service:jmx:rmi://<name>/jndi/rmi://<name>:1199/jmx/siebel/agent state=online java.lang.NullPointerExceptionWhen running deploy_enterprise_name.bat from the MgmtSrvrInstallDir directory, a Java exception error occurs right away: java.lang.NullPointerException The file adm.cli is missing from the MgmtSrvrInstallDir directory. Get a copy of the adm.cli file from another ADM environment. Update the file with the correct target host machine name. Run the deploy command again. java.net.BindException: Address Already In Use: JVM_BindYou can not bring up Management Server service. The following error shows in the service_out.log file: Aug 31, 2007 2:44:04 PM org.apache.catalina.core.StandardServer await This error occurs when the port number of Tomcat server (8005) is being used by an existing service. To fix this, you need to change the shutdown port from 8005 to another port number (such as 8006). This port number is specified in the <Server port="8006" shutdown="SHUTDOWN"> SBL_CLI_00001 Exception Caught During ProcessingWhen deploying, this error occurs: The command failed: SBL_CLI_00001 Exception caught during processing: Unable to connect to the Management Server. Verify that the Management Server is running. The following entries are in the ManagementServer.log: MgmtServer INFO 2007-08-31 14:44:03 trying to connect 1 agents This error occurs when the Management Server service or Management Agent service is not running. Restart the Siebel Management Agent service first. Wait until it is fully running. Then restart the Siebel Management Server. Check the ManagementServer.log file to make sure the Management Server can connect to the Management Agent. Then redeploy. Step RunSecurityBat: Failed to Run Program CmdDuring the Management Agent configuration step, or when configuring the Management Server the following error appears: Step RunSecurityBat: failed to run program cmd with cmdline /V:ON /C %%AgentHomeDir%%%%OSDirSeparator%%security The error means security.bat file cannot be executed successfully. This issue can only be reproduced on some machines. The behavior is not consistent. Make sure your machine meets ADM system requirements. See Siebel System Requirements and Supported Platforms on Oracle Technology Network. Go to Windows Control Panel, then Services. Manually start the Management Agent or Management Server service. The Following Server(s) <Server Name> Are Specified in Target EnterpriseWhen running the Warning - The following server(s) '<Server Name>' are specified in target enterprise, but they are not listed in enterprise profile's server information section. Failure - The following server(s) '<Server Name>' are used in deployment, but they are not in the enterprise profile's server information section.(SBL-DMJ-00298) Validation failed, total failure number is '1'. The target host name is not configured correctly in entprofile_enterprise_name.xml file. Check the entprofile_enterprise_name.xml file and make sure the host name is correct. Remove the _1199 from the Make sure the agent name in agentconfig.xml and configuration.agents.xml matches the server name listed in entprofile_enterprise_name.xml. The entries are case-sensitive, so make sure they match exactly. Restart Management Server, Management Agent, and the Siebel Server. |
Siebel Application Deployment Manager Guide | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |