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

Troubleshooting ADM Error Messages

This topic provides troubleshooting tips and information about issues that may occur while using the Application Deployment Manager (ADM) feature.

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.

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.

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.

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

Make sure that the server name in entprofile.xml matches the server name in agentconfig.xml. The servers in the list of deployment servers must also match the agents under <enterprise_target_information> in entprofile.xml. Values are case-sensitive.

Backup Command Hangs

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

• The package location is specified in deploy.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.

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 server components are running.

Copy Command Error: Validation Fails

If the validation fails, make sure that the agent name under <targetserverdetails> in entprofile.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.xml. Values are case-sensitive.

Copy Command Hangs

If nothing happens after you run the copy command, make sure that SRBroker and SRProc system management server components 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.

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 srvrmgr path is present in startagent.bat.

   For Windows, the srvrmgr is generally in $Siebel_Root$\bin for the release version and in $Siebel_Root$\bin\w32ud for the debug version.

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

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

   set ADM_ENTERPRISE= <enterprise_name>

3. Change the Siebel Enterprise Server name in the Header File of entprofile.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.xml. For example:

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

5. Change the Siebel Enterprise Server name for the agent in configuration.agent.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.

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 in order to export the project when data becomes available. Thus, setting deployment filters that return zero records is not prohibited.

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

Cannot Add More Than One 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. Release 8.0 supports a multipartitioned FileSystem, 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.