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/
- PrafulBusaJan 11, 2021
Microsoft
found this issue is happening only one New Microsoft Edge browser. It's working/playing fine without any issue on Chrome browser.
for the below error
There’s a problem with the network.
Client Session ID 3c08ef4a-c4dd-468a-83de-d59adff47996
Error code 0x20200259 - PrafulBusaJan 10, 2021
Microsoft
- Jimena_RamosMay 27, 2020Copper Contributor
Estimado
Reciba un cordial saludo.
yo tengo el mismo error 0x20200259 al acceder a los videos de reuniones de microsoft teams..
se adjunta la imagen del error.
- Musab_AsimDec 02, 2020Copper Contributor
I am also having this issue when I try to play some previous recorded lectures that one of my teachers uploaded. And this happens only for certain videos, I don't know why...
- Jason DennessDec 02, 2020Brass ContributorIs it only you that gets the error or can others play the video?
- Bill BlaisJun 27, 2017Iron Contributor
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).
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?
- 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?
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.