New fact about "path is too deep"
I've been attempting to copy files to a directory on the network,
using Windows Explorer from Windows XP Professional, and have been having problems. I kept getting either the "the path is too deep" error, or the "the network name is no longer available" error. The file whose copying was claimed to have failed due to the error always had actually been copied. As a workaround, I tried mapping the network destination to a drive letter, and using XCOPY from the command window. I still ended up with an error, but that error was: "File creation error - The semaphore timeout period has expired." It is possible that this is a better error message, and identifies the actual underlying issue. John Savard |
New fact about "path is too deep"
Most likely a hardware problem.
Try: http://support.microsoft.com/kb/325487 Advanced network adapter troubleshooting for Windows workstations http://www.chicagotech.net/winissues/pathtoolong.htm Path is too long or deep http://alexpb.com/notes/articles/200...error-message/ Notes » Blog Archive » Path Too Deep Error Message John Quadibloc wrote: I've been attempting to copy files to a directory on the network, using Windows Explorer from Windows XP Professional, and have been having problems. I kept getting either the "the path is too deep" error, or the "the network name is no longer available" error. The file whose copying was claimed to have failed due to the error always had actually been copied. As a workaround, I tried mapping the network destination to a drive letter, and using XCOPY from the command window. I still ended up with an error, but that error was: "File creation error - The semaphore timeout period has expired." It is possible that this is a better error message, and identifies the actual underlying issue. John Savard |
New fact about "path is too deep"
Most likely a hardware problem.
Try: http://support.microsoft.com/kb/325487 Advanced network adapter troubleshooting for Windows workstations http://www.chicagotech.net/winissues/pathtoolong.htm Path is too long or deep http://alexpb.com/notes/articles/200...error-message/ Notes » Blog Archive » Path Too Deep Error Message John Quadibloc wrote: I've been attempting to copy files to a directory on the network, using Windows Explorer from Windows XP Professional, and have been having problems. I kept getting either the "the path is too deep" error, or the "the network name is no longer available" error. The file whose copying was claimed to have failed due to the error always had actually been copied. As a workaround, I tried mapping the network destination to a drive letter, and using XCOPY from the command window. I still ended up with an error, but that error was: "File creation error - The semaphore timeout period has expired." It is possible that this is a better error message, and identifies the actual underlying issue. John Savard |
New fact about "path is too deep"
'Path too deep' normally arises when someone uses Explorer to move one folder inside another. Explorer has no checks for path-length violations in these circumstances. Though, your problem sounds more like this: http://mylogon.net/support/psave "Quadibloc" wrote: I've been attempting to copy files to a directory on the network, using Windows Explorer from Windows XP Professional, and have been having problems. I kept getting either the "the path is too deep" error, or the "the network name is no longer available" error. The file whose copying was claimed to have failed due to the error always had actually been copied. As a workaround, I tried mapping the network destination to a drive letter, and using XCOPY from the command window. I still ended up with an error, but that error was: "File creation error - The semaphore timeout period has expired." It is possible that this is a better error message, and identifies the actual underlying issue. John Savard . |
New fact about "path is too deep"
'Path too deep' normally arises when someone uses Explorer to move one folder inside another. Explorer has no checks for path-length violations in these circumstances. Though, your problem sounds more like this: http://mylogon.net/support/psave "Quadibloc" wrote: I've been attempting to copy files to a directory on the network, using Windows Explorer from Windows XP Professional, and have been having problems. I kept getting either the "the path is too deep" error, or the "the network name is no longer available" error. The file whose copying was claimed to have failed due to the error always had actually been copied. As a workaround, I tried mapping the network destination to a drive letter, and using XCOPY from the command window. I still ended up with an error, but that error was: "File creation error - The semaphore timeout period has expired." It is possible that this is a better error message, and identifies the actual underlying issue. John Savard . |
New fact about "path is too deep"
Quadibloc wrote on 11/24/2009 13:02 ET :
I've been attempting to copy files to a directory on the network, using Windows Explorer from Windows XP Professional, and have been having problems. I kept getting either the "the path is too deep" error, or the "the network name is no longer available" error. The file whose copying was claimed to have failed due to the error always had actually been copied. As a workaround, I tried mapping the network destination to a drive letter, and using XCOPY from the command window. I still ended up with an error, but that error was: "File creation error - The semaphore timeout period has expired." It is possible that this is a better error message, and identifies the actual underlying issue. John Savard i have the same problem and i use longpathtool and my problem is solved |
New fact about "path is too deep"
Have you tried software called Long Path Tool, it is absolute solution for such kind of errors.
|
All times are GMT +1. The time now is 10:06 PM. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright © 2004 - 2006 PCbanter
Comments are property of their posters