Troubleshooting dependency data scanning

Edit online

You can troubleshoot known problems that might occur when you use the source control data scanner.

No permission to refresh and select streams for scanning

This problem occurs when you try to refresh and select streams for data scanning, but you do not have the permissions that are required to perform this action. Ask your system administrator to give you the appropriate permissions by modifying your user settings this way:

  1. In the Team Artifacts view, right-click your project area and select Open. The Project Area editor opens.
  2. In the Project Area editor, select the Process Configuration tab, expand the Project Configuration node, then click Permissions.
  3. In the Permissions section, select the user role you want to modify. Under the Source Code Data node in the Permitted actions section, make sure that all of the boxes are selected.

Stream is not selected for scanning during a dependency build

This problem occurs when you try to scan a stream that is not enabled for scanning.

The source code data collection service does not automatically scan all streams to collect source code data. It only scan the streams you want to scan. By default, no streams are selected for scanning. To enable a stream for source code data scanning, perform the following steps:

Before Version 6.0.1:
  1. From the Team Artifacts view in the Eclipse client, expand the Enterprise Extensions node, right-click Source Code Data, and select Select Streams for Scanning. The Source Code Data Scanning editor opens.
  2. In the editor, select which project and team area streams you want to scan for source code data.
  3. Click Finish.
From Version 6.0.1:
  1. From the Team Artifacts view in the Eclipse client, expand the Enterprise Extensions node and select Source Code Data > Open Scan Configurations.
  2. In the Scan Configurations editor that opens, select the stream for the scan.
  3. If that stream has not been set up for dependency scanning, the Create button appears. Click it and the Scan Configurations dialog opens. You can leave all the default settings.
  4. Click Save.
  5. Close the Scan Configurations dialog.

Stream is locked for scanning

This problem occurs when you select a stream to scan for source code data, but the scan will not run. Several scenarios can cause a stream to lock out scanning, including the following:
  • If you run a dependency build and, while the build is running, you request the reset of the source code data of the stream.
  • If you shut down your server before a dependency build completes.
  • If you shut down your server before your source code data reset completes.
  • Anytime you shut down your server while the scan is already preprocessing.
To solve this problem, restart your server, verify that the build failed, and then reset the scanning lock. To do this, perform the following steps:
  1. From the Team Artifacts view in the Eclipse client, expand the Enterprise Extensions node and select Source Code Data > Open Scan Configurations.
  2. In the Scan Configurations dialog that opens, select the stream for the scan.
  3. Click the Request Scan (Request Scan icon) icon in the toolbar.
  4. On the Select scan type page of the Request Scan wizard, clear Scan changed files only.
  5. Click Finish.

Run your build again, and the scan should run successfully.

Source code data scanning fails

This problem occurs when a scanner fails to scan a file, and the entire scan process fails. In the case of a dependency build, the build also fails. To solve this problem, follow these steps:
  1. Open the scan configuration from the Team Artifacts view. Expand the Enterprise Extensions node, then select Source Code Data > Open Scan Configurations.
  2. In the Scan Configurations dialog that opens, select the stream for the scan that failed.
  3. Select the Continue on error option.
  4. Click the Request Scan (Request Scan icon) icon in the toolbar.
  5. Run your scan again, and the scan should run successfully.
  6. Open the Engineering Workflow Management Administration Console.
  7. Log in to the Administration Console with administrator privileges.
  8. In the left navigation frame, expand Configuration and select Advanced Properties,
  9. Scroll down the alphabetized list of properties to the Source Code Data Collection properties.
  10. Set the Continue Source Code Data Scanning On Error property to true.

Run your build again, and the scan should run successfully.

Dependency builds will not build correctly if the source code data is deleted

If you delete source code data by entering -delete as the scan argument in the Scan Configuration field of the selected stream, dependency builds for the selected streams will build incorrectly. If you delete the source code data for a stream, it will remain deleted until the source code data is rescanned or the files have been modified. A dependency build will only update the source code data for any files that have changed since the last scan.
To ensure that dependency builds run correctly, rescan the stream by completing the following steps:
  1. From the Enterprise Extensions node, right-click Source Code Data and select Open Scan Configurations.
  2. In the Scan Configurations editor that opens, select the streams that you want to scan.
  3. Click the Request Scan (Request Scan icon) icon in the toolbar.
  4. On the Select scan type page of the Request Scan wizard, clear Scan changed files only.
  5. Click Finish.
Note: You must have Jazz administrator permissions to complete these steps.