Azure Media Services v3 CreateEvent Hangs
I am using the example code from The Azure GitHub page. I've been messing with it for a few hours, sometimes the LiveEvent.Create works pretty instantly, sometimes it just hangs. Right now its going on 50 minutes. Can someone help with what i'm doing wrong? Is there a way to figure out why this is hanging? If we are using this in a live production, not having reliable start times is a real problem. This is the line it fails on:
liveEvent = client.LiveEvents.Create(config.ResourceGroup, config.AccountName, liveEventName, liveEvent, autoStart:true);
Can anyone help?
c# .net-core azure-media-services
asked Nov 13 '18 at 23:06
Chris KookenChris Kooken
22k1172106
|
show 1 more comment
I am using the example code from The Azure GitHub page. I've been messing with it for a few hours, sometimes the LiveEvent.Create works pretty instantly, sometimes it just hangs. Right now its going on 50 minutes. Can someone help with what i'm doing wrong? Is there a way to figure out why this is hanging? If we are using this in a live production, not having reliable start times is a real problem. This is the line it fails on:
liveEvent = client.LiveEvents.Create(config.ResourceGroup, config.AccountName, liveEventName, liveEvent, autoStart:true);
Can anyone help?
c# .net-core azure-media-services
asked Nov 13 '18 at 23:06
Chris KookenChris Kooken
22k1172106
Even the comments in the code saysThe following operation can sometimes take awhile. Be patient.
– Nkosi
Nov 13 '18 at 23:20
I do see that, but its now going on 90 minutes.
– Chris Kooken
Nov 13 '18 at 23:36
Yeah I can see how that is a bit excessive.
– Nkosi
Nov 13 '18 at 23:37
Have you tried finding the source code to see what that call does internally?
– Nkosi
Nov 13 '18 at 23:38
90 minutes is very excessive. Can you send details to amshelp@microsoft.com with your subscription ID, region, account name and the time period this happened at please
– johndeu
Nov 15 '18 at 1:08
|
show 1 more comment
I am using the example code from The Azure GitHub page. I've been messing with it for a few hours, sometimes the LiveEvent.Create works pretty instantly, sometimes it just hangs. Right now its going on 50 minutes. Can someone help with what i'm doing wrong? Is there a way to figure out why this is hanging? If we are using this in a live production, not having reliable start times is a real problem. This is the line it fails on:
liveEvent = client.LiveEvents.Create(config.ResourceGroup, config.AccountName, liveEventName, liveEvent, autoStart:true);
Can anyone help?
c# .net-core azure-media-services
asked Nov 13 '18 at 23:06
Chris KookenChris Kooken
22k1172106
I am using the example code from The Azure GitHub page. I've been messing with it for a few hours, sometimes the LiveEvent.Create works pretty instantly, sometimes it just hangs. Right now its going on 50 minutes. Can someone help with what i'm doing wrong? Is there a way to figure out why this is hanging? If we are using this in a live production, not having reliable start times is a real problem. This is the line it fails on:
liveEvent = client.LiveEvents.Create(config.ResourceGroup, config.AccountName, liveEventName, liveEvent, autoStart:true);
Can anyone help?
c# .net-core azure-media-services
c# .net-core azure-media-services
asked Nov 13 '18 at 23:06
Chris KookenChris Kooken
22k1172106
asked Nov 13 '18 at 23:06
Chris KookenChris Kooken
22k1172106
asked Nov 13 '18 at 23:06
Chris KookenChris Kooken
22k1172106
asked Nov 13 '18 at 23:06
Chris KookenChris Kooken
22k1172106
asked Nov 13 '18 at 23:06
Chris KookenChris Kooken
22k1172106
22k1172106
Even the comments in the code saysThe following operation can sometimes take awhile. Be patient.
– Nkosi
Nov 13 '18 at 23:20
I do see that, but its now going on 90 minutes.
– Chris Kooken
Nov 13 '18 at 23:36
Yeah I can see how that is a bit excessive.
– Nkosi
Nov 13 '18 at 23:37
Have you tried finding the source code to see what that call does internally?
– Nkosi
Nov 13 '18 at 23:38
90 minutes is very excessive. Can you send details to amshelp@microsoft.com with your subscription ID, region, account name and the time period this happened at please
– johndeu
Nov 15 '18 at 1:08
|
show 1 more comment
Even the comments in the code saysThe following operation can sometimes take awhile. Be patient.
– Nkosi
Nov 13 '18 at 23:20
I do see that, but its now going on 90 minutes.
– Chris Kooken
Nov 13 '18 at 23:36
Yeah I can see how that is a bit excessive.
– Nkosi
Nov 13 '18 at 23:37
Have you tried finding the source code to see what that call does internally?
– Nkosi
Nov 13 '18 at 23:38
90 minutes is very excessive. Can you send details to amshelp@microsoft.com with your subscription ID, region, account name and the time period this happened at please
– johndeu
Nov 15 '18 at 1:08
Even the comments in the code says
The following operation can sometimes take awhile. Be patient.– Nkosi
Nov 13 '18 at 23:20
Even the comments in the code says
The following operation can sometimes take awhile. Be patient.– Nkosi
Nov 13 '18 at 23:20
I do see that, but its now going on 90 minutes.
– Chris Kooken
Nov 13 '18 at 23:36
I do see that, but its now going on 90 minutes.
– Chris Kooken
Nov 13 '18 at 23:36
Yeah I can see how that is a bit excessive.
– Nkosi
Nov 13 '18 at 23:37
Yeah I can see how that is a bit excessive.
– Nkosi
Nov 13 '18 at 23:37
Have you tried finding the source code to see what that call does internally?
– Nkosi
Nov 13 '18 at 23:38
Have you tried finding the source code to see what that call does internally?
– Nkosi
Nov 13 '18 at 23:38
90 minutes is very excessive. Can you send details to amshelp@microsoft.com with your subscription ID, region, account name and the time period this happened at please
– johndeu
Nov 15 '18 at 1:08
90 minutes is very excessive. Can you send details to amshelp@microsoft.com with your subscription ID, region, account name and the time period this happened at please
– johndeu
Nov 15 '18 at 1:08
|
show 1 more comment
1 Answer
1
active
oldest
votes
The problem was found to be specific to the region (East US 2), where the necessary resources had not been configured correctly. A hotfix has been deployed to fix it, and you should be able to create and use LiveEvents in this region.
answered Nov 16 '18 at 5:52
Anil MurchingAnil Murching
31025
Yes. This was the problem. I engaged MS support and they confirmed the bug. All is fixed now.
– Chris Kooken
Nov 26 '18 at 15:59
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53290835%2fazure-media-services-v3-createevent-hangs%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The problem was found to be specific to the region (East US 2), where the necessary resources had not been configured correctly. A hotfix has been deployed to fix it, and you should be able to create and use LiveEvents in this region.
answered Nov 16 '18 at 5:52
Anil MurchingAnil Murching
31025
Yes. This was the problem. I engaged MS support and they confirmed the bug. All is fixed now.
– Chris Kooken
Nov 26 '18 at 15:59
add a comment |
The problem was found to be specific to the region (East US 2), where the necessary resources had not been configured correctly. A hotfix has been deployed to fix it, and you should be able to create and use LiveEvents in this region.
answered Nov 16 '18 at 5:52
Anil MurchingAnil Murching
31025
Yes. This was the problem. I engaged MS support and they confirmed the bug. All is fixed now.
– Chris Kooken
Nov 26 '18 at 15:59
add a comment |
The problem was found to be specific to the region (East US 2), where the necessary resources had not been configured correctly. A hotfix has been deployed to fix it, and you should be able to create and use LiveEvents in this region.
answered Nov 16 '18 at 5:52
Anil MurchingAnil Murching
31025
The problem was found to be specific to the region (East US 2), where the necessary resources had not been configured correctly. A hotfix has been deployed to fix it, and you should be able to create and use LiveEvents in this region.
answered Nov 16 '18 at 5:52
Anil MurchingAnil Murching
31025
answered Nov 16 '18 at 5:52
Anil MurchingAnil Murching
31025
answered Nov 16 '18 at 5:52
Anil MurchingAnil Murching
31025
answered Nov 16 '18 at 5:52
Anil MurchingAnil Murching
31025
31025
Yes. This was the problem. I engaged MS support and they confirmed the bug. All is fixed now.
– Chris Kooken
Nov 26 '18 at 15:59
add a comment |
Yes. This was the problem. I engaged MS support and they confirmed the bug. All is fixed now.
– Chris Kooken
Nov 26 '18 at 15:59
Yes. This was the problem. I engaged MS support and they confirmed the bug. All is fixed now.
– Chris Kooken
Nov 26 '18 at 15:59
Yes. This was the problem. I engaged MS support and they confirmed the bug. All is fixed now.
– Chris Kooken
Nov 26 '18 at 15:59
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53290835%2fazure-media-services-v3-createevent-hangs%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Even the comments in the code says
The following operation can sometimes take awhile. Be patient.– Nkosi
Nov 13 '18 at 23:20
I do see that, but its now going on 90 minutes.
– Chris Kooken
Nov 13 '18 at 23:36
Yeah I can see how that is a bit excessive.
– Nkosi
Nov 13 '18 at 23:37
Have you tried finding the source code to see what that call does internally?
– Nkosi
Nov 13 '18 at 23:38
90 minutes is very excessive. Can you send details to amshelp@microsoft.com with your subscription ID, region, account name and the time period this happened at please
– johndeu
Nov 15 '18 at 1:08