Failed to connect to account using personal access token '<omitted>' provided, check url and token.

[Prateek1584990]

Hi Team,

When we are trying to import the process .json into Azure Devops Server 2019 , we are getting below error from the process migrator tool.

Failed to connect to account https://FQDN/tfs/Collection Name using personal access token '' provided, check url and token.

Request your help in fixing this issue.

[jkocsis3]

Seeing the same issue as well with Azure Devops Sever 2019. Token is less than a day old, has full access to all collections. Using SSL and hitting https://<Azure url>/<colectionName> as the sourceAccountUrl.

[eduardobbs]

I am getting this error when trying to export from a local TFS instance (Version Dev17.M153.3).

[xg578962913]

I also encountered such a problem. Is there any way to solve it

[liang2zhu1]

Happened to look at a different issue and noticed node.js ADO client appears not working for collection-scoped token on boxed product, try with a token with access to 'all organizations'

[Roberto8004]

Tuve el mismo problema. El mismo se me dio por tener Azure Devops 2019 on premise con certificado autofirmado. Para que el script node funcione hay que agregar la variable de entorno NODE_TLS_REJECT_UNAUTHORIZED=0

[AminTi]

Our team is dedicated to providing continuous support for this extension. To ensure efficient issue resolution, we will close any old or inactive issues. If you come across any new problems, please create a ticket, and we will promptly address and resolve them. Thank you for your cooperation and understanding.