Beginning run of 0 processors

[amalavarghese]

I am trying to migrate my entire devops project from one organisation to another. For which iam trying to use azure devops migration tool for migrating workitems (along with history, comments, attachments, etc.) and pipelines. But when executed the configuration.json file it shows no processor are run.

[17:56:58 INF] [16.0.3] The Max log levels above show where to go look for extra info. e.g. Even if you set the log level to Verbose you will only see that info in the Log File, however everything up to Debug will be in the Console.
**[17:56:58 INF] [16.0.3] Beginning run of 0 processors**
[17:56:58 INF] [16.0.3] Command ExecuteMigrationCommand completed in 00:00:04.3702645

configuration.json file:

{
  "CommonTools": {},
  "MigrationTools": {
    "Version": "16.0",
    "Endpoints": {
      "Source": {
        "EndpointType": "TfsTeamProjectEndpoint",
        "Collection": "https://dev.azure.com/**/**",
        "Project": "**",
        "Authentication": {
          "AuthenticationMode": "AccessToken",
          "AccessToken": "**"
        },
        "ReflectedWorkItemIdField": "Custom.ReflectedWorkItemId"
      },
      "Target": {
        "EndpointType": "TfsTeamProjectEndpoint",
        "Collection": "https://dev.azure.com/**/**",
        "Project": "**",
        "Authentication": {
          "AuthenticationMode": "AccessToken",
          "AccessToken": "**"
        },
        "ReflectedWorkItemIdField": "Custom.ReflectedWorkItemId"
      }
    }
  },
  "Processors": [
    {
      "ProcessorType": "TfsWorkItemMigrationProcessor",
      "Enabled": true,
      "UpdateCreatedDate": true,
      "UpdateCreatedBy": true,
      "FixHtmlAttachmentLinks": true,
      "WorkItemCreateRetryLimit": 5,
      "FilterWorkItemsThatAlreadyExistInTarget": true,
      "PauseAfterEachWorkItem": false,
      "AttachRevisionHistory": false,
      "GenerateMigrationComment": true,
      "WorkItemIDs": null,
      "MaxGracefulFailures": 0,
      "SkipRevisionWithInvalidIterationPath": false,
      "SkipRevisionWithInvalidAreaPath": false,
      "Enrichers": null,
      "SourceName": "Source",
      "TargetName": "Target",
      "RefName": null
    },
    {
      "ProcessorType": "AzureDevOpsPipelineProcessor",
      "BuildPipelines": null,
      "Enabled": true,
      "MigrateBuildPipelines": true,
      "MigrateReleasePipelines": true,
      "MigrateServiceConnections": false,
      "MigrateTaskGroups": false,
      "MigrateVariableGroups": false,
      "ReleasePipelines": null,
      "SourceName": "Source",
      "TargetName": "Target",
      "RepositoryNameMaps": {
        "InsurityMigration": "test-repo"
      }
    }
  ],
  "Serilog": {
    "MinimumLevel": "Verbose"
  }
}

[MrHinsh]

Please provide the entire log file!

[amalavarghese]

log file attached
migration.log

[MrHinsh]

What config are you passing? ProcessorContainer: Of 0 configured Processors only 0 are enabled looks like there are no processors...

[MrHinsh]

Solution: Your "Processors" node is at the root and not "MigrationTools:Processors" where its suposed to be... :)

You have an extra }, after "MigrationTools:Endpoints"

[amalavarghese]

Thankyou for the quick response. That was a miss from my end.
But still I am facing another issue, which I got earlier also and in resolving this error I landed into an extra '}' error :).

Now I am getting PAT access error, even though I have given full access.

[20:20:34 INF] [16.0.3] Beginning run of 2 processors
[20:20:34 INF] [16.0.3] Processor: TfsWorkItemMigrationProcessor
[20:20:34 INF] [16.0.3] Migration Context Start: TfsWorkItemMigrationProcessor
[20:20:34 INF] [16.0.3] Migrating all Nodes before the Processor run.
[20:20:34 INF] [16.0.3] Connecting with AccessToken
Error logged to Elmah.io!
!! Check for latest version - We fix issues constantly - If not, please create a discussion on https://github.com/nkdAgility/azure-devops-migration-tools/discussions so we can get this fixed !!
[20:20:37 ERR] [16.0.3] Unable to configure store: Check persmissions and credentials for AccessToken: TF31002: Unable to connect to this Azure DevOps Server: https://dev.azure.com//.
Azure DevOps Server Url: https://dev.azure.com//.

Possible reasons for failure include:

• The name, port number, or protocol for the Azure DevOps Server is incorrect.
• The Azure DevOps Server is offline.
• The password has expired or is incorrect.

Technical information (for administrator):
The remote server returned an error: (404) Not Found.
[20:20:37 ERR] [16.0.3] The PAT MUST be 'full access' for it to work with the Object Model API.

[MrHinsh]

Either the URL is bad or the PAT token is. From the data above it looks like the URL.