PAT Token Error follow up? #2367
Unanswered
soodgautam
asked this question in
Q&A
Replies: 1 comment 1 reply
-
Your upgraded config looks good, but you are missing the
These values default to |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I saw someone else run into the same PAT token issue as me. I'm trying to migrate from one ADO project to another. I've done multiple migrations on v15 and not run into any PAT token issues. Once I upgraded to v16 and reconfigured my config file I started running into the PAT token issues. I've tried running the tool with just TFS team project endpoints and it gives me the same PAT token error and I've also tried running the tool with TFS and Azure Devops endpoints and I'm getting the same error. I've attached the error code and my config file with TFS endpoints and my config file with TFS and Azure Devops endpoints below. I've put in dummy characters for my PAT Token so you can see where I'm putting it in. Please help me understand what I'm doing wrong because I've gone through all the docs and tried a hundred different fixes for this issue. Thanks in advance!
configuration.json
configuration-upgraded.json
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.CallSiteVisitor
2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument) at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache(ServiceCallSite callSite, RuntimeResolverContext context) at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor
2.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.ConcurrentDictionary
2.GetOrAdd(TKey key, Func
2 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
[09:48:50 INF] [16.0.2] TfsWorkItemMigrationProcessor completed in 00:00:00
[09:48:50 ERR] [16.0.2] TfsWorkItemMigrationProcessor The Processor MigrationEngine entered the failed state...stopping run
[09:48:50 INF] [16.0.2] Command ExecuteMigrationCommand completed in 00:00:03.5729539
Beta Was this translation helpful? Give feedback.
All reactions