Common Azure DevOps Integration Errors

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 the Personal Access token is still 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).

Undefined: Specified Work Type Name ({Type Name}) does not exist

Example: Undefined: Specified Work Type Name (Feature) does not exist

The work type name in the error message, is missing from the "Item Type" work plan level choice field in OnePlan.

Open the OnePlan configuration, go to the fields, find the Item Type field and add the missing choice.

Item not processed because {Work Item Type name here} is not specified in OneConnect config

Example: Item not processed because My Special Epic is not specified in OneConnect config

When OneConnect is trying to add an item to Azure DevOps the work item type is missing. This can happen if there is a mapping for plan level items and the plan type that is being used is not in Azure DevOps. 

To solve this issue, either rename the plan type to match Azure DevOps, or add the missing work item type to Azure DevOps.

VS403691: Update to work item -1 had two or more updates for field with reference name 'System.AreaPath'. A field cannot be updated more than once in the same update.

The integration has more than one value going to the Area Path (or Area ID) field at the plan level. If connecting an item to Azure DevOps via the Connected Systems window within OnePlan, the area path value will be mapped and sent over automatically when an event is triggered from OnePlan. If a user also has a field mapping to the Area Path or Area ID at the plan level, the integration will try to send two sets of data to the Azure DevOps Area Path field, and this error will be sent to the logs.

The [Team Projects Areas] field is not mapped. Please map the field. Refer to the online help for instructions

When running the OnePlanPublish strategy, the FilterPlansByIntegration function may fail with the following error:

“The [Team Projects Areas] field is not mapped. Please map the field. Refer to the online help for instructions.”

This occurs because when syncing data from OnePlan to Azure DevOps during a scheduled strategy run, Azure DevOps requires the Area ID field. In this integration, the OnePlan field is hardcoded to reference the Team Projects Areas field at the Plan level. This field must be mapped in the Plans – Epics table within the integration’s field mappings.

Please follow the instructions below to enable this functionality. 

If you want to publish data from OnePlan to Azure DevOps, please make sure that you have a mapping for the "Team Projects Areas" OnePlan field. (see below the mapping details)

If you don't have a field called "Team Projects Areas" in OnePlan, then create a plan level Choice field and name it exactly "Team Projects Areas".

Once you have the plan level field in OnePlan, map it in OneConnect on the plan level in your Azure DevOps integration.