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 Page and Activity Log tab for information. If those do not give enough information for you to identify the problem, check the details in the alm.log file.
Verify that the connection requirements are met
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 Manager projects, such as Release Packages and Deployment Tasks.
If the deployment task fails with the error: Project was not found
If your deployment of a Dimensions CM or DVM deployment task fails with an error similar to the following, make sure that you specified the VAULT parameters in all upper case in the provider file, such as dm_qlarius.properties.
"Deployment of unit VAULT:V_QA_BASE1 to area(s) V_PRE-PROD_AREA has failed : Project was not found"
"Promotion of deployment unit VAULT:V_QA_BASE1 to stage PRE-PROD has failed : Project was not found."
This also causes a message similar to the following to be generated in the log file:
10-23@04:29:03 DEBUG [DimClientException.java:28] [max] : DimClientException happened : Project was not found.
10-23@04:29:03 ERROR [RLMUtilServiceSkeleton.java:519] [max] : Error: Deployment of unit VAULT:V_QA_BASE1 to area(s) V_PRE-PROD_AREA has failed : Project was not found.
Check for an SbmDeployUnitHelper error message
If you receive an error in the product log file similar to the following:
Error
java.lang.NullPointerException: null at java.util.StringTokenizer.(Unknown Source) ~[na:1.6.0_12] at java.util.StringTokenizer. Unknown Source) ~[na:1.6.0_12] at com.serena.alm.sbm.client.internal.util.hlp. SbmDeployUnitHelper.getRelatedByIds (SbmDeployUnitHelper.java:175)
check the rlm-sbm.properties related deployment unit ID table value to ensure it is entered exactly as follows.
deployment.extfield.relatedDeployUnitId=RELATED_DEPLOY_UNITS
The value should be plural, not singular. If you have upgraded from a pre-release version of Serena Release Manager 2.1 and did not replace the rlm-sbm.properties file with the latest version, you could encounter this issue.
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.