If deployment of a release package fails, here are some possible solutions.
Before you try deployment tasks in Serena Release Manager, make sure that the same type of task works in native Dimensions CM.
If you are sure the task works in native Dimensions CM, check the Activity Log tab for information. If that does not give enough information for you to identify the problem, check the details in the rlm.log file.
A common source of the problem is the user ID setup. Make sure that all of the requirements are met as follows:
The same user ID and password must be used in both SBM and Dimensions CM.
SSO must be enabled for both SBM and Dimensions CM on the same SSO server.
The user ID must be given a role in the Serena Release Control projects, such as Release Packages and Deployment Tasks.
If an automation deployment task fails when you promote a release package, test the server process in native Serena Release Automation.
If the process works in native Serena Release Automation but not in Serena Release Manager, here are some other things to try:
Verify that the Serena Release Automation service is running properly.
Close the Deployment Task dialog box and reopen it.
Clear the Web browser cache and retry.