Invalid Operation Exception (new install) #2404
Closed
chrisburger90
announced in
Exceptions
Replies: 1 comment
-
This seems to not occur if I run the command and explicitly referencing the exe in the packages folder as well as the configuration.json in the same folder. Previously I was using the symlink for the exe and the full folder path for the config which was in a different folder. I'll do some more tests to see if anything might be worth noting but this is no longer an issue. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm trying to run a test migration of work items between two organizations. I've setup the tool using the winget method on my win11 machine and have configured a basic config file. When I try and run the tool I get the following exception:
[18:30:41 FTL] [16.0.3] Error while running TfsWorkItemMigrationProcessor
System.InvalidOperationException: No service for type 'MigrationTools.Endpoints.IEndpoint' has been registered.
at Microsoft.Extensions.DependencyInjection.ServiceProvider.GetRequiredKeyedService(Type serviceType, Object serviceKey, ServiceProviderEngineScope serviceProviderEngineScope)
at Microsoft.Extensions.DependencyInjection.ServiceProviderKeyedServiceExtensions.GetRequiredKeyedService[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 68
at MigrationTools.Processors.Infrastructure.Processor.get_Source() 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_Source() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Processors\Infra\TfsProcessor.cs:line 22
at MigrationTools.Tools.TfsNodeStructureTool.EntryForProcessorType(TfsProcessor processor) in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Tools\TfsNodeStructureTool.cs:line 300
at MigrationTools.Tools.TfsNodeStructureTool.ProcessorExecutionBegin(TfsProcessor processor) in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Tools\TfsNodeStructureTool.cs:line 277
at MigrationTools.Processors.TfsWorkItemMigrationProcessor.InternalExecute() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Processors\TfsWorkItemMigrationProcessor.cs:line 103
at MigrationTools.Processors.Infrastructure.Processor.Execute() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools\Processors\Infrastructure\Processor.cs:line 98
[18:30:41 INF] [16.0.3] TfsWorkItemMigrationProcessor completed in 00:00:00
[18:30:41 ERR] [16.0.3] TfsWorkItemMigrationProcessor The Processor MigrationEngine entered the failed state...stopping run
[18:30:41 INF] [16.0.3] Command ExecuteMigrationCommand completed in 00:00:05.4281848
configuration.json
Are there dependencies missing on my machine or has something not worked with the installation? I've attached the configuration json file if that helps.
Beta Was this translation helpful? Give feedback.
All reactions