Release Package Deployment Fails

If deployment of a release package fails, here are some possible solutions.

A deployment vault task fails when you deploy a release package

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

Check for an SbmDeployUnitHelper error message

If you receive an error in the product log file similar to the following:


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.rlm.sbm.client.internal.util.hlp.SbmDeployUnitHelper.getRelatedByIds(

check the related deployment unit ID table value to ensure it is entered exactly as follows.


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 file with the latest version, you could encounter this issue.

An automation deployment task fails when you deploy a release package

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:

Related Topics