rh._.exports({"0":[[" ","Specific Errors"]],"1":[[" ","Specific \n Errors"," ","This section presents a list of specific \n errors you may see, with possible causes."," ","Area \n <area name> is in use"," ","Attempt \n to close invalid connection"," ","Failed to authenticate \n to the build agent"," ","Failed \n to find product-specific upload rules"," ","No build \n areas found for the selected configuration"," ","Template \n pbem_stop.cmd open failed"," ","You \n do not have a role to extract item"," ","Area <area name> is \n in use"," ","The full error message is:"," ","Area <area_name> is in use and you \n cannot update <property> at this time"," ","If you see this error message, it means \n that you are trying to edit a build area that has already been associated \n with a checked in build configuration. Once a build configuration with \n an attached build area has been checked in, you can no longer modify the \n following build area properties:"," ","Area ID"," ","Stage ID"," ","Network node"," ","Directory"," ","Attempt to close invalid connection"," ","If your build does not execute, and \n if you see this message in the Tomcat window, it may mean that Tomcat \n has timed out your connection. In this case, restart Tomcat from the Start \n menu."," ","Failed to authenticate to the build \n agent"," ","If your build displays this error message, \n it may mean that the you have entered an incorrect password for the user \n ID under which ","Dimensions CM"," \n logs in."," ","It could also mean that the build agent \n is not installed or not running on the build machine."," ","Failed to find product-specific \n upload rules"," ","If your build runs but displays this \n error message, it may mean that your Dimensions administrator has not \n yet defined a default item library. ","Dimensions CM"," cannot \n upload the build target to Dimensions as a new item unless it can locate \n a default item library."," ","No build areas found for the \n selected configuration"," ","If you see this error in the Run Build \n wizard, it could mean that you are trying to use the Build Scheduling \n tab to execute a never-before-executed version of a build configuration."," ","If a version of a build configuration \n has been checked in but has never been run, it does not contain a build \n area association. A version of a build must be run at least once before \n you can execute it from the Build Scheduling tab."," ","If you see this error when trying to \n execute the build from the Build Management tab, it means that the build \n configuration has no build areas attached."," ","Template pbem_stop.cmd open \n failed"," ","If your build job displays this error \n message, it may mean that the temp directory defined in the Dimensions \n configuration file contains a space."," ","Edit <DM_ROOT>/","dm.cfg"," \n and change the value of DM_TMP to a path that does not contain spaces."," ","You do not have a role to \n extract item"," ","If your build job displays this error \n message, it may mean that the Dimensions user you have logged in as does \n not have a role that allows updating the build target. More specifically, \n the Dimensions user may lack a role on the first transition of the item. \n For example, an .exe file using the default LC_EXECUTABLE lifecycle transitions \n from BUILT to TESTED. If the Dimensions user does not have a role on that \n transition, the check-in of the build target may fail."," ","Use the Dimensions Administration Console \n to check the appropriate roles and transitions, or contact your Dimensions \n administrator."]],"id":"439"})