This repository has been archived by the owner on Jan 23, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 86
Unbale to add azure storage account to MK/IO through azure media service explorer , error like storage failed validation, location not found #191
Comments
@Diwakar488 Hello, I will look to the issue tomorrow. How did you import the account into AMSE ? |
Hi Xavier,
Greeting for the day.
I had import through AMS resource id and Azure AD tenant id, fro more
details please see below screenshot.
[image: image.png]
[image: image.png]
After login into my account I'm able to see all AMS resources like assets ,
storage account, streaming endpoint but when trying to create
assets(migrate asste) from AMS to MK/IO below error occurred
[image: image.png]
but when I tried to add this account from Azure storage account to MK/IO
error show storage validation failed, location not found.
[image: image.png]
Kindly provide you guidance on this so I can solve this issue, after a few
days AMS retired and yet not migrate all assets from AMS to MK/IO, kindly
assist with this..
Thanks & Regards
Diwakar Tiwari
…On Thu, Jun 20, 2024 at 2:24 AM Xavier Pouyat ***@***.***> wrote:
@Diwakar488 <https://github.com/Diwakar488> Hello, I will look to the
issue tomorrow. How did you import the account into AMSE ?
—
Reply to this email directly, view it on GitHub
<#191 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BJI6BAHFBNK32OY65GKMHFDZIHVYRAVCNFSM6AAAAABJPNNZECVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZZGQ2DINZVGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Thanks & Regards,
*Diwakar Tiwari*
Mail Id- ***@***.**** ***@***.***>
--
Disclaimer: This e-mail & attachment(s) within it are for sole use of
intended recipient(s) & may contain confidential & privileged information.
If you are not the intended recipient, please intimate the sender by
replying to this email & destroy all copies & the original message. Any
unauthorized review, use, disclosure, dissemination, forwarding, printing
or copying of this email or any action taken in reliance on this e-mail is
strictly prohibited & unlawful. The recipient acknowledges that COMPANY ,
its subsidiaries, associated companies or persons authorized by it
(collectively "THE Group"), are unable to exercise control, ensure,
guarantee the integrity of/over the contents of the information contained
in e-mail transmissions & further acknowledges that any views expressed in
this message are those of the individual sender & no binding nature of the
message shall be implied or assumed unless the sender does so expressly
with due authority of THE Group.
|
Thanks ! @Diwakar488 Can you send the screenshots to [email protected] ? I don't see them. |
Also, please confirm what is the location of your storage account. |
I looked to AMSE code and the location is reported by the AMS SDK. I wonder if your storage account is in a MK.IO supported region https://docs.mk.io/docs/azure-region-support May be the MK.IO API refuses the connection if you are outside. |
Hi Xavier,
My Azure storage account location is South Central US.As I have checked
K/IO supports a few locations only.
Current production regions:
- West Europe
- West US 2
- Central US NEW
- East US
- UK South
- France Central
- Japan East
- Japan West
Is that the reason ?I'm unable to migrate my existing storage account with
MK/IO. Then how I can bulk migrate our existing assets into MK/IO..
Thanks & Regards
Diwakar Tiwari
…On Thu, Jun 20, 2024 at 2:45 PM Xavier Pouyat ***@***.***> wrote:
I looked to AMSE code and the location is reported by the AMS SDK. I
wonder if your storage account is in a MK.IO supported region
https://docs.mk.io/docs/azure-region-support May be the MK.IO API refuses
the connection if you are outside.
—
Reply to this email directly, view it on GitHub
<#191 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BJI6BAEX4EZ3Q64JESBBIVLZIKMSTAVCNFSM6AAAAABJPNNZECVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBQGIYDINBZHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Thanks & Regards,
*Diwakar Tiwari*
Mail Id- ***@***.**** ***@***.***>
--
Disclaimer: This e-mail & attachment(s) within it are for sole use of
intended recipient(s) & may contain confidential & privileged information.
If you are not the intended recipient, please intimate the sender by
replying to this email & destroy all copies & the original message. Any
unauthorized review, use, disclosure, dissemination, forwarding, printing
or copying of this email or any action taken in reliance on this e-mail is
strictly prohibited & unlawful. The recipient acknowledges that COMPANY ,
its subsidiaries, associated companies or persons authorized by it
(collectively "THE Group"), are unable to exercise control, ensure,
guarantee the integrity of/over the contents of the information contained
in e-mail transmissions & further acknowledges that any views expressed in
this message are those of the individual sender & no binding nature of the
message shall be implied or assumed unless the sender does so expressly
with due authority of THE Group.
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Unbale to add azure storage account to MK/IO through azure media service explorer , error like storage failed validation, location not found. KIndly help for this issue.
The text was updated successfully, but these errors were encountered: