A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows XP » Networking and the Internet with Windows XP
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

New fact about "path is too deep"



 
 
Thread Tools Display Modes
  #1  
Old November 24th 09, 06:02 PM posted to microsoft.public.windowsxp.network_web
Quadibloc
external usenet poster
 
Posts: 2
Default 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
Ads
  #2  
Old November 24th 09, 06:47 PM posted to microsoft.public.windowsxp.network_web
John John - MVP[_2_]
external usenet poster
 
Posts: 1,637
Default 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

  #3  
Old November 24th 09, 06:47 PM posted to microsoft.public.windowsxp.network_web
John John - MVP[_2_]
external usenet poster
 
Posts: 1,637
Default 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

  #4  
Old November 25th 09, 07:47 AM posted to microsoft.public.windowsxp.network_web
Anteaus
external usenet poster
 
Posts: 1,331
Default 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
.

  #5  
Old November 25th 09, 07:47 AM posted to microsoft.public.windowsxp.network_web
Anteaus
external usenet poster
 
Posts: 1,331
Default 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
.

  #6  
Old January 30th 12, 11:39 PM posted to microsoft.public.windowsxp.network_web
adamgrat
external usenet poster
 
Posts: 1
Default 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
  #7  
Old September 26th 15, 11:49 AM posted to microsoft.public.windowsxp.network_web
No_Name
external usenet poster
 
Posts: 1
Default New fact about "path is too deep"

Have you tried software called Long Path Tool, it is absolute solution for such kind of errors.
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off






All times are GMT +1. The time now is 06:22 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright 2004-2017 PCbanter.
The comments are property of their posters.