PAT Token Error after pointing to Source and Target?

[soodgautam]

I cleaned up my config file and pointed source and target to the right place in my TFSworkitemmigration processor but I'm still getting the same PAT token error.

Error while running TfsWorkItemMigrationProcessor
System.InvalidOperationException: An error occurred while retrieving the endpoint 'Target'. ---> System.InvalidOperationException: Validation failed for endpoint 'Target': The AccessToken must not be null or empty when AuthenticationMode is set to 'AccessToken'.
at MigrationTools.EndpointRegistrationExtensions.<>c__DisplayClass1_0.b__0(IServiceProvider sp, Object key) in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools\Endpoints\Infrastructure\EndpointRegistrationExtensions.cs:line 61
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitFactory(FactoryCallSite factoryCallSite, RuntimeResolverContext context)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument) at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache(ServiceCallSite callSite, RuntimeResolverContext context) at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.Resolve(ServiceCallSite callSite, ServiceProviderEngineScope scope)
at Microsoft.Extensions.DependencyInjection.ServiceProvider.CreateServiceAccessor(ServiceIdentifier serviceIdentifier)
at System.Collections.Concurrent.ConcurrentDictionary2.GetOrAdd(TKey key, Func2 valueFactory)
at Microsoft.Extensions.DependencyInjection.ServiceProvider.GetService(ServiceIdentifier serviceIdentifier, ServiceProviderEngineScope serviceProviderEngineScope)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.GetKeyedService(Type serviceType, Object serviceKey)
at Microsoft.Extensions.DependencyInjection.ServiceProviderKeyedServiceExtensions.GetKeyedService[T](IServiceProvider provider, Object serviceKey)
at MigrationTools.Processors.Infrastructure.Processor.GetEndpoint(String name) in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools\Processors\Infrastructure\Processor.cs:line 69
--- End of inner exception stack trace ---
at MigrationTools.Processors.Infrastructure.Processor.GetEndpoint(String name) in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools\Processors\Infrastructure\Processor.cs:line 79
at MigrationTools.Processors.Infrastructure.Processor.get_Target() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools\Processors\Infrastructure\Processor.cs:line 43
at MigrationTools.Processors.Infrastructure.TfsProcessor.get_Target() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Processors\Infra\TfsProcessor.cs:line 24
at MigrationTools.Processors.TfsWorkItemMigrationProcessor.get_Target() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Processors\TfsWorkItemMigrationProcessor.cs:line 76
at MigrationTools.Processors.TfsWorkItemMigrationProcessor.ValidatePatTokenRequirement() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Processors\TfsWorkItemMigrationProcessor.cs:line 323
at MigrationTools.Processors.TfsWorkItemMigrationProcessor.InternalExecute() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Processors\TfsWorkItemMigrationProcessor.cs:line 101
at MigrationTools.Processors.Infrastructure.Processor.Execute() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools\Processors\Infrastructure\Processor.cs:line 105

configuration.json

[MrHinsh]

Thats not the format for an AzureDevOpsEndpoint thats the format for the TfsTeamProjectEndpoint. If you are trying to run a TfsWorkItemMigrationProcessor then you need the TfsTeamProjectEndpoint.

However when I run your config above I get: Unable to cast object of type 'MigrationTools.Endpoints.AzureDevOpsEndpoint' to type 'MigrationTools.Clients.TfsTeamProjectEndpoint', which is the correct error as you have the wrong endpoint type specified.

Did you run this config?

In your config you should have TfsTeamProjectEndpoint fo both Source and Target.

You should take a look at the Getting Started page!

[soodgautam]

I'm running this exact config file and still getting the same PAT error.

configuration.json

[MrHinsh]

Every time you send the config its diferent, and changes in the oposit way I sugested!

This latest config is going to get an 'AccessToken' missing as the token is not in the right place. Please look at Getting Started and pay atention to the Endpoint type, and the location of the token.

Last time you had the "typename" of "AzureDevOpsEndpoint" and the body of "TfsTeamProjectEndpoint"... this time you have the typename of "TfsTeamProjectEndpoint" and the body of "AzureDevOpsEndpoint".

For TfsWorkItemMigrationProcessor to function, as per Getting Started you need to have the TfsTeamProjectEndpoint endpoint with the body of the TfsTeamProjectEndpoint.

[soodgautam]

I apologize Mr.Hinsh and I really appreciate you take the time to help me. I went back through the documentation and changed the name and body of my endpoint to match TfsTeamProjectEndpoint however I'm still getting the same PAT error. I copied it twice for source and target. I've attached the proper config file below. Also just a sidenote but I'm using the same PAT for both source and target as both projects exist within the same org. I do this for testing and it worked on v15. Just thought I should include this for extra context
configuration.json

[MrHinsh]

Both your endpoints are invalid. But I see the problem... the sample on TfsTeamProjectEndpoint is not rendering correctly, same for all the endpoints. However it is correct in Getting Started.

You have:

{
  "MigrationTools": {
    "Version": "16.0.2",
    "Endpoints": {
      "Target": {
        "TfsTeamProjectEndpoint": {
          "Collection": "",
          "Project": "target-migration"
          ...
        }}
      }
  }
}

This is not what is shown on Getting Started and you should have:

{
  "MigrationTools": {
    "Version": "16.0.2",
    "Endpoints": {
      "Target": {
          "EndpointType": "TfsTeamProjectEndpoint",
          "Collection": "",
          "Project": "target-migration"
          ...
        }
      }
  }
}

So your config never ends up with any endpoints...

Ill look at how TfsTeamProjectEndpoint is rendered... and try to figure a way to validate this...