UNC Path not working following update to 1.32.0.6918

Server Version#: 1.32.0.6918
Player (Plex Web) Version#: 4.104.2

Steps to reproduce…

  1. Add a new file to an existing library. This library is configured to use a UNC path e.g. \FUBAR\Media\Music
  2. Select ‘Scan Files’ for the library
  3. If ‘automtically empty trash’ is turned on, the entire collection disappears, otherwise the item shows a big red trashcan and is marked as ‘unavailable’.
  4. Edit the library and add a new folder with UNC path
  5. Select ‘Scan Files’ for the library
  6. Library remains empty
  7. Edit the library and add a new local folder path
  8. Select ‘Scan Files’ for the library
  9. Items now appear in the library for the local folder items.

Expected…
Files that have previously been added from a UNC path should continue to be recognised.

Plex Media Server Logs_2023-04-07_20-56-37.zip (1.2 MB)

Good evening.
I have tried a few alternatives.
o Added a new UNC share and tried to scan that
o Added a drive mapping M: and tried to scan that

both failed with the following error logged:
Filesystem error (boost::filesystem::directory_iterator::construct: The system call level is not correct [system:124]: “\XXXX\Media\Music”) during scanning: 124 in “\XXXX\Media\Music”

Please note that I am running Plex stand alone using Plex Media Service.

Thanks!
Clear Filters and Jump to Context

Your log files are unfortunately not usable.
You need to enable “debug” logging.
(Do NOT enable “verbose” logging!)

Then stop and restart Plex server.
Repeat the scanning attempt, then fetch server logs again, please.

Sorry, I’m having difficulty understanding what you mean with this.

Thanks for taking the time to reply.

Sorry for my cryptic comment below…

To clarify, I am running Plex as a service using the ‘Plex Media Service’. This allows me to run on a headless windows box without logging in.

I resolved my issue by rolling back to version 1.31.3.6868. The UNC path scanning works on this version. Additionally, scanning mapped drive via plex web UI (when editing a library) also works on this version. Attempting to browse a mapped folder in this fashion on version 1.32.0.6918 would fail with an error message.

If no-one else has raised this issue hopefully it was a fluke… if it reoccurs upon upgrading to the next updated version I will repost debug logs.

Thanks again.

If you mean this one: PMS as a service
This is a 3rd-party tool and not officially supported.
Did you think of updating the tool itself? It definitely needs an update to be able to handle the 64 bit versions of Plex Server.

Hi

I use PMS As a Service on my windows 10 PC. On that machine I am also running Plex Media Server 1.32.0.6918-6f393eda1

I did not get your error

Apr 07, 2023 16:16:07.303 [9760] WARN - Filesystem error (boost::filesystem::directory_iterator::construct: The system call level is not correct [system:124]: "\\ios\media\music2") during scanning: 124 in "\\ios\media\music2"

Could you please go back to the failing version and do a simple test with one library but have Micorsoft SystemInternals Process Monitor running at the time and run Plex Media Server with both Verbose and Debug logging enabled

and please start the procmon capture just before starting the scan and and stop it soon after you get the error

I would like to see what procmon logs when the boost::filesystem error is generated

Please save the procmon capture as a PML file, zip it and and upload to google drive / dropbox etc and send me and @OttoKerner link by Private Message and please also ensure server verbose and debug logging is enabled beforehand - do that before you relaunch Plex Media Server for the test and include the zipped server logs as well

Thanks

This shows my test which runs PMS non-interactively using the service

Apr 11, 2023 04:47:40.186 [9564] INFO - Plex Media Server v1.32.0.6918-6f393eda1 - Microsoft PC x64-x64 - build: windows-x86_64 windows - GMT 01:00
Apr 11, 2023 04:47:40.186 [9564] INFO - Windows version: 10.0 (Build 19045), language en-GB
Apr 11, 2023 04:47:40.186 [9564] INFO - 4 3398 MHz processor(s): Architecture=9, Level=6, Revision=15363 Processor Identifier=Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
Apr 11, 2023 04:47:40.186 [9564] DEBUG - System Memory 15.94GB
Apr 11, 2023 04:47:40.186 [9564] INFO - Compiler is - MSVC 1929
Apr 11, 2023 04:47:40.187 [9564] DEBUG - "C:\Program Files\Plex\Plex Media Server\Plex Media Server.exe" -noninteractive
Apr 11, 2023 10:12:17.574 [15328] INFO - Notification: Scanning the "TestMusicUNC" section -
Apr 11, 2023 10:12:17.574 [15328] DEBUG - Scanning section 65

Apr 11, 2023 10:12:17.592 [15328] DEBUG - Scanning TestMusicUNC using en(Plex Music) with 44 current media items and 3 section locations in the database.

Apr 11, 2023 10:12:17.592 [15328] DEBUG -   * Scanning \\mycloudpr4100\plextesttv1\TestNASMedia2\Music3

Apr 11, 2023 10:12:18.799 [15328] DEBUG -   * Scanning \\MYCLOUDPR4100\plextesttv1\TestNASMedia2\Music2

Apr 11, 2023 10:12:19.537 [15328] DEBUG -   * Scanning \\MYCLOUDPR4100\plextesttv1\TestNASMedia2\Music

Apr 11, 2023 10:12:20.284 [15328] INFO - Notification: Library scan complete - Extra information may still be downloading from the Internet

I am running the latest release of PMS as a Service Releases · cjmurph/PmsService · GitHub

Please remove verbose logging setting after doing the test to capture the diags

Hi,
i dont think that the problem is UNC because i have the same issue and i dont use UNC link.
I have symlinked 2 local drive (F and G) to C: drive to c:\SYMLINK. the resulat is that plex take C:\SYMLINK to browse the content but i have the same issue anyway…

Its strange because when i replace database files by a backup (exactly the same files size), the content come back but when i try to scan new content, content dissapear.

Ho we can rollback version without losing configurations?
I have try to execute EXE file from 1.31 but plex refuse to install.
thanks

All you need to do is:

  • Stop/quit/end Plex Server with the tray icon
  • deinstall Plex Server with the regular ‘Apps’ control panel of Windows
    (do not use 3rd party ‘Uninstaller’ software like Revo etc.
    do not use “Registry Cleaner/optimizer” software like CCleaner et al)
  • for safety, reboot Windows
  • download the installation exe of the older version and install it

(If you want to install an older version of PMS, take a look into %LOCALAPPDATA%\Plex Media Server\Updates)

1 Like

@Andrew_and_Ingrid I updated my earlier post to ask for both verbose and debug logging enabled - to go with the procmon capture

My tests were actually using the 64-bit windows build of Plex Media Server - may be there is an issue with boost and the 32-bit build of Plex Media Server.

What happened to the allegedly security feature that do not delete your whole library if the path is not available? This shows me I did correct by never activating the automatic empty trash option.

@Andrew_and_Ingrid I tested with the 32-bit build (not running PMS As Service on this machine) and my music library scan with unc paths was ok

So waiting for diagnostics from you to look further into the issue

Usage of Symlinks will disable this security feature.

I have just tested x64, doesn’t change anything.

I have:

  • restore database

  • uninstall plex

  • reinstall 1.31 x86 (everything work fine)

  • Upgrade to 1.31 x64 (everything work fine)

  • Update to 1.32 x64. (Broken, issue come back)

Thanks for trying. I have been unable to reproduce the error.

Waiting for debug + verbose logging server logs plus Process Monitor - Sysinternals | Microsoft Learn capture zipped PML file for the time of the error

I was told to post here, as I’m having similar problems with accessing network drives, like a NAS on my Plex, especially when it comes time to scan a new video in or something.

Folders1
Folders2

I’ve tried mapping the drive, I’ve tried UNC, both methods don’t work, but if I just throw a random video file on the C: drive and tell Plex to scan that folder, it’s totally fine.

As you can see from my images, it’s blind to anything in the V: (or S: drive), but when I rolled it back to the “Public” release, rather than the Beta, it’s back to normal and can scan folders again.

1 Like

Those of you who are using file shares: can you determine which version of the SMB/CIFS protocol is used by the file server?
If the file shares are supplied by a Windows machine, it is most likely SMB2 or SMB3.
But you are using some Linux powered appliance like NAS boxes, or routers, or similar stuff, it might still be SMB1.

(Windows 11 even removed support for SMB1 by default, as it is considered unsafe.)

I have the very same issue. The images that iTrooper posted is representative of what I saw as well. Any directly attached storage continued to allow for scanning for new content. Network storage (I have an older synology NAS box) would show without directories and not allow you to browse or scan for new media. Having said that, media that was already scanned (even on the NAS) would still play. I’m running Windows 11.

I have rolled back to the previous version and everything works again.

If your NAS device allows for selection of a higher SMB protocol version, please check if it’s currently set to SMBv1. If it is, try and raise that to at least SMBv2.