Troubleshooting the Deployment Path

"Please contact your administrator" warning (for missing deployment log report)

If "Please contact your administrator" appears at the top of the page when creating or editing a release package or when editing deployment units or deployment tasks, the following report may be missing:

• Deployment Log for Release Packages

You can confirm this by searching for this report in Report Center under All Reports. If the report is missing, you can either re-promote the snapshot with Merge Conflicts selected or create the report yourself. See Creating the Deployment Log Report Manually.

The pop up for viewing deployment units hangs in the loading state

If the pop up for viewing deployment units hangs in the loading state, the following report may be missing.

• RLC DU Execution Log for Deployment Path

You'll see the following error in the network log:

/tmtrack/tmtrack.dll?sid=zmgmuxih&StdPage&Template=error&ParamsInUserCache= ...

You can confirm this by searching for this report in Report Center under All Reports. If the report is missing, you can either re-promote the snapshot with Merge Conflicts selected or create the report yourself. See Creating the DU Execution Log Report Manually.

Deployment path information is missing or incomplete

If the deployment path history doesn't appear below the deployment path or after you have deployed to an environment, the deployment units aren't shown when you click the eye icon, there are issues with the configuration.

If the information is missing, do the following:

• Ensure that you have followed the promotion instructions exactly as documented for the Release Package process app snapshot. In particular, ensure you clicked Apply in SBM Configurator before promoting the Release Package snapshot the first time and generated the view in a command prompt before promoting the Release Package the second time. Refer to Promoting the Snapshots.
• Ensure that you have the proper privileges to access the Deployment Log and DU Execution Log tables. See Creating Groups and Assigning Roles and Privileges.
• If the wrong database is connected, the promotion of the Release Package will fail with an error about the Deployment Log for Release Packages report. To resolve this, on the SBM Application Engine server, open SBM System Administrator and verify the database connection. Ensure that the database you are promoting to is connected. Close SBM System Administrator once you verify that the correct database is connected, and then try promoting the Release Package snapshot again.
• If you did all of the above and the reports are still missing, you can create the reports yourself. See Creating the Deployment Log Report Manually and Creating the DU Execution Log Report Manually.

Creating the Deployment Log Report Manually

If you still do not see the report, create the report as follows:

1. Create a listing report using the following settings:
   • Content, Report Item Type: RLC Deployment Log
   • Content, Select Columns to Display:
     • Start Time
     • End Time
     • Execution Type
     • Execution Status
     • Path Element ID
     • Environment ID
     • QA Result
     • QA Result Time
     • Parent TC ID
     • Source TC Execution ID
   • Search Filter, Use Basic Conditions: Deployment Task ID contains (Query At Runtime)
   • Sorting, Sort by: Start Time, Ascending
2. Save the report as follows:
   • Title: RLC Deployment Log for Release Package
   • Privilege Category: Guest
   • Reference Name: RLC.DeploymentLogByTCID

Creating the DU Execution Log Report Manually

If you still do not see the report, create the report as follows:

1. Open Release Control in the standard SBM shell.
2. Create a listing report using the following settings:
   • Content, Report Item Type: RLC DU Execution Log
   • Content, Select Columns to Display:
     • Deployment Unit
     • Configuration Type
     • Release Package
     • Task
     • Task Execution Status
     • Start Time
     • End Time
   • Search Filter, Use Basic Conditions:
     • Task Collection Execution ID like (Query At Runtime)
     • Environment TTID like (Query At Runtime)
   • Sorting: Select Enable Dynamic Column Sorting
3. Save the report as follows:
   • Title: RLC DU Execution Log for Deployment Path
   • Privilege Category: Guest
   • Reference Name: DusForDpExecution

Required Privileges

If you are receiving privilege errors or want to double-check privileges for a user or group, following are the required privileges:

For Deployment Log Functionality

• TS_USRPRJPRIV_VIEWALLITEMS (Project - View All Items) for "Environments Projects"
• TS_USRPRJPRIV_VIEWALLITEMS (Project - View All Items) for "Environment Schedule Project"
• TS_USRPRJPRIV_VIEWALLITEMS (Project - View All Items) for "Path Elements Project"
• TS_USRPRJPRIV_VIEWALLITEMS (Project - View All Items) for "Deployment Path Project"
• TS_USRTBLPRIV_VIEW (Table - View) for "RLC Deployment Log" auxiliary table
• TS_USRTBLPRIV_EXECUSERRPT (Table - Run Guest-Level Reports) for "RLC Deployment Log" auxiliary table

For Deployment Unit Execution Log Functionality

• TS_USRTBLPRIV_VIEW (Table - View) for "RLC DU Execution Log" auxiliary table
• TS_USRTBLPRIV_EXECUSERRPT (Table - Run Guest-Level Reports) for "RLC DU Execution Log" auxiliary table