15 pts.
Copy error
Mapped drives
Memory dump error
I am getting two dumps on the screen when copying files from a PC to the mapped drive on the server kept at datacenter. the DUMPS are 1. The network path is too deep 2. The network name no longer exist. I have checked the same thing on diffrent PC's in the same dippartment but one of the same two dumps I am getting. Please can any one suggest me or give me solution on this.

Answer Wiki

Thanks. We'll let you know when a new response is added.


Most insidiously, on network shares, drive letter mapped path that is shorter than 254 characters (e.g., H:\(longpath)\file.txt), but the file path on the server itself is longer than 254 characters (e.g., (blah blah servername)\(sharename)\(subsharename)\(longpath)\file.txt).

So now for the good stuff, here is what our problem was, it may help some of you, (no promises though). Just recently I noticed that 1 of our servers was changed to 100mb full duplex (found out also that this needs to be like this temporarily due to a network assessment) all of the pcs were at Auto. The problem was transferring to that particular server would give the error message, any other server was fine. I changed the PC’s to 10mb Half duplex and they worked just fine, slower than 100 of course but it is our temporary fix until it can be changed back to auto.
I agree with TPinky about the network cabling and pathway. Check that out to begin with. Another option to consider is fooling the application to a shorter path by using the old SUBST command. Here’s the syntax (it has to be run from a command window):

Associates a path with a drive letter.

SUBST [drive1: [drive2:]path]
SUBST drive1: /D

drive1: Specifies a virtual drive to which you want to assign a path.
[drive2:]path Specifies a physical drive and path you want to assign to
a virtual drive.
/D Deletes a substituted (virtual) drive.

Type SUBST with no parameters to display a list of current virtual drives.

Discuss This Question: 2  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Pressler2904
    LabNuke99 - Jeez... I haven't used the SUBST command in ages - good call, that should indeed work...
    2,190 pointsBadges:
  • Labnuke99
    :) the command line is still indeed a useful too! Go figure that MS has gone back to it with their Powershell scripting.
    32,960 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: