Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Roaming profiles and 'cannot copy file due to filename or extension is too long'?

Posted on 2010-11-22
2
Medium Priority
?
2,666 Views
Last Modified: 2012-05-10
We have a Windows 2008 R2 file server, and our clients are Windows 7 machines mostly. They are all in the same domain. I've noticed that an user has trouble with his roaming profile due to the filename or extension of files synced being too long. And this isn't exactly the first time either.

User Profile General - Event id 1509:

"Windows cannot copy file \\Synsrv1$NOCSC$\Synocus Users\KenI\Profile.V2\Documents\Visual Studio 2010\Projects\EmployeesVisualWebPart1\EmployeesVisualWebPart1\pkg\Debug\EmployeesVisualWebPart1\CONTROLTEMPLATES\EmployeesVisualWebPart1\EmployeesVisualWebPart\EmployeesVisualWebPartUserControl.ascx to location C:\Users\KenI\Documents\Visual Studio 2010\Projects\EmployeesVisualWebPart1\EmployeesVisualWebPart1\pkg\Debug\EmployeesVisualWebPart1\CONTROLTEMPLATES\EmployeesVisualWebPart1\EmployeesVisualWebPart\EmployeesVisualWebPartUserControl.ascx. This error may be caused by network problems or insufficient security rights.

 DETAIL - The filename or extension is too long."

I've checked for the file on our file server, and it's simply not there. Apparently it has never been synced to the file server, probably due to the filename or extension being too long.

The solution, as presented in a similar thread (http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2000_Server/Q_22600828.html), is to create a new profile and copy all important content. Alright, that's doable...

However, I'm not looking for the quick fix, but rather to the cause of this issue. Is there any way to get rid of the 'filename or extension is too long' bug in the first place? As we cannot control the folders each application creates, I'm hoping to find a way to be able to copy long filenames and extensions.
0
Comment
Question by:Synocus
2 Comments
 

Author Comment

by:Synocus
ID: 34188185
Confirmed, the troublesome long filename files were never synced to the file server, and from that point on the profile sychronization started failing, and as the files were never removed they effectively made the user to keep running a profile that's stored locally only.

How can we prevent this issue from repeating?
0
 
LVL 38

Accepted Solution

by:
Hypercat (Deb) earned 2000 total points
ID: 34192051
This is a limitation of every operating system that Microsoft has ever produced. It's not a "bug" but built into the design of the OS that the maximum path length is 255 characters. The problem is that the roaming profile location adds "\\synsrv$NOCSC$\Synocus Users\" to the path so that the final result is a path that is too long to be read by the OS. I have seen this happen numerous times and as far as I know there is no fix for it simply because it's not something that can be "fixed." The only other suggestion I could think of would be to somehow limit the original path to a shorter one. It seems like a very long and convoluted path in the first place, but I'm not familiar with Visual Studio so I don't know if changing that path perhaps through preferences within the application would be a possibility.
0

Featured Post

Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

How to deal with a specific error when using the Enable-RemoteMailbox cmdlet to create a mailbox in the cloud-based service, for an existing user in an on-premises Active Directory.
Transferring FSMO roles is done when an admin wants to split roles between certain Domain Controllers or the Domain Controller holding the Roles has been forcefully demoted using dcpromo / forceremoval
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…
Suggested Courses

926 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question