SOLUTION: Conversion failed. The transcoder exited due to an error

[cbabb]

@CinemaBen

The OP spreading a way for other customers to get the program to work RIGHT NOW is the standard and encouraged behavior for any software product.

Two things.

1. Cross posting is not allowed. This is where you are wrong. Whether it be a topic or response. The user went to FIVE other threads and posted his solution as well as creating a topic. This is against the rules.
2. Of course temporary solutions are welcomed. However, they do not solve the problem in the long run. In fact I even submitted a temporary solution to a problem there was recently and it worked. Many people used it. Then six days later an actual solution was found.

@CinemaBen

Your desire to suppress the stopgap fix so that plex can obtain information is ridiculous,

No, not the case. The user broke the rules. @sa2000 is a team member at Plex and always looks for the correct solution. Not just a band-aid fix. His response was to correct the behavior so the user understands it is not allowed.

@CinemaBen

your judgement is way out of line

This is your opinion. You are out of line.

@CinemaBen

Plex should roll back the update itself instead of withholding a working product for x days or weeks.

Rolling back an update isn’t something that many companies do. They release a patch to fix the issue. The case of the transcoder stopping can be the result of many things. Hardware or software. The possibilities are massive.

Please do not bring negative behavior into the forums. If you don’t agree with something, you are welcome to share in a constructive manner.

[kcwebmonkey]

I just received the error as well, running 1.134.5271. pertinent logs below:

Aug 01, 2018 13:53:23.934 [8712] DEBUG - Asked for segment 185 from session.
Aug 01, 2018 13:53:23.934 [8712] DEBUG - Returning segment 185 from session: "K:\PlexTrancodingTemp\Transcode\Sessions\plex-transcode-64uwkt5xcy2h4br6382gmtvg-540b1e06-28c6-42ef-945f-9fb02b7fdd95\chunk-stream0-00186.m4s"
Aug 01, 2018 13:53:23.934 [8712] VERBOSE - [IDLE] Adding (0->1) work item http_download - /video/:/transcode/universal/dash/64uwkt5xcy2h4br6382gmtvg/0/185.m4s
Aug 01, 2018 13:53:23.934 [8712] VERBOSE - [IDLE] * http_download - /player/proxy/poll?deviceClass=pc&protocolVersion=1&protocolCapabilities=timeline%2Cplayback%2Cnavigation%2Cmirror%2Cplayqueues&timeout=1&X-Plex-Product=Plex%20Web&X-Plex-Version=3.53.7&X-Plex-Client-Identifier=v8m5o3ewdoi0aw6qpm83rjbz&X-Plex-Platform=Chrome&X-Plex-Platform-Version=67.0&X-Plex-Sync-Version=2&X-Plex-Device=Windows&X-Plex-Device-Name=Chrome&X-Plex-Device-Screen-Resolution=1920x926%2C1920x1080&X-Plex-Token=szg7mk9HExD9xJQ5Egyj&X-Plex-Language=en - 1 active item(s)
Aug 01, 2018 13:53:23.934 [8712] VERBOSE - [IDLE] * http_download - /video/:/transcode/universal/dash/64uwkt5xcy2h4br6382gmtvg/0/185.m4s - 1 active item(s)
Aug 01, 2018 13:53:23.934 [8712] VERBOSE - [IDLE] * transcoder - 64uwkt5xcy2h4br6382gmtvg - 1 active item(s)
Aug 01, 2018 13:53:23.934 [8712] DEBUG - Content-Length of K:\PlexTrancodingTemp\Transcode\Sessions\plex-transcode-64uwkt5xcy2h4br6382gmtvg-540b1e06-28c6-42ef-945f-9fb02b7fdd95\init-stream0.m4s,K:\PlexTrancodingTemp\Transcode\Sessions\plex-transcode-64uwkt5xcy2h4br6382gmtvg-540b1e06-28c6-42ef-945f-9fb02b7fdd95\chunk-stream0-00186.m4s is 809983.
Aug 01, 2018 13:53:23.939 [7724] DEBUG - Completed: [127.0.0.1:49996] 200 GET /video/:/transcode/universal/dash/64uwkt5xcy2h4br6382gmtvg/0/185.m4s (7 live) GZIP 6ms 809983 bytes (pipelined: 83)
Aug 01, 2018 13:53:23.939 [7724] VERBOSE - [IDLE] Removing (1->0) work item http_download - /video/:/transcode/universal/dash/64uwkt5xcy2h4br6382gmtvg/0/185.m4s
Aug 01, 2018 13:53:23.939 [7724] VERBOSE - [IDLE] * http_download - /player/proxy/poll?deviceClass=pc&protocolVersion=1&protocolCapabilities=timeline%2Cplayback%2Cnavigation%2Cmirror%2Cplayqueues&timeout=1&X-Plex-Product=Plex%20Web&X-Plex-Version=3.53.7&X-Plex-Client-Identifier=v8m5o3ewdoi0aw6qpm83rjbz&X-Plex-Platform=Chrome&X-Plex-Platform-Version=67.0&X-Plex-Sync-Version=2&X-Plex-Device=Windows&X-Plex-Device-Name=Chrome&X-Plex-Device-Screen-Resolution=1920x926%2C1920x1080&X-Plex-Token=szg7mk9HExD9xJQ5Egyj&X-Plex-Language=en - 1 active item(s)
Aug 01, 2018 13:53:23.939 [7724] VERBOSE - [IDLE] * transcoder - 64uwkt5xcy2h4br6382gmtvg - 1 active item(s)
Aug 01, 2018 13:53:26.445 [16632] VERBOSE - JobManager: child process with handle 0x1050 exited
Aug 01, 2018 13:53:26.445 [16632] DEBUG - Jobs: 'K:\Program Files (x86)\Plex\Plex Media Server\PlexTranscoder.exe' exit code for process 6788 is 1 (failure)
Aug 01, 2018 13:53:26.445 [13556] DEBUG - Streaming Resource: Terminating session 0x85e84c8:bece36rjtywipg91o32vg57c which is using transcoder slot.  Used slots is now 0
Aug 01, 2018 13:53:26.446 [15876] DEBUG - Killing job.
Aug 01, 2018 13:53:26.446 [13556] DEBUG - Streaming Resource: Terminated session 0x85e84c8:bece36rjtywipg91o32vg57c with reason Conversion failed. The transcoder exited due to an error.
Aug 01, 2018 13:53:26.446 [15876] DEBUG - Job was already killed, not killing again.
Aug 01, 2018 13:53:26.446 [15876] DEBUG - Stopping transcode session 64uwkt5xcy2h4br6382gmtvg
Aug 01, 2018 13:53:26.446 [16632] DEBUG - Cleaning directory for session 64uwkt5xcy2h4br6382gmtvg (K:\PlexTrancodingTemp\Transcode\Sessions\plex-transcode-64uwkt5xcy2h4br6382gmtvg-540b1e06-28c6-42ef-945f-9fb02b7fdd95)

[aiwubf]

Had the same issues, updated Windows to KB4340917 and it seems to be working.

[lifeisabet]

I also have transcoder error, when both recording and streaming remotely. When will this be fixed? Can I use different encoder in the meantime?

[billyreichard]

Updating Windows to KB4340917 also helped me with this issue. I no longer get this error.

[Giovanniee]

Updating windows seems to have fixed the issue for me as well.

[juliancj]

Hi all, last night I had the same issue, I read a lot and it seems to be that there’s no solution yet.

I finally manage to get it working.

The problem, in my case, was having an external hard drive plugged in my PC, I just unplugged it, restart the PC and it worked as usual.

I came up with this after I saw someone having issues with playback and Plex changing the location of the media folder.

If you happen to have a USB, external hard drive or any kind of storage connected on any external USB port, give it a try.

Cheers

[mbrett]

Bummer. I just completed a transfer to my more powerful HTPC, and use an external HD for my media. Is this a known bug? I was able to record to my external HD on my original PC.

[afrancopz_hotmail.com]

I’m having the exact same issue. Server version 1.13.5.5291, via LG webOs. Server is on my PC Asus G30AB, Windows 8.1. I love Plex, I never had any issues until now, hope Plex team can fix this. Every 10 minutes the server cashes with message “Conversion failes. The transcoder exited due to an error”. My Windows is updated.

[klaus_hax.at]

Same Issue for me since a couple of versions… only happens when I watch on the pc that I have plex installed on using chrome browser. doesn’t happen when I watch trough tv’s app or firetv stick app.

[joemonster]

I’m on Windows 10 64bit and was also experiencing this for the past month or so. I also do CPU mining on my Plex server so I thought maybe that was causing issues. Rebooted fresh, nothing running, still received the transcoder error when playing any .mkv local or remote. Noticed that I had a missing update for KB4340917, installed that, and Plex has been stable. Reading on this KB patch I don’t see what is included that would change or fix the transcoder.exe Plex uses, but things definitely seem better.

[bluefrog10]

Running Win7 64bit. I installed all Windows updates, installed the latest version of Plex and set the transcoder temporary directory to a system drive root folder I created (eg. C:\PlexTemp). That did the trick for me.

[ntylerwetrust]

So far this has worked for me to. Don’t know why it is working but it has.

[Plextreme_Infinity]

This also seemed to fix it for me to also seemed to fix it on Roku as well still need to test on PS4

[Plextreme_Infinity]

Updating Windows to KB4340917 also helped me with this issue. I no longer get this error.

Try this To download and install this update, go to Settings > Update & Security > Windows Update and select Check for updates .

[jonevancook]

@Plextreme_Infinity

KB4340917

My Plex Server (Win 10) suddenly had this problem yesterday after months with no major issues. Installing KB4340917 seems to have solved my problem today.

[mal68]

After just upgrading to 1.13.5.5291 on Synology I am now getting this issue, I don’t suppose anyone knows of a solution for a Synology server?

[humanoid]

I am now experiencing the same issue on v1.13.5.5291.

[LunarRyuu]

Hello this is the secondPlex Media Server Logs_2018-08-12_01-05-35.zip (3.0 MB)
time i’m actually posting cause i’m getting this Conversion error a lot lately with different videos i have sometime I’d just wait it out and the video would work but i’m getting really tired of this error. I’ve waited patiently for solutions beside going back to older versions. and all of them kept pointing to “wait for an update” well i updated and I’m still getting this. i remember 4-5 months ago I never even saw this in the whole 2 years I’ve been using plex, not once. Now I’m having this issue left and right with different videos. And so here are my logs please fix because i love plex and what it does but this is frustrating that i cant even watch 1 min of a video with out this popping up.

[Nostromo21]

Oh dear, where do I begin. When this started happening a month or so ago I spent hours trying to get it sorted for my wife & I. I’m running my Plex server on Win 10 64-bit & we have 2 android phones (Samsung S5 & S7) which had the latest Plex client on them. I tried to revert back to even older versions I had stashed away (which I did prior to that anyway, due to the new disaster of a UI that was released), to get things stabilised. Everything seemed ok-ish for a month or so. Now the magic transcoding errors are back…

I accept that this could be entirely Microsoft’s fault with their last/latest release causing these errors due to some extremely obscure incompatibility which the Plex team couldn’t track down quickly. But as the above poster said, it’s now been months & returning to this thread I see that this major issue still hasn’t been sorted, not only that, but it’s now crept back into older versions. If I wasn’t such a realist cynic I would start spouting conspiracy theories about now…

1. Is the new UI any better or has it been changed from that horrible update a few months back which pretty much destroyed everyone’s carefully managed library catalogues?
2. Is there any light at the end of this transcoding error tunnel? I’m almost tempted to re-update the server & android apps back to current version just to see if it alleviates this error for us. We would even find a way to live with the new UI if those went away.

Thanks everyone, but if this error doesn’t get fixed soon I may have to look at alternative media players that can transcode files, like so many others unfortunately…