Siebel Application Deployment Manager Guide > Siebel ADM Logging Capabilities and Troubleshooting >

Troubleshooting Siebel ADM Error Messages


This 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 Found

If 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 Correctly

If the ADM Packager is not functioning correctly, make sure that:

  • The package location given in the command has read and write permission for the user.
  • The package name in the command is spelled correctly and uses the appropriate capitalization. The package name is case-sensitive.
  • No previous descriptor files exist in the package location. Delete old descriptor files before creating new ones.

Backup Command Hangs

If nothing happens after you run the backup command, make sure that:

  • The package location is specified in deploy_enterprise_name.bat.
  • The package location has read and write permissions.
  • The package is present and the descriptor file matches the package.
  • Re-create the descriptor file and try again.

Cannot Add More Than One Siebel File System for Each Siebel Enterprise Server

In 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 Definition

The 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 Machine

Multiple 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 Key

If 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 Online

If 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 Fails

If the validation fails, make sure that the agent name under <EnterpriseTargetServerInformation> in entprofile_enterprise_name.xml matches the deployment server for file, database, and repository categories. Also make sure that the agent name in agentconfig.xml matches the agent details in entprofile_enterprise_name.xml. Values are case-sensitive.

Copy Command Hangs

If nothing happens after you run the copy command, make sure that the SRBroker and SRProc server components for system management are online and that ADMJavaSubsys profile is configured properly. Locate the log files for this package deployment (ADMProc*.log) in the Siebel Server log directory and check for error messages.

Copy Fails Due to a FileSystem Error

If 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 Profile

If 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 <EnterpriseTargetServerInformation> in entprofile_enterprise_name.xml. Values are case-sensitive.

Create Command Error: Session Already Exists for the Current Package

If you receive an error message stating that a session already exists for the current package after you run a create command, then you must first acknowledge the previous session, then run the create command again.

Deployment Filter Can Return Zero Records While Exporting Database Data Types to Deployment Units

In 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 Error

If 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)
java.lang.IllegalArgumentException: (SBL-CMS-00953) Name server name is null or empty.

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

  1. Make sure the Server Manager (srvrmgr) path is present in startagent.bat.

    For Windows, Server Manager is located in SIEBSRV_ROOT\bin.

    If the Server Manager path is not present, add it to startagent.bat.

  2. Change the Siebel Enterprise Server name in deploy_enterprise_name.bat by entering the following command:

    set ADM_ENTERPRISE= enterprise_name

  3. Change the Siebel Enterprise Server name in the Header File of entprofile_enterprise_name.xml.

    For example:

    Description="This profile is used to describe the target enterprise related parameters." EnterpriseName=":<enterprise_name>"

  4. Change the Siebel Enterprise Server name in the <EnterpriseTargetServerInformation> section of entprofile_enterprise_name.xml.

    For example:

    <EnterpriseTargetServerInformation>
    <ServerInfo AgentName="sdchs20i059" SiebelServerConnectString="siebel://sdchs20i059:2321/:enterprise_name/ADMObjMgr_enu" ServerInstallDir="d:\sba81\sbl1202\"/>
    </EnterpriseTargetServerInformation>

    NOTE:  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 <EnterpriseTargetServerInformation> in entprofile_enterprise_name.xml. Values are case-sensitive.

  5. Change the Siebel Enterprise Server name for the agent in configuration.agents.xml.

    For example:

    <entry key="sdchs20i059" value="sdchs20i059:SiebelServer::enterprise_name:service:jmx:rmi://sdchs20i059/jndi/rmi://sdchs20i059:1299/jmx/siebel/agent"/>

  6. Change the Siebel Enterprise Server name for the entry key in configuration.globals.xml.

    For example:

    <entry key="<enterprise_name>.management.serveraccess.nameServer" value="string:sdchs20i059:2320"/>

  7. Restart the Management Server and Management Agent for the changes to take effect.

Function Errors Occur After Successful Deployment

If the deployment completes without errors (status is DEPLOYMENT_COMPLETE), but the users report some function errors, and it is not clear whether these are part of the changes made by the developers or whether the deployment has not completed as required, redeploy the package and verify the deployment to determine whether or not the data in the package is correctly applied to the target environment. For more information on verifying an ADM deployment, see Verifying a Siebel ADM Deployment.

java.lang.IllegalStateException: AlertManager Already Started

The following error appears in the ManagementServer.log file:

MgmtServer INFO 2007-09-19 14:20:40 creating server connection to agent [ name=<name>
url=service:jmx:rmi://<name>/jndi/rmi:///<name>:1199/jmx/siebel/agent state=offline ]
MgmtServer INFO 2007-09-19 14:20:40 agent=[ name=<name>
url=service:jmx:rmi://<name>/jndi/rmi://<name>:1199/jmx/siebel/agent state=offline ]
MgmtServer INFO 2007-09-19 14:20:41 new connection to [ name=<name>
url=service:jmx:rmi://<name>/jndi/rmi://<name>:1199/jmx/siebel/agent state=online ]
MgmtServer SEVERE 2007-09-19 14:20:41 caught exception
java.lang.IllegalStateException: AlertManager already started
at com.siebel.management.alerts.AlertManager.getPrivilegedAction(AlertManager.java:142)
at com.siebel.management.general.configuration.ServerConfigMgr.getPrivilegedInitActions(ServerConfigMgr.java:1146)
at com.siebel.management.agents.AbstractServerAgent.start(AbstractServerAgent.java:69)
at com.siebel.management.agents.MgmtServerAgent.init(MgmtServerAgent.java:41)
at com.siebel.management.agents.MgmtServerService.init(MgmtServerService.java:31)
at javax.servlet.GenericServlet.init(GenericServlet.java:211)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)

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.NullPointerException

When running deploy_enterprise_name.bat from the MgmtSrvrInstallDir directory, a Java exception error occurs right away:

java.lang.NullPointerException
at
com.siebel.client.management.cli.CLIUtil.loadFromCLIFile(CLIUtil.java:296)
at
com.siebel.client.management.cli.CLIUtil.processCommand(CLIUtil.java:238)
at com.siebel.client.management.cli.CLIUtil.main(CLIUtil.java:59)

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_Bind

You 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
SEVERE: StandardServer.await: create[8005]:
java.net.BindException: Address already in use: JVM_Bind

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 MgmtSrvrInstallDir\tomcat\conf\server.xml file.

<Server port="8006" shutdown="SHUTDOWN">

SBL_CLI_00001 Exception Caught During Processing

When 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
MgmtServer INFO 2007-08-31 14:44:03 submitting task=com.siebel.management.general.communication.ConnectTask@15c40eb to 1 agents
MgmtServer INFO 2007-08-31 14:44:03 creating server connection to agent [ name=<name>
url=service:jmx:rmi://<name>/jndi/rmi://<name>:1199/jmx/siebel/agent state=offline ]
MgmtServer INFO 2007-08-31 14:44:03 agent=[ name=<name>
url=service:jmx:rmi:///<name>/jndi/rmi://<name>:1199/jmx/siebel/agent state=offline ]
MgmtServer INFO 2007-08-31 14:44:03 non-connection related exception while executing task
com.siebel.management.general.communication.AgentNotFoundException: Agent not online or name is invalid: <name>(SBL-CMS-00104)

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 Cmd

During 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 Enterprise

When running the valent command, the following error message appears:

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 <EnterpriseTargetServerInformation> section.

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.