We migrated a collection that uses the Team Calendar extension (v 2.0.17) from one server to another, upgrading from Azure DevOps Server 2020 (Dev18.M170.8) to Azure DevOps Server 2022 (AzureDevOpsServer_20221122.1) in the process. After the migration everything is working (so far) on the new server except for the Team Calendar exception. When adding an event the user prompted for credentials to the server to which the user is already authenticated. Supplying the username and password does not get the user past this authentication screen (see attached screenshot).
In the browser's network capture we can see this...
{
"message": "TF400813: The user is not authorized to access this resource. ",
"type": "Microsoft.TeamFoundation.Framework.Server.InvalidIdentityException",
"isRemoteException": false,
"errorCode": 0,
"eventId": 3000
}
What we tried:
We made the user an administrator on the new Azure DevOps server to see if it was a permission issue. This had no effect.
We brought the collection online on the old server to see if the calendar was trying to reach the old server for some reason. This had no effect.
Hello.
We migrated a collection that uses the Team Calendar extension (v 2.0.17) from one server to another, upgrading from Azure DevOps Server 2020 (Dev18.M170.8) to Azure DevOps Server 2022 (AzureDevOpsServer_20221122.1) in the process. After the migration everything is working (so far) on the new server except for the Team Calendar exception. When adding an event the user prompted for credentials to the server to which the user is already authenticated. Supplying the username and password does not get the user past this authentication screen (see attached screenshot).
In the browser's network capture we can see this...
{ "message": "TF400813: The user is not authorized to access this resource. ", "type": "Microsoft.TeamFoundation.Framework.Server.InvalidIdentityException", "isRemoteException": false, "errorCode": 0, "eventId": 3000 }
What we tried:
We made the user an administrator on the new Azure DevOps server to see if it was a permission issue. This had no effect.
We brought the collection online on the old server to see if the calendar was trying to reach the old server for some reason. This had no effect.
Thanks in advance for your help!