attachments did not migrate due to error: limit of 0 bites for Azure DevOps

[creed777]

I completed a migration run and everything looked correct except that no attachments were migrated. Below is an example of an mp4 attachment, but it's the same error for anything (html, png, pdf, etc). I can't find anywhere in Devops that limits attachment sizes, so I assume the problem is something else?

Also, once this issue is resolved can I run the AttachmentMigrationEnricher by itself and update the items that are already migrated or do I run the full migration again and maybe it will add the documents?

[10:21:02 INF] [v15.0.4] AttachmentMigrationEnricher: Migrating 1 attachemnts from 4622 to 13698
[10:21:02 DBG] [v15.0.4] MAS 1.4.13_Leap Sponsorship Portal_ReadOnly_EditField.mp4
[10:21:02 DBG] [v15.0.4] ...downloading MAS 1.4.13_Leap Sponsorship Portal_ReadOnly_EditField.mp4 to c:\temp\WorkItemAttachmentExport\4622
[10:21:03 DBG] [v15.0.4] AttachmentMigrationEnricher: Exported MAS 1.4.13_Leap Sponsorship Portal_ReadOnly_EditField.mp4 to disk
[10:21:03 WRN] [v15.0.4] [SKIP] Attachment MAS 1.4.13_Leap Sponsorship Portal_ReadOnly_EditField.mp4 on Work Item 13698 is bigger than the limit of 0 bites for Azure DevOps.
[10:21:03 DBG] [v15.0.4] AttachmentMigrationEnricher: Imported MAS 1.4.13_Leap Sponsorship Portal_ReadOnly_EditField.mp4 from disk
[10:21:03 INF] [v15.0.4] [ Bug][Complete: 7/498][sid: 4622|Rev: 14][tid: null | Links 1 | LinkMigrator:true

config.json

[MrHinsh]

The MaxAttachmentSize defaults to 480000000 bits, which is the default limit for Azure DevOps. This can't be changed.

You can rerun for that specific work item and it will bring over any missing attachments or links.

Reference: TfsAttachmentEnricherOptions

[creed777]

But these are coming from another ADO. How could they be too big?

[MrHinsh]

If that ADO was imported from TFS then it can have attachments that are too big to upload.

[creed777]

I couldn't respond properly yesterday as it was a US Holiday and I was on my phone. (Anniversary of the British colonies revolting :-) ) Anyway, the error is referring to a limit of zero bites. Maybe that's a bad error message from ADO? All of these attachments are well below the 60MB limit (480000000 bits). I'm going to run the attachment enricher and see if I can get them to move.

[creed777]

I did some debugging and found the MaxAttachmentSize is coming through as zero.

The Config.TFSAttachmentEnricher did not have a MaxAttachementSize so I added it with the max value allowed. It made no difference; it was still zero in the debugger.

[MrHinsh]

With the follwing in my config I get MaxAttachmentSize set to the correct value.

    {
      "$type": "TfsAttachmentEnricherOptions",
      "RefName": "TfsAttachmentEnricher",
      "Enabled": true,
      "ExportBasePath": "c:\\temp\\WorkItemAttachmentExport",
      "MaxAttachmentSize": 480000000
    },

[creed777]

I was missing the RefName. Thank you.