Error while running repository synchronization job

[DK_13918167]

Hello PTC community,

We were performing the Codebeamer and Azure DevOps integration using the "New External Repository".

After doing the configuration when we clicked on the Validation it got validated and we were able to create the new external repository. 

Everything went well.

But after trying to "Scm repository update synchronization" we are facing the "Error while running repository synchronization job, For: Azure-repository".

We are using the Codebeamer version 2.2.0.2 but i have not found any article in the knowledge base addressing this issue. 

[pshashipreetham]

Hey, 

1. Recheck the PAT (Personal Access Token)

   • In Azure DevOps, go to User Settings → Personal Access Tokens.

   • Create a new token with at least the following scopes:

     • Code → Read

     • Project and Team → Read

   • Update this token in Codebeamer under the External Repository configuration and revalidate.

2. Verify Repository URL Format

   • The repository URL should look like:
     https://dev.azure.com/<organization>/<project>/_git/<repository>

   • Avoid trailing slashes or cloned URLs with SSH format — Codebeamer only supports HTTPS URLs.

3. Check Branch Configuration

   • Ensure that the default branch specified in Codebeamer actually exists in the Azure repo.

   • If it’s blank, specify the primary or master branch manually.

4. Network and Proxy Validation

   • Make sure the Codebeamer server can be reached dev.azure.com through HTTPS.

   • If your organisation uses a proxy, whitelist this domain.

5. Run Manual Synchronisation Test

   • In Codebeamer, go to the repository integration page and click “Validate.”

   • Then run “SCM Repository Update Synchronization” again.

   • If it still fails, check the system logs (cb.log or scm.log) on the Codebeamer server for more specific messages like 401 Unauthorized or Connection Refused.

If Still Not Working

• Restart the SCM synchronisation job service in Codebeamer.

• Try deleting and recreating the external repository configuration after saving the working PAT.

• As of Codebeamer version 22.2.0.2, there’s no specific patch for this issue, but newer versions (like 22.3.x and above) handle Azure repository jobs more reliably — consider upgrading if the integration remains unstable.

Recreate the Azure PAT with correct permissions, check the repository URL, confirm the branch, and revalidate the connection. 90% of the time, this error is caused by either expired tokens or mismatches in URL formatting.

Thanks,