ERROR : The specified path, file name, or both are too long

General Support / Questions
#1

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)

#2

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

#3

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 name must be less than 248 characters.

I have fixed (I think) the suggested fix with registry changes.
Still getting the error,

This is new and happening the last month or so.

THis is an example of a very long title
\192.168.1.77\Media\tv\FINISHED\Murder in the Outback the Falconio and Lees Mystery\Murder in the Outback the Falconio and Lees Mystery - S01E01-02 - Episode 1 + Episode 2.mp4

And is Only 176 characters…

Dragging into buddy desktop seems to work !

Any suggestions?

#4

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 and the length of the path sorted by longest to shortest.
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

#5

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

#6

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.168.1.77\Media\tv" -Recurse -Force | Select-Object -Property FullName, @{Name = "FullNameLength"; Expression = { ($_.FullName.Length) } } | Sort-Object -Property FullNameLength -Descending | Export-Csv -Path "\\192.168.1.77\Media\tv\PathLength.csv" -NoTypeInformation

1 Like
#7

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.

#8

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.

#9

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 MCE started pulling in my conversions.

1 Like
#10

This has been resolved here:

2 Likes