[Bug] PeekNamedPipe failed: 0x6d when detecting intros

Server Version#: 1.23.0.4459
Player Version#: Doesn’t matter

Intro detection seems to be broken since a day (log attached)

Things tried to resolve it:

  • Reinstalling PMS

  • Rolling back to previous 2 PMS

  • Completely uninstalling PMS and rebuilding all library metadata.

Nothing seems to be working for me for some reason. It gives PeekNamedPipe failed: 0x6d
error as soon as it gets to fetch the intros, so I suspect it could be a database error or something else and not related to the PMS.

This is the snapshot of the logs for the error. Please let me know if I can provide anything else to resolve it. Intro detection is my favourite feature:

May 01, 2021 10:31:09.525 [6900] Debug — Completed: [127.0.0.1:1444] 200 GET /status/sessions/background (5 live) GZIP 0ms 397 bytes (pipelined: 101)
May 01, 2021 10:31:09.527 [3156] Debug — [JobRunner] Jobs: Starting child process with pid 5156
May 01, 2021 10:31:09.545 [16460] Debug — Jobs: 'C:\Program Files (x86)\Plex\Plex Media Server\Plex Media Fingerprinter.exe' exit code for process 5156 is -1073741515 ()
May 01, 2021 10:31:09.558 [3156] Error — PeekNamedPipe failed: 0x6d
May 01, 2021 10:31:09.563 [3156] Debug — Activity: updated activity a0981ffb-dbe8-4ea7-a409-1c78d03b35fa - completed 85.0% - Detecting intros
May 01, 2021 10:31:09.563 [3156] Debug — Activity: updated activity a0981ffb-dbe8-4ea7-a409-1c78d03b35fa - completed 85.0% - Detecting intros
May 01, 2021 10:31:09.564 [3156] Debug — Activity: updated activity a0981ffb-dbe8-4ea7-a409-1c78d03b35fa - completed 95.0% - Detecting intros
May 01, 2021 10:31:09.564 [3156] Debug — Activity: ended sub-activity f1567b63-5789-4518-a77c-5dfdc12e1019 parent: a0981ffb-dbe8-4ea7-a409-1c78d03b35fa overall progress: 100.0% (1/1)
May 01, 2021 10:31:09.564 [3156] Debug — Activity: updated activity a0981ffb-dbe8-4ea7-a409-1c78d03b35fa - completed 100.0% - Detecting intros
May 01, 2021 10:31:09.564 [3156] Debug — Activity: Ended activity a0981ffb-dbe8-4ea7-a409-1c78d03b35fa.

Somebody else mentioned a similar symptom - also on Windows.

Yes, that seems like the exact same issue as me. The XML won’t be updated obviously because the process itself failed to extract the intro metadata.

Just to clear some points, since I rebuilt the entire library I can ensure that even for shows and episodes that previously had intro metadata don’t have now and can’t generate it either. So it’s definitely an issue.

I’m having the same issue.

1 Like

Same issue also with Windows and Version 1.23.0.4459 of Plex (Beta). Is this fixable or do we have to wait for Plex to release a new version with a fix?

1 Like

Another issue that relates to the same thing:

It seems like the executable fingerprinter.exe isn’t compiled properly in the last two releases. This is definitely a bug and will need to be fixed in the next release. Nothing we can do about it.

I hope someone from the Plex dev team notices this. @ChuckPa , can someone look into this please?

I’ve been able to confirm this bug. We are looking into it. Thanks for the reports.

3 Likes

Updated to PMS version 1.23.0.4480. Unfortunately, still, the issue isn’t fixed.

Try 1.23.0.4482: Plex Media Server - #426 by gbooker02

1 Like

Yes, this seems to be working. Intros are getting detected and put in the XML. Also can’t see any Error log in the logs during Analyze.

Thanks for the prompt fix!

This is a continuation of this thread which was closed.

Can anyone confirm if 4482 fixes the fingerprinter crash?

Yes, as I mentioned above the issue is solved. Detecting intros triggers fingerprinter.exe and doesn’t show any error now.

1 Like

Hi I have updated my PMS to 4482 and still getting the error

PLEX_crsh.txt (2.1 KB)

@Tychi Please provide your PMS logs so we can check the error there.

Thank you - as requested > Plex Media Server Logs_2021-05-07_08-55-12.zip (2.6 MB)

Your logs show that intro detection worked without any errors. It also performed the video preview generation without errors. I see a few curl errors but that’s not related to this issue.

Exactly what errors are you seeing and when does it occur?

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.