File name too lng when saving to a network drive

[AnnDroyd]

We've been sporadically receiving an error message saying the path or filename is too long when some staff try to save to a network drive.

 

Further investigation shows it happens on some computers and not others, despite the same user being logged on.

 

All staff in question have the same permissions, and the computers are all of identical build with the possible exception of different windows updates.

 

Has anyone come across this before and found a solution?

[CHR1S]

I know this is the most obvious thing, but is the file name too big??

[somabc]

I had the exact same thing yesterday!

 

This is how we solved it - http://support.microsoft.com/default.aspx?scid=kb;en-us;817861&Product=winxp

 

To work around this behavior, click to clear the Launch folder windows in a separate process check box. To do this, follow these steps:

Right-click Start, and then click Explore.

In Windows Explorer, click Tools, and then click Folder Options.

In the Folder Options dialog box, click the View tab.

Under Advanced settings, click to clear the Launch folder windows in a separate process check box, and then click OK

 

You can also get a Hotfix from Microsoft.

Edited June 24, 2010 by somabc

[sted]

I know this is the most obvious thing, but is the file name too big??

 

and if not on teh mapped drive is it too long on the real drive so r:\myfile is short but that may be d:\dfs\users\staff\slt\myname\myfile and be getting long that way

[Polski]

256 rings a bell somewhere. The further down the tree you start, the less you have to use.

 

Feel free to correct me if I am wrong, I usually am!

[somabc]

It is 248 for UNC paths.

[tarquel]

also, I've seen in the past where the user has managed to save the file with the path long, but not too long, and then in their profile, the Recent folder entry makes the path go over the limit and cause them logon problems with their profile.

 

So something to be wary of there too

 

Nath

[farquea]

ive got a similar problem where students have deliberatly created new folder inside new folder inside new folder and so on so that i now cant delete it because the path is too long and when you drill down the folder structure windows gets so far then even though it shows there is another folder, wont let you click in it.

 

Any ideas how i can delete these folders?

[3s-gtech]

Yup, just rename the folders further up the tree with a single character, it'll let you access and delete them then.

[AnnDroyd]

I know this is the most obvious thing, but is the file name too big??

 

No, the file name is not too long. It's only about 50 characters including the full path. Anyway, when the same user logs on to a different computer and tries the same thing, it works fine.

 

I've tried to download the hotfix suggested by somabc, but the page is no longer there. Does anyone know where this fix can be found?

[sted]

drive mapping map it part way down then delete the kill the drive map and delete further up

[AnnDroyd]

Just to clarify, this problem is not caused by the filename or path being too long. The total lenth of the path and filename is around 50 characters. Furthermore, if the same person logs onto a different computer with the same mapped drives and filenames, the problem goes away. I don't know what the problem is, but we've narrowed it down to a problem with the actual computer/laptop.

[birchanger]

I just create a share some way down the path then delete the offending filed/folders via the share.

[somabc]

Just to clarify, this problem is not caused by the filename or path being too long. The total lenth of the path and filename is around 50 characters. Furthermore, if the same person logs onto a different computer with the same mapped drives and filenames, the problem goes away. I don't know what the problem is, but we've narrowed it down to a problem with the actual computer/laptop.

 

 

Have you checked if Launch folder windows in a separate process is turned on?

[AnnDroyd]

Have you checked if Launch folder windows in a separate process is turned on?

 

No I haven't. Could that cause this problem? I'll have a look on Monday morning and see what happens.

[ajs]

No I haven't. Could that cause this problem? I'll have a look on Monday morning and see what happens.

 

I encountered the same issue on a newly built machine on Friday and clearing the checkbox for the "Launch folder windows in a separate process" made it go away.

 

If that doesn't help then let me know and I'll dig out a URL I've got that you can use to request hotfixes from MS without having to go through the phone line (that is assuming it still works of course).