File name too long to delete/rename on Server 2012 R2 platform

I had a user name a file with a very long file name. Now we can't access the file. I have tried renaming and deleting it from the server but I just get an error that the file name is too long. It then suggests to move the file to a path with a shorter name. I can't. I can do nothing with this file.

What can be done to correct this problem?

Error Message
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

JohnBusiness Consultant (Owner)Commented:
Try deleting it with Unlocker.

I have used Unlocker to get rid of tough files.
You could also share the directory the file is in, then map a drive-letter to that share, and then rename or delete the file. After that just unmap the drive letter and unshare the directory.
You can connect via SMB to the server from a Mac and the Mac will let you delete it.
Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

Spike99On-Site IT TechnicianCommented:
The issue with long file names is not just the file's name: it's that the full path name is too long.  The full path to that file has probably exceeded the 255 character limit.  So, I would rename the containing folder or folders to something shorter.  Remove any spaces, shorten long words using abbreviations, etc.  Once you get the path short enough, you can shorten the name of the file.

Even if you map that location to a different drive letter, the actual path to the file is still just as long, so I don't believe that workaround will be effective.

I encountered this problem in a past job on several occasions.   Shortening the path to the file by renaming upper level folders always fixed it for us.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DahliaLadyAuthor Commented:
Thank you everyone for your quick comments. I'm going to work on this after hours tonight or tomorrow morning. I'll reply back with which option(s) worked best for our system.
deroodeSystems AdministratorCommented:
You can also move the directory the file is in to a place closer to the root of the filesystem. You cannot move the file itself, but you should be able to move the directory. That is how these long paths often get created in the first place.
DahliaLadyAuthor Commented:
Thank you everyone for you help. I appreciate it.

I was able to shorten the folder names and then delete the file.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.