Troubleshooting

This topic provides information about troubleshooting Deployment Automation.

For more help with troubleshooting, see the Knowledge Base and the Community website.

Conflict with WebDAV in IIS

If you are running Deployment Automation under JBOSS and IIS, make sure that WebDAV is removed from IIS on the server that hosts Deployment Automation.

WebDAV prevents Deployment Automation from using critical web service DELETE and PUT operations. For example, you cannot apply a license in Deployment Automation.

To remove WebDAV:

Select the website in IIS.
Edit the Handler Mappings and remove WebDAV.
Navigate back to the website Home page.
Edit the Modules and remove the WebDAVModule.

Installation failure due to interruption

Your installation may fail due to system interruption the first time you attempt to install.

In this case, the installation runs very quickly, and the Install Wizard Completed dialog box displays a message similar to the following:

The installation wizard was interrupted before Deployment Automation could be completely installed.
Your system has not been modified. To complete installation at another time, please run setup again.

To complete the failed installation:

Run the installer again to remove the installation.
Run the installer again to install.

This time, the installation may take longer to copy the files. You receive a message with installation details in the Install Wizard Completed dialog box.

Import failure, or issues after import

Generally, export files are backward compatible, but you may encounter an issue when importing export files from earlier versions of Deployment Automation.

This table includes examples of the errors and ways to resolve them.

Error type	Resolution
You receive an error when you try to import environments that were exported from a prior version of Deployment Automation.	Upgrade the primary Deployment Automation server and export the objects again. You can then import them into a target server of the same version.
You cannot import an application from a json file because it was exported while using a different plugin version than the one you have. For example, you receive an error similar to "Plugin DA Versioned File Storage Version 20 does not exist."	You can use the resolution in the earlier entry. Or you can edit the exported application json file and try to import again. Open the json file in a text editor and change all occurrences of pluginName and pluginVersion to the name and version of the plugin you have loaded. In this example, you could change pluginName to DA Versioned File Storage and pluginVersion to 20.
Your import seems to work, but when you try to deploy, you receive a generic run error. This means the structure of the application may have been imported incorrectly. For example, you can deploy at the component level but not the application level. There is a structure mismatch in the imported files.	Typically, you can fix this issue by removing and readding the component to the application.

Error type

Resolution

You receive an error when you try to import environments that were exported from a prior version of Deployment Automation.

Upgrade the primary Deployment Automation server and export the objects again. You can then import them into a target server of the same version.

You cannot import an application from a json file because it was exported while using a different plugin version than the one you have.

For example, you receive an error similar to "Plugin DA Versioned File Storage Version 20 does not exist."

You can use the resolution in the earlier entry.

Or you can edit the exported application json file and try to import again. Open the json file in a text editor and change all occurrences of pluginName and pluginVersion to the name and version of the plugin you have loaded.

In this example, you could change pluginName to DA Versioned File Storage and pluginVersion to 20.

Your import seems to work, but when you try to deploy, you receive a generic run error. This means the structure of the application may have been imported incorrectly.

For example, you can deploy at the component level but not the application level. There is a structure mismatch in the imported files.

Typically, you can fix this issue by removing and readding the component to the application.

SSO login failure after Tomcat upgrade

If you have configured Single Sign-On (SSO) with one version of Common Tomcat and have upgraded Deployment Automation to a version that uses a different version, you must configure Common Tomcat for SSO again, including setting the parameters in the gatekeeper-core-config.xml file. Otherwise, the SSO login fails.

To set these parameters, copy over the corresponding strings from earlier version of the gatekeeper-core-config.xml file. Copying and replacing the entire file from the earlier Common Tomcat installation doesn't work.

For instructions on setting up SSO, see Configure Common Tomcat for SBM SSO.

Process failures or false successes

This table describes some common reasons for process failures and false successes.

Issue	Resolution
The process runs quickly and the status is Success, but the process didn't run and the output log says that the component already exists in that environment.	To run the process in that environment regardless of whether the component already exists, clear the Only Changed Version option when you run the process.
The process runs as a global process but when you try to run it as a component process, it fails.	You may not have mapped resources for the component within the application environment. This is required for component processes. See Map application components to resources.
When using a plugin, the status of the process doesn't show the same status as that in the integrating product.	Click the Refresh button to see the latest status. In some cases, additional action may be necessary. See the documentation for your specific plugin.

Navigation tips

You may find the following tips helpful as you navigate the user interface.

Navigation point	Resolution
When you are in the process designer, you click other options, but the process designer is still displayed.	Before you can continue navigation to other options, click the x at the top right next to the other controls to close the process designer. For details, see Create and design component processes.
When you select View Details for an application environment, the page doesn't open.	If the click is released too slowly, the page sometimes doesn't open. If a quick single-click doesn't work, try double-clicking. See Application environments.
You clicked a link after you ran a process request, and now can't get back to the page that displays the process results.	For information on viewing process request information, see View an application process request and View a component process request.
You can't find the option to map a component to a resource.	You map components to resources for each application environment to which the component is to be deployed. For details, see Map application components to resources.
You can't find the option to map an agent to an environment.	You map agents to environments at the global level in the environment Resources tab. For details, see Map agents to environments.
You can't find the page that displays the environments graphically so that you can configure them.	The environments are shown graphically in the application they are associated with. For details, see Add environments to applications.
You can't find a way to promote or rerun a process in an environment that is part of a pipeline.	If your pipeline is configured for auto promote and a process fails in one of the environments, you must run the process again for the pipeline, starting with the first environment. For details, see Run deployment processes.
You can't find the replication import and export options.	Select any Administration page, for example, System. Expand the Action list at the top right to view the Replication options. For details, see Replication. Note: The replication options are not available from the drop-down selection on the left side of the page.