My PMS is running on Windows 7x64
I started getting this error Yesterday 4.30.2018 on my Phone while using plex for some videos but not all. Took me about 30 minutes to figure this out.
Thought = what’s changed in the last few days?
Answer = Auto Update of PMS to 1.13.0.5003-8fcb5b6e5 on 04.27.2018.
Solution = Rollback PMS → Clear Cache of Apps = Good to go!
What I did to trouble shoot:
- Checked that files are complete with no issues scrubbing through source files
- Checked I had latest update
- tested files I was able to play without issue last week (same error)
- Tried updating apps on both tablet & phone (same error)
- Searched forums & did the whole [stop server → delete 4 *.gdb files → restart server = (same error)
- Cleared cache & data (same error)
What worked for me: emphasis on the “for me” part
- Go into server setting disable auto update & set to manual/ask
- Uninstall [ PMS 1.13.0.5003-8fcb5b6e5 April 27, 2018 ] (Leave settings and files)
- Download & Install last release that seemed to work [ Plex-Media-Server-1.12.3.4973-215c28d86 ]
- All working fine again including newly added files that initially threw the error and all old files that previously worked are now working again.
Hope this help you guys!
3 Likes
I am going to delete all your 5 posts where you told others that you had the same issue and you fixed as above. Saying that does not help solve the problem and in any case transcoder errors could be due to many different reasons and you cannot say to everyone it was the same as your problem.
Please do not do that again
Reverting to a previous version does not help get the problem addressed and is a short term outcome.
So please if you have a problem - provide logs from the server with debug logs and media info xml. After initial investigation, it may be necessary to ask for a sample file to reproduce the problem
https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
https://support.plex.tv/articles/201998867-investigate-media-information-and-formats/
https://support.plex.tv/articles/201035968-generating-sample-files-from-media/
@sa2000 said:
I am going to delete all your 5 posts where you told others that you had the same issue and you fixed as above. Saying that does not help solve the problem and in any case transcoder errors could be due to many different reasons and you cannot say to everyone it was the same as your problem.
Please do not do that again
Reverting to a previous version does not help get the problem addressed and is a short term outcome.
So please if you have a problem - provide logs from the server with debug logs and media info xml. After initial investigation, it may be necessary to ask for a sample file to reproduce the problem
https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
https://support.plex.tv/articles/201998867-investigate-media-information-and-formats/
https://support.plex.tv/articles/201035968-generating-sample-files-from-media/
Understood & it won’t happen again.
To be clear, my intent wasn’t malicious.
I was just trying to help folks who seemed to have a “similar” issue, which is why i used the word similar.
I totally get that the fix i found to work “for me” may not work for others. That’s again why I put intentional emphasis on the “for me” disclaimer. eg; your mileage may vary It’s also why I went the extra step to put my Os version and call to attention this was a recent issue and was most likely caused by the update on the 27th.
Do I intend to stay on an out dated version of plex indefinitely?
No, plex is great as are the devs that maintain and constantly improve it.
My purpose was to get up and running and help folks do the same. When I get more than the 30 minutes it took to figure out my solution I’ll look into submitting logs.
3 Likes
@BiGgRiE said:
@sa2000 said:
I am going to delete all your 5 posts where you told others that you had the same issue and you fixed as above. Saying that does not help solve the problem and in any case transcoder errors could be due to many different reasons and you cannot say to everyone it was the same as your problem.
Please do not do that again
Reverting to a previous version does not help get the problem addressed and is a short term outcome.
So please if you have a problem - provide logs from the server with debug logs and media info xml. After initial investigation, it may be necessary to ask for a sample file to reproduce the problem
https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
https://support.plex.tv/articles/201998867-investigate-media-information-and-formats/
https://support.plex.tv/articles/201035968-generating-sample-files-from-media/
Understood & it won’t happen again.
To be clear, my intent wasn’t malicious.
I was just trying to help folks who seemed to have a “similar” issue, which is why i used the word similar.
I totally get that the fix i found to work “for me” may not work for others. That’s again why I put intentional emphasis on the “for me” disclaimer. eg; your mileage may vary It’s also why I went the extra step to put my Os version and call to attention this was a recent issue and was most likely caused by the update on the 27th.
Do I intend to stay on an out dated version of plex indefinitely?
No, plex is great as are the devs that maintain and constantly improve it.
My purpose was to get up and running and help folks do the same. When I get more than the 30 minutes it took to figure out my solution I’ll look into submitting logs.
Getting other users to downgrade whilst they have issues being investigated would impact the current investigations
Reverting to old version may make the problem go away but it does not in any way help getting the problem addressed and investigated and fixed
Do you have any debug logs from the server for the issue on 1.13.0.5003 ? Any file that it fails with?
and can I have debug logs of the server from the version that works ok
1 Like
And FWIW, upgrading TO THE VERSION YOU WANTED ME TO REMOVE is what fixed my problem.
For the record, I was running the same version on my PR4100, and started having the exact same symptoms. It was also completely bringing down the server, disrupting all users. I, too, resolved the problem quickly and easily by reverting to a previous version. You may not want people to encourage others to do that, and I understand your reasoning, but the fact is that this is a commercial product, and this is the single page on Google that addresses this problem, so I damn well want to see a rapid solution to a highly disruptive problem.
Feel free to tell people that if they have the time, energy, and lack of responsibilities necessary to help you track down the issue, you’d love to have them help, but don’t discourage the dissemination of functioning workarounds for the people that need it, some of whom are paying customers.
25 Likes
@dmiller67 said:
For the record, I was running the same version on my PR4100, and started having the exact same symptoms. It was also completely bringing down the server, disrupting all users. I, too, resolved the problem quickly and easily by reverting to a previous version. You may not want people to encourage others to do that, and I understand your reasoning, but the fact is that this is a commercial product, and this is the single page on Google that addresses this problem, so I damn well want to see a rapid solution to a highly disruptive problem.
Feel free to tell people that if they have the time, energy, and lack of responsibilities necessary to help you track down the issue, you’d love to have them help, but don’t discourage the dissemination of functioning workarounds for the people that need it, some of whom are paying customers.
There will not be a rapid fix if you advise other users that are having their issue investigated to revert to an old version. The only posts that were deleted were ones added to lots of other forum threads - most unrelated - advising them to revert versions
I did not delete this forum thread
Again, @sa2000 as a real person, in the real world, who pays real money for this, when my and my family’s experience is on the line, sometimes, I don’t care that it’s going to slow down a solution, if there’s a quick and functional workaround, which I think we’ve all confirmed there is. Yes, I know that your paying customers knowing that there’s a way to resolve a debilitating problem without helping you investigate the ultimate solution does slow down that solution. Regardless, your customer base is becoming less and less a tight community of hobbyists, and discouraging us from communicating those workarounds doesn’t do Plex’s image any favors.
29 Likes
I understand, and as I said, I kept this forum thread going,
What I objected to was going round all threads relating to transcoder errors regardless of what the underlying issue was and regardless of what version was being used and pointing them to this topic, when we were in the middle of actual investigations. I feel that was disruptive and unwarranted.
Users can find this thread - there is no need to go round posting in every other thread
1 Like
I experienced the same issues with 1.3.0.5003, can someone please update this post as a new version is available which fix this? First time I disabled autoupdate…
@rdevrede said:
I experienced the same issues with 1.3.0.5003, can someone please update this post as a new version is available which fix this? First time I disabled autoupdate…
The only issue I investigated with logs provided from 3 users relates to Media Foundation on Windows and yes a special build with a fix was tested and confirmed as fixed by one of the users.
I have not had logs for this issue from anyone else
The Transcoder Conversion Error is a generic error and could be due to different underlying issues
Can I test this fix also? If needed, where to send logfiles?
@rdevrede said:
Can I test this fix also? If needed, where to send logfiles?
Please ensure debug logging enabled on the server (settings / server / general ) and restart the server and reproduce the problem and download the logs zip (settings / server / help / download logs) and attach to post here
I already reverted to the previous version without debugging enabled so I dont have logfiles when it occurs, also I will not post logfiles here due to API, security and privacy reasons. I’m willing to test the new patch or I wait for the new version.
I also had the same problem on both my Plex servers. Playback worked locally on the network, but not from remote on the same machine/browser. I tried both browser based and from a iPhone. The same second I downgraded one of the servers to 1.12 it worked again and the other one also started as well when that was downgraded, so 1.13 clearly has issues.
1 Like
There may be issues but the only issue that is being fixed at the moment is the eac3 Media Foundation windows issue that we had logs for and was investigated and the issue identified and fixed and the fix is expected in the next release
@earl7399 said:
And FWIW, upgrading TO THE VERSION YOU WANTED ME TO REMOVE is what fixed my problem.
“Cool story bro, you should start a thread, just be sure not to share it in any other threads (¬_¬)”
( ͡° ͜ʖ ͡°) Slight digs aside, I really was just trying to help. I also get the rationale of not disseminating info that could stunt progress on solving an issue/bug, which is why I chose my words very carefully in the OP.
I’m constantly trouble shooting things for folks and know how the minutia & specificity of one’s setup can impact whether or not a solution/work around helps or hurts.
I mean no offense to anyone, just trying to do my part and help the growing user base of Plex, which seems to have helped a few folks.
This “work around” works for me and at the very least I have a functioning fall back of a server version that currently works for my setup ¯_(ツ)_/¯.
@dmiller67
Appreciate you communicating your understanding of the use-case/intent of the OP.
having the same issue iOS clients on home networks and remote users all report the same error “conversion failed transcoder exited due to an error) . im similarly miffed by the autoupdate release and the shade thrown for a quick workaround . logs attached hoping for a new release or fix.
@jmohin said:
having the same issue iOS clients on home networks and remote users all report the same error “conversion failed transcoder exited due to an error) . im similarly miffed by the autoupdate release and the shade thrown for a quick workaround . logs attached hoping for a new release or fix.
Your log does show the Media Foundation codecs issue.
May 06, 2018 12:09:03.499 [5416] ERROR - [Transcoder] [eac3_mf @ 03c3c080] could not create MFT
May 06, 2018 12:09:03.511 [5164] ERROR - [Transcoder] Error while opening decoder for input stream #0:1 : Function not implemented
May 06, 2018 12:09:03.518 [4412] VERBOSE - JobManager: child process with handle 0xa44 exited
May 06, 2018 12:09:03.518 [4412] DEBUG - Jobs: 'C:\Program Files (x86)\Plex\Plex Media Server\PlexTranscoder.exe' exit code for process 428 is 1 (failure)
May 06, 2018 12:09:03.519 [5736] DEBUG - Streaming Resource: Terminated session 0x4b800e8:59379C30-8AF2-49F2-811C-595EA074D0BF with reason Conversion failed. The transcoder exited due to an error.
I have sent you a link to the pre-release version that has the fix. It is expected to be officially released in the next beta release
