AMS Migration tool issue

[bechtdev]

Product

Other

Question

Hello there!

I have used the AMS Migration tool (https://ams.bitmovin.com/) to serve my content via Bitmovin. The migration is showing up as a success, but the provided playback of my content fails with the error message SOURCE_COULD_NOT_LOAD_MANIFEST.

Checking into the console, I see a 403 forbidden and opening the manifest manually I get the following response:


403
1000
MPE_STORAGE_AUTHENTICATION_FAILURE
80001159-0001-FF00-B63F-84710C7967BB
00000000-0000-0000-0000-000000000000

What could possibly be causing this issue?

[albertobitmovin]

Hi @bechtdev ,

Thanks for posting. To discard any missed steps or issues during the process with that tool, what results do you get when running this alternative tool locally instead? https://github.com/bitmovin/azure-media-services-migration?tab=readme-ov-file#bitmovin-azure-migration-tool

PS: Microsoft also offers their own tool: azure-media-migration/migrationTool/README.md at main · Azure/azure-media-migration · GitHub

Azure Media Services Migration Guide

[jason.grey]

What was the solution here? Were you able to ever resolve it?

[albertobitmovin]

Most common reason for this is that someone without the required privileges ran the migration. Worth checking if you see the role from the screenshot attached on your media service account? (under Access control (IAM) → Role assignments)

[jason.grey]

I tried both on the media services resource, and it’s associated storage resource, and that role does not show up as an option to assign.
The media service, and associated storage were created quite some time ago, not sure if that matters.
Storage - appears to be “Storage account (classic)” - so, perhaps some old kind? It does not appear to need the role you describe to function. And my user is an owner on it (and was the user who ran the migration as well)