Specific Errors

This section presents a list of specific errors you may see, with possible causes.

Area <area name> is in use

Attempt to close invalid connection

Failed to authenticate to the build agent

Failed to find product-specific upload rules

No build areas found for the selected configuration

Template pbem_stop.cmd open failed

You do not have a role to extract item

Area <area name> is in use

The full error message is:

Area <area_name> is in use and you cannot update <property> at this time

If you see this error message, it means that you are trying to edit a build area that has already been associated with a checked in build configuration. Once a build configuration with an attached build area has been checked in, you can no longer modify the following build area properties:

- Area ID

- Stage ID

- Network node

- Directory

Attempt to close invalid connection

If your build does not execute, and if you see this message in the Tomcat window, it may mean that Tomcat has timed out your connection. In this case, restart Tomcat from the Start menu.

Failed to authenticate to the build agent

If your build displays this error message, it may mean that the you have entered an incorrect password for the user ID under which Dimensions CM logs in.

It could also mean that the build agent is not installed or not running on the build machine.

Failed to find product-specific upload rules

If your build runs but displays this error message, it may mean that your Dimensions administrator has not yet defined a default item library. Dimensions CM cannot upload the build target to Dimensions as a new item unless it can locate a default item library.

No build areas found for the selected configuration

If you see this error in the Run Build wizard, it could mean that you are trying to use the Build Scheduling tab to execute a never-before-executed version of a build configuration.

If a version of a build configuration has been checked in but has never been run, it does not contain a build area association. A version of a build must be run at least once before you can execute it from the Build Scheduling tab.

If you see this error when trying to execute the build from the Build Management tab, it means that the build configuration has no build areas attached.

Template pbem_stop.cmd open failed

If your build job displays this error message, it may mean that the temp directory defined in the Dimensions configuration file contains a space.

Edit <DM_ROOT>/dm.cfg and change the value of DM_TMP to a path that does not contain spaces.

You do not have a role to extract item

If your build job displays this error message, it may mean that the Dimensions user you have logged in as does not have a role that allows updating the build target. More specifically, the Dimensions user may lack a role on the first transition of the item. For example, an .exe file using the default LC_EXECUTABLE lifecycle transitions from BUILT to TESTED. If the Dimensions user does not have a role on that transition, the check-in of the build target may fail.

Use the Dimensions Administration Console to check the appropriate roles and transitions, or contact your Dimensions administrator.