Why the copy activity hangs and refuses to copy to new folder?

[blitz92]

I issued a copy command to copy an existing folder with files (using win xp pro workstation) to a new folder on the same Windows 2003 Server. The copy activity starts for a few minutes and the copy activity hangs and refuses to copy the remaininf files into the new folder. It hangs for several minutes and gives me an error - "...path too deep"!

Platform: Windows 2003 Server
Workstation: Win Xp pro
Activity: Select all, then copy the whole folder to a new destination folder.

Please help!!!!

 

[crobin1]

You actually can have a path that is too long for some things in Windows to handle. This Microsoft KB article might help:

http://support.microsoft.com/kb/320081/en-us

 

[blitz92]

Thanks crobin1!

My dilema is that I have another Windows 2000 server that handles the same folder copy function just fine. But this new Win 2003 server can't copy the same folder (as was done by the w2k server). I am wondering if there is a problem with the configurations for my win 2003 server.

Example: w2k server ===> adapter properties ===> tcp/ip ==> wins ==> checked Enable LMHost and Use netbios setting

Win 2003 server ===> enable netbios over tcp/ip

 

[crobin1]

Are you saying that if you have the same folder on Windows 2000 and initiate the copy from Windows XP it works? Or are you saying you have the folder on Windows 2003 and initiate the copy from Windows 2000 it works? The "path too deep" message would be coming from the client that initiated the copy. Have you tried doing the copy directly on the Windows 2003 server itself (logged on the console)?

 

[blitz92]

Yes, I am saying that I have the same folder on Windows 2000 server and when I initiate the copy from Windows XP pro workstation, it works just fine. When I have the same folder on Windows 2003 server and initiate the copy from the same Windows XP pro workstation, it fails and gives me the error: "path too deep". When I tried doing the copy directly on the Windows 2003 server itself (logged on the console), it works. The problem is that my users do not have access to copy directly on the Windows 2003 server itself (i.e. logged on the console). They can only map to the Windows 2003 server and work from there.