Contents

Test Connection fails for Sample Data for Oracle if user expiration error received

When running the Development Control installer with either the Dimensions CM or SBM sample data selected for Oracle, the test connection fails if the password is due to expire within 7 days.

You will need to make sure that the Oracle user will not receive this expired password warning in order to complete the installation.

An error Should be Displayed if Attempting to Install SBM Sample Data for remote MSSQL

When running the Development Control installer and choosing to install the sample data for SBM using a remote MSSQL database, the installer allows the process to continue. This option is not actually supported, and the installation should not complete successfully.

You will need to run the installer on the machine where MSSQL is installed, selecting the option to install the SBM sample data using the Custom install option.

Upgrade from DVM 1.1 to DVM 1.2 not Updating the Version of DVM

If you have run the installer for DVM 1.2 on an existing version of DVM 1.1, and the installed version is still 1.1, it is likely that the installer has not completed because of a failure in installing/upgrading the QC connector, causing it to roll back the installation.

In this case the solution is to:

1. Uninstall the QC connector 2.
2. Rerun the DVM 1.2 installer with the QC connector option included.

This will successfully update the installation.

Create Dev CR Button not Appearing After Upgrade

There is a problem where, after upgrading to DVM 1.2 from a previous version, the Create Dev CR button does not appear on the Change Requests tab for an ALM project. This can be remedied by using the following steps:

1. Open SBM Composer.
2. Deploy the Dev Change Requests process app.
3. Deploy the ALM Projects process app.

Error Promoting Dev Change Requests Snapshot

On promoting the Dev Change Requests snapshot after upgrading to DVM 1.2 from a previous version, the promotion may fail with the following error appearing in the log file:

Import: Incoming project already exists at this level. Name: 'Dev Change Requests Project',

Existing UUID: '60b85e4d-b11a-47c8-9f2c-66674945a733

The solution is to select None for Projects on the Entities page of the Promote wizard.

Promoting Snapshots Fails after Upgrade to DVM 1.2

When performing an upgrade to Development Manager 1.2, promoting snapshots may fail with an error in the log file such as:

ERROR -- Cannot deploy BPEL definition for process model alf/9c629f6d-0686-41d5-a41a-1c079ba973fa/ - 500: could not execute query. ORA-00923:

FROM keyword not found where expected. Failed to complete the deployment to server "Default BPEL Server" at 4/23/12 12:18 PM.

The following steps should resolve the problem:

If you are using SBM 10.1:

1. Open SBM Configurator.
2. Restart the Serena Common JBOSS service.

   • Make sure that the file:

     C:\Program Files\Serena\SBM\Common\jboss405\server\default\log\sbm_oe_health.log

     Does not contain any errors

3. If there are errors found, stop and restart Serena Common JBOSS.
4. Promote the snapshots.

If you are using SBM 10.1.1.1:

1. Open SBM Configurator.
2. Restart the Serena Common JBOSS service.
3. Select Diagnostics.
4. Click the Diagnostic Tests button.
5. Select Orchestration engine complex health test.
6. Click the Run Selected Tests button.
7. If there are errors found from either of the above, stop and restart Serena Common JBOSS.
8. Promote the snapshots.

Installation Interrupted Error on Upgrade if Already Installed Component is Deselected

If upgrading an installation and deselecting an option that was previously installed, the installer fails.

You will need to run the installer without deselecting a component that is already installed.

Please Contact Your Administrator Message Appears on Forms

If you experience a problem where the message Please Contact Your Administrator keeps appearing on various forms, it is likely that a report that is being used in an embedded report widget is missing. This will cause the error to appear, and not cleared for a period of time, thus appearing on other pages. The solution is to make sure all reports exist and that the widgets are properly calling them.

To check that the reports are set up correctly:

1. In the user environment view an item (almproj,devcr,devpack,tasks,ram,etc)
2. View each tab that has an embedded report.
• If you see the report showing data, or even it you just see the columns and there is no data, then that report is setup correctly
• if the report is not there and it says something like “this report may be deleted”, “you do not have permissions to see this report”, or any other error message, then the report has not been set up correctly.

For details of how to create a missing report with the correct reference name, see the corresponding section in the Troubleshooting section in Chapter 3 of the Development Manger Installation and Configuration Guide.

QC Integration not Working on 64-bit Machine

If on a 64-bit installation, having created a Dev CR of type Defect, and having submitted it to Approve, there is no value in the Quality CR field, and there is an error in SBM Composer : "Access is denied." It is likely that you need to carry out the post-installation steps described in the Serena Development Manager Connector for HP Quality Center / ALM Implementation Guide.

See Post-Installation Steps for 64-bit QC Connector in Chapter 2 of this guide.

Privilege Error when Transitioning a Defect Dev Change Request

If you receive an error saying that the user does not have the privilege to view the auxiliary table, you will need to grant the view privilege to the Quality Connector auxiliary table to any users that need to perform the necessary transitions (e.g. Josh the development manager, Alexander the build engineer).

1. In SBM Application Administrator, Select Users.
2. Select the user.
3. Select Privileges.
4. Select Table.
5. Under Tables, select Quality Connector.
6. Under Grant Privileges, select View.
7. Click the Save button.

Build of Baselines Fails in Dimensions CM for CM Sample Data

When attempting to perform a build for a baseline using the sample database (dvm_demo) for Dimensions CM for a baseline using the default build areas, the build fails with the message:

To overcome this problem:

1. In the Dimensions Administration Console select Build Admiinistration, select the project/stream
2. Check out the build configuration
3. Select the build area and click the Edit button.
4. Click the Edit button in the Change Build Area Selection dialog box.
5. Set the change the user to dmsys, and the password to the dmsys password.
6. Save the changes and check in the build configuration.

For more details, see Updating the Default Build Areas in Chapter 3 of the Development Manger Installation and Configuration Guide.

Admin User Does not have Group Privileges for SBM Sample Data for SBM 10.1

Is this still true???

When using SBM 10.1, the Admin user for the SBM sample database does not have access to any groups in the Web Administrator. The solution to this is to create a user with Remote Administration privileges, and use this user to grant the privileges for the groups for the Admin user.

1. Open SBM System Administrator and Select the Users tab.
2. Add a new User as a Managed Administrator.
3. On the Privileges tab, make sure Remote Administration is selected.
4. Save the details and log out.
5. Log in as the user you created.
6. On the Users tab, select the Amin user and select Edit.
7. Select Administration and select Groups.
8. Select all the groups and click OK.

Actioning a Task in Dimensions CM to Complete Does not Transition the Task in SBM to Complete.

When actioning a task request from Peer Review to Complete in Dimensions CM, and delegating the Development Engineer role (for example to user Amy) the corresponding task in SBM is not transitioned to Complete in SBM. To remedy this, the transition in the TASK lifecycle in Dimensions CM needs to have DEVELOPMENT ENGINEER assigned as a Pending role.

1. In the Dimensions Administration Console, under Configuration Object Management, select Lifecycles.
2. Edit the lifecycle LC_TASK.
3. Edit the transition between PEER REVIEW and COMPLETE.
4. Select DEVELOPMENT ENGINEER, and select the Pending check box.
5. Select the the transition between COMPLETE and CLOSED.
6. Click the Edit button on the Transitions tab.
7. Select DEVELOPMENT ENGINEER and select the Pending check box.

For more details, see Troubleshooting in Chapter 3 of the Development Manger Installation and Configuration Guide.

Error When Deploying Process Apps

If you receive an error in SBM Composer when deploying a process app:

It is likely that the process app contains references to another process app that needs to be deployed before it.

The process apps need to be deployed in the order below:

1. Global Process App (eval)
2. Dev Change Requests
3. ALM Projects
4. Dev Tasks
5. Dev Packages
6. Dev Control Orchestrations
7. Quality Center Connector
8. Requirement Approval Management

Error Promoting Global Process Apps when Upgrading an Existing DVM Installation

If you are upgrading a previous installation of DVM, you may receive an error in SBM Application Administrator when promoting the Global Process App (eval) process app.

This problem can be overcome by setting the following values on the Global Entities page of the Promote Wizard.

• Groups: None
• Users: None

Groups and Users unassigned from projects when Upgrading an Existing DVM Installation

When upgrading an existing installation of DVM, you may find that some groups and users are unassigned from projects after promoting snapshots.

This problem can be overcome by setting the following values on the Global Entities page of the Promote Wizard

• Groups: None
• Users: None

User Groups Missing for Sample Database on MSSQL

If you are using MSSQL, the user groups are not present for the sample data. In this case you will need to assign the necessary roles for the users to enable them to use the applications using SBM Administrator. For details, see "Creating and Assigning the Users" in the Development Manager Installation and Configuration Guide.

New Endpoints Created After Deploying Process Apps

When you have redeployed the process apps, for example after updating the application links in the Event Mappings as described in the post-installation steps, you may find that duplicate endpoints have been created, such as:

dmwebservices_2

DevManagerServices_2

This results in an error in SBM Composer such as:

The Orchestration Engine cannot send the Web service request at service step CM_Create_Standard_Baseline to the endpoint ...

The solution is to use SBM Application Administrator to perform the deployments.

1. Open each process app in SBM Composer.
2. Click the Publish button in the toolbar.
3. In the Publish Process App dialog box, select Allow others to deploy this version of the process app and click Publish.
4. Open SBM Application Administrator (enter http://localhost:8085/mashupmgr/ in a browser).
5. Select Process Apps on the left.
6. Select a process app and click the Deploy button.
7. Click in the Destination field.
8. Select the environment and click Next.
9. Check that the list of endpoints is correct.
10. Click Done and complete the deployment.
11. Repeat Step 6 thru Step 10 for the other process apps.

The DVM User Interface is not Being Displayed

The User Interface for Development Manager should have a blue and grey color scheme. If when accessing the DVM Application, the standard SBM interface is displayed, it is probably the result of not applying the steps described in "Importing the Files for the Development Manager UI" in Chapter 3 of the Development Manger Installation and Configuration Guide. This must be done immediately after running the installation.

If the correct user interface is not being displayed, follow the steps described in the Troubleshooting section in Chapter 3 of the Development Manger Installation and Configuration Guide.

There is an Access Denied failure when Attempting to Create an Item

If a process is attempting to create an item, and there is an error, for example "[ERROR] Access Denied," in the log, and the item is not created, then it is likely that you do not have access privileges for the connector user.

1. Carry out the following steps:
2. Open the SBM System Administrator.
3. Select users.
4. Select the connector user (for example DMSYS) and click Edit.
5. Select the Administration tab.
6. Select Global Administration and click OK.

The REST Grids are not Returning Values

Check whether:

1. The DVM web services is running.
2. You have configured the DVM web services correctly.
3. If SSO is enabled, ensure that the user you are using in SBM also exists in Dimensions CM.

TASK requests are not Being created in CM When Creating Dev Tasks

1. Deploy the Dev Control Orchestrations process app.
2. Restart the server.

If this does not work, check whether you are using the connector account (for example dmsys). You should not be using the connector account to create items in SBM, it is reserved for connecting only.

A Baseline Cannot be Created from a Dev Package

If when trying to create a baseline from a dev package, no baseline gets created in Dimensions CM, and the following appears in the Windows Event Viewer:

you can resolve the event viewer error by unlocking the event definition. Do the following:

1. In SBM Composer open the Dev Packages application.
2. Show Extensions.
3. Expand Orchestration Links.
4. Click on Event without Reply.
5. Check the item out.
6. Ensure that Lock definition (on the right-hand side) is not checked.
7. Check in the item and re-deploy.

The Dev Control Orchestrations Process Application Doesn't Handle Events from the Dev Tasks Process Application

You need to recreate ChangeTaskworkflowEventDefinition:

1. In SBM Composer, Open the Dev Tasks process application.
2. Under Orchestration Links, select Event without Reply.
3. Uncheck Lock definition.
4. Click Export to file… , type the file name and export the Orchestration link to a file.
5. Click Yes to automatically lock the definition
6. Check in the item and re-deploy.

The Dev Control Orchestrations Process Application Doesn't Handle Events from the ALM Projects Process Application

In this case, you need to recreate DevelopmentControlChangeRequestWorkflowEventDefinition.

1. In SBM Composer, open the ALM Projects process application.
2. Perform the same steps 2 to 6 as above.

For further details, see the Troubleshooting section in Chapter 3 of the Development Manger Installation and Configuration Guide.

The Dev Control Orchestrations Process Application Doesn't Handle Events from the Dev Package Process Application

You need to recreate DVMBaselineEventDefinition.

1. In SBM Composer, open the ALM Projects process application.
2. Perform the same steps 2 to 6 as above.

For further details, see the Troubleshooting section in Chapter 3 of the Development Manger Installation and Configuration Guide.

QC Integration Installation window is Minimized

When running the 64-bit installer with QC integration selected, the installation window is minimized.

Progress Bar not Displayed when Installing the Dimensions CM Sample Data

When running the Development Control installer with the Dimensions CM sample data option selected, the status bar on the Installing page does not display the progress.

SBM Sample Data Installer Page for MSSQL does not support use of DSN names

When running the Development Control installer to install the sample data for SBM, the DSN name is not validated correctly.

Credentials on "Connection details" page for MSSQL not verified correctly

When installing the CM sample data for MSSQL, it is possible to connect without a password to the database, even in the case when the user is configured with a password. You can only specify details for the "pcms_sys" admin user for MSSQL, other existing users are not allowed.

Installer Allowing invalid credentials for SBM Sample Data on Oracle

When installing the SBM sample data for Oracle, the user is able to enter an invalid Admin password and continue with the installation.