Skip to main content

Common Azure DevOps Integration Errors

  • Updated

This article lists and describes common errors that may occur with the Azure DevOps integrations.

VSTS Connection: Error at (2-6) Response status code does not indicate success: 401 (Unauthorized). at System.Net.Http.HttpResponseMessage.En ureSuccessStatusCode() at ProjectConnect.Connectors.VSTS.TfsClient. estConnection() in D:\a\1\s\ProjectConnect.Connectors.VSTS\ fsClient.cs:line 103

This error indicates that the Azure DevOps Personal Access Token expired or is revoked.

Please make sure that you are using an access token that is valid.

For more information, please see Use personal access tokens from Microsoft.

TF50316

Azure DevOps has several naming conventions. This error indicates that those naming conventions are violated.

For more information, please see Naming restrictions and conventions from Microsoft.

VS403074

The Work Item Type does not exist in the Inherited Process template.

For more information, please see Add and manage work item types from Microsoft.

Error: TF401326: Invalid field status 'InvalidType' for field 'Microsoft.VSTS.Common.{Field Name}'.

The value used in OnePlan does not match the available values in Azure DevOps.

OnePlan should either have the value updated, or there needs to be Value Mapping configured in OneConnect. (to map between the list of values in OnePlan and the list of values in Azure DevOps).

TF51011: The specified iteration path does not exist. The error is caused by «'{Iteration Path Value}'».

The iteration path in Azure DevOps no longer exists, or it is in the middle of the iteration path list (I.E., Path Two was chosen within: Path One/Path Two/Path Three).

Related articles

Comments

0 comments

Article is closed for comments.