I am getting this error ERROR : The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. A lot. mcebuddy.log (555.3 KB)

Try Get-ChildItem -Path "\\192.168.1.77\Media\tv" -Recurse -Force | Select-Object -Property FullName, @{Name = "FullNameLength"; Expression = { ($_.FullName.Length) } } | Sort-Object -Property FullNameLength -Descending | Format-List or to have it output to a CSV file Get-ChildItem -Path "\\192.1…

The path including the file of a path you are monitoring is too long. Take a look at Monitoring Subdirectories - #8 by kellynewman post.

Greetings. ERROR> 2021-01-06T10:15:13 MCEBuddy.Engine.QueueManager --> Unable to search for files in location \192.168.1.77\Media\tv for monitor task TV ERROR : The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory na…

I can’t think of anything else to try. I wasn’t even sure if the registry update would work. Are there any other files in the monitor location that might still be exceeding the 260 character limit? Try running the following in an Admin Powershell to output the path to everything under the folder …

Hi Tried that and appears not to show the full length and MP4 files look to be cut short. [image]

Yep That worked . Thanks for the scripts it found one over 260 and another over 248 - both now amended. Looks like that fixed buddy’s error.

It does appear to be a bug that if any file in a monitor location exceeds the 260 limit that no files are processed. I recommend submitting a bug report stating as such so this won’t be an issue for others.

Thank you so much for posting this. I’ve been struggling with this the past week or so. I didn’t realize that there was a bug that stumbled if ANY file path is too long. I modified the above script to suit my file location and ran it revealing the offending files, deleted them, and immediately MC…

This has been resolved here: [afbeelding] Long title name sticks buddy in a loop Bugs Fixed in today’s 2.5.6 BETA build. It’ll log an error for the problematic file/directory and move onto the next one.

FOUT: Het opgegeven pad, bestandsnaam of beide zijn te lang

Algemene Ondersteuning / Vragen

Goose (Goose) 19 januari 2021 om 18:17 10

Dit is hier opgelost:

Topic		Antwoorden	Weergaven
Monitoring Subdirectories General Support / Questions	7	1164	14 december 2020
QueueManager Long file names error General Support / Questions	5	1435	11 januari 2018
Long title name sticks buddy in a loop Bugs	2	712	19 januari 2021
Multiple Errors trying to convert Metadata and Renaming	4	946	27 maart 2019
Not scanning directory General Support / Questions	8	1166	14 april 2025

FOUT: Het opgegeven pad, bestandsnaam of beide zijn te lang

Gerelateerde topics