Forum Discussion
Error code 0x20200259
- Jun 21, 2017
Glad it's working for you now. Not sure what issue you were seeing intially. If you run into problems again let us know. If you send us a screenshot it might help us see what's going on.
We have the supported video formats documented here (or there is a link in product at the bottom of the upload page): https://stream.microsoft.com/en-us/documentation/stream-formats/
And upload error codes documented here: https://stream.microsoft.com/en-us/documentation/stream-portal-understanding-playback-errors/
Glad it's working for you now. Not sure what issue you were seeing intially. If you run into problems again let us know. If you send us a screenshot it might help us see what's going on.
We have the supported video formats documented here (or there is a link in product at the bottom of the upload page): https://stream.microsoft.com/en-us/documentation/stream-formats/
And upload error codes documented here: https://stream.microsoft.com/en-us/documentation/stream-portal-understanding-playback-errors/
We're having/had/having a similar issue today. Slightly different error codes (0x20200258, 0x20200194, etc), but all with same basic issue. See video of the issue below.
It was working fine previously. Same experience in multiple browsers. 1 out of 10 tries may start playing, but even then will eventually fail mid-play after 30-45 seconds. This is true for existing videos and new videos (all .mp4 originally).
- Marc MrozJun 27, 2017
Microsoft
Most frustratingly, the link to 'contact support' is to a page that doesn't exist with no other info. The links you gave would be helpful there, but they really don't explain the problem (and some of our error codes aren't listed there). Is there something larger happening?
In additon I filed a bug on our side to address that "Contact support" link not going anywhere.
- Bill BlaisJun 27, 2017Iron ContributorExcellent!
I just got in contact with our engineering team, there is a sev2 issue affecting Azure Media Services (which is used under the covers in Stream). On call engineers are investigating the issue right now to determine the root cause and how to mitigate/fix the issue.
So no need for the traces / info, it looks like there is an underlying escalation affecting playback at this point in time. So sorry for the issues. We'll let you know more as we have it.
- DeletedSep 20, 2017Hello Marc,
I tried to upload a new video and I encounter the same issue (Error code 0x20200259). Same error occurred for the existing videos.
Is there any update from engineering team about the sev2 issue?- Nicola LegittimoOct 19, 2017Copper Contributor
We have the same issue after uploading an MP4 video. Could it be a timeout problem as the video size is 650mb? It works on some clients but not on all.
- Bill BlaisJun 27, 2017Iron Contributor
Thanks Marc Mroz. Is there a place for more pro-active notifications of such issues? Even if they're not affecting everyone, it would be good to have a place to check to see if there are any disruptions. Perhaps through an admin panel? Anyway, thanks for digging into it and looking forward to hearing what the issue is.
- Marc MrozJun 27, 2017
Microsoft
Bill Blais wrote:
Thanks Marc Mroz. Is there a place for more pro-active notifications of such issues? Even if they're not affecting everyone, it would be good to have a place to check to see if there are any disruptions. Perhaps through an admin panel? Anyway, thanks for digging into it and looking forward to hearing what the issue is.
We are still identifying a process for how we can do pro-active notification of issues like this. We are looking into the O365 Service Health Dashboard, etc. Untill then feel free to come here and post on the forum for us to look at and answer.
Bill Blais - Would you be able to send us a fiddler trace (with HTTPS decrypted) as you try and play a video and it fails? If you could also send us the info from ? > About Microsoft Stream, we can start looking into what's happening. (You can send me a private message here on the MS Tech Community).
I'll also log into some demo test tenants and see if I can reproduce the issue on my end as well.
So sorry you are having issues.