When I initially tried to update Plex Media Server to 1.5.0.3501 (Windows 10 Pro, Newest Updates Installed) it crashed, leaving me unable to install or uninstall flex due to unavailable network resource errror. After finding a helpful forums post, which I have now lost, I was able to fix the issue my extracting the msi to get the missing resources and was able to update the server successfully. Since then I have also done a successful repair function with the 1.5 installer too. Since then I have had an issue with any device that needs conversion (PS3, Chromecast). It shows the library and media information, but as soon as you select play, it just shows up as an error. They will pull up my server and the movie information, but as soon as I try to start playing it says “unable to cast”. Surprisingly the server will stream to iOS, tvOS, and Amazon TV devices just fine. I have attached my server logs and photos showing what the phone and chrome cast display when you try to start media. I attempted to chrome cast a movie right before collecting the logs. Any ideas would be helpful. Would prefer not having to setup my entire plex server again.
Thank you for the logs.
When you revert to the Public version, all is normal again? (there have been reports of issues with the latest Windows updates and why I ask)
I have not tried downgrading. I can try that tomorrow if that is what you suggest as the first step?
Yes.
If you search in the threads, you’ll see where we’re working hard on identifying what the problem is exactly.
Please do feel free to try what we’re testing… and report back.
ChuckPA, so I tried rolling back to version 1.4.4.3495 and still had the issue. Rolling back to 1.3.4 has fixed the issue. I have attached the logs for the successful playing with 1.3.4.3285 if they will help at all.
Perfect. Thank you.
This is showing what we are pinning down very clearly for the dev team. Please be patient with us now as we pull it all together? (there’s a lot of information to go through and stuff on my side to write up properly)
Wanted to let you know I updated to 1.5.1 today and it fixed my issue!
Thanks for the feedback!!
