Access Control Data Migration Tool Troubleshooting (v9.0.0 and v9.2.0)

Owned by Former user (Deleted)
Last updated: Jan 11, 2021 by Johannes Stark (Unlicensed)
2 min read

This chapter provides troubleshooting information for typical errors that may be encountered when running the Access Control Migration Tool installer.

For any error encountered while running the Access Control Migration Tool installer (whether in the Access Control installation phase or the data migration phase), an error notification will be displayed.

Only upon completion of the Access Control Migration Tool installer without any error notification (you'll receive a confirmation message) will you then be able to continue to the next phase (manual validation of migrated data), after which you can then run the CxSAST / CxOSA upgrade installation. 

Access Control Installation Errors

In case of an error found during the Access Control installation, the installer will not proceed to the data migration stage. In this case contact Checkmarx support.

After resolution, rerun the Access Control Migration Tool installer. If no further errors are found in the Access Control installation stage, the data migration stage will then run automatically.

Data Migration Errors

In case of an error found during the data migration stage:

  1. Rectify the problem / discrepancy in the CxSAST CxDB.
  2. In the installer, click the Rerun Data Migration button to perform the data migration again.
  3. Alternatively, you can exit and restart the installer, which will also confirm the Access Control installation was successful, before rerunning the migration again.

Data Migration Error Notifications and Potential Fixes

The following is a list of typical errors encountered and their potential fixes in the data migration phase:

Error found:

In the step Checking Access Control API Connection, the following error displays:

Failed to make an API call to Access Control. Verify that Access Control is up and running and rerun the migration.

Potential fix: Disable the Windows proxy configuration, and rerun the data migration tool.

Potential fix: Manually change the CxAccessControl account to have the same domain user as the remaining 8.x application pools.


Error found:

Error is due to an invalid character ( \ ) in the team name:

2018-11-07 07:59:29.999 [ERR] Failed to migrate team Team\C (Id: 88080c54-c92d-45a6-9fcb-ee60d9a7ceff). HTTP response status code: 400, content: {"Message":"Invalid character in team name."}

Potential fix:

The backslash (\) and colon (:) are not supported characters for a team name. In the SAST CxDB, change team name Team\C  to  Team-C for example, and rerun the data migration tool.


Errors found:

A problematic team GUID appears in the users-teams mapping table.

2018-11-07 08:06:44.985 [Fatal] [ACMigrationTool.Infrastructure.SAST.SASTUsersRepository] Failed to read SAST users-teams connections from the database

2018-11-07 08:06:44.986 [Fatal] [ACMigrationTool.MigrationRunner] Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).

Potential fix:

  1. Find the problematic GUID in the users-team mapping table in the SAST CxDB
  2. Remove the problematic entry.
  3. Log into CxSAST and assign a team to the specific user.
  4. Rerun the data migration tool.

.


Read More