Link to home
Start Free TrialLog in
Avatar of paulCardiff
paulCardiff

asked on

xcopy: file creation error- the parameter is incorrect

hi

i'm trying to copy a rar file from a server to another server on the network (internal address)

when i try, i get the above error
i use a simple xcopy c:\rar\file.rar \\192.168.2.2\backup\file.rar

i've tried playing with switches etc but no joy

i can browse to the network path fine.

SOLUTION
Avatar of Richard Cole
Richard Cole
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of paulCardiff
paulCardiff

ASKER

I can create a file on the network drive no problem

when i try the NET USE command, i get:
system error 67 has occurred
The network name cannot be found

(i dont have and L drive)

Could you confirm "backup" is a shared folder on 192.168.2.2 ?

Try this :

NET USE \\192.168.2.2 password_administrator /USER:administrator
NET USE L:\ \\192.168.2.2\backup\
MKDIR L:\test

Regards.
backup is shared

the first command completed successfully, however, i get same error on 2nd command

system error 67 has occurred
The network name cannot be found
Have you response by running "ping 192.168.2.2" ?
remove the \ after the drive letter.

so net use l: \\192.168.2.2\backup\
Bad mistake, you right tricky98 !
i've removed the \ after the drive letter and i'm still getting the same error
And the ping ?
figured out that issue, the trailing forward slash

net use l: \\192.168.2.2\backup


that works
now when i try to mkdir l:\test i get access denied
ping times out, but that could be firewall

if i browse to it, i can see it
What is the firewall(s) and OS of both peer ?
You don't use the same protocol with windows explorer and DOS.

Regards.
script is running on a windows 2003 server
and copying to xp pro machine

xp pro is running windows firewall and kaspersky
OK. Disable both and try to confirm it's a basic firewall problem.

Regards.
try mapping the drive from windows explorer and then, if successful try the copy.
I mapped the drive and now get
file creation error - the parameter is incorrect

i've turned off firewalls and disabled all anti virus!

surely this shouldn't be difficult
Could you create a file or a folder with the windows explorer ?
>Could you create a file or a folder with the windows explorer ?

yep, new file and new folder, not a problem
Open command line :
Type :
L:
MKDIR myfolder

What happen ?
that worked

seems there is a problem with the xcopy command
Try to copy...
COPY c:\rar\file.rar L:\
ok, this is weird, i tried the same command with a txt file, and it copied fine!
i then tried with a new rar file......that also worked

however, when i try to copy a 9gig rar file is keeps bailing!

any ideas?
i've tried the same command one with
XCOPY
and one with
COPY

XCOPY says about the file creation error

COPY says "the parameter is incorrect"

file.rar is not a file ?
Try echo blabla > L:\blabla.txt

Regards.
If you drag and drop it with explorer, do you get an error?
both blabla through CMD window, and drag and drop with explorer work
For me a final test :
echo blabla > blabla2.txt
copy blabla2.txt L:\blabla2.txt
If it worked your problem is "file.rar"
yes that worked

however, there doesn't seem to be an issue with the rar file
i also tried it with a different file (the .BFK that i rar'd) and that failed too

the rar file is now 3 gig, and the BKF file is 8 gig
is there an issue with copying large file as it seems related to this?
You may use robocopy for "huge" files

robocopy c:\rar L:\

This will copy full content of rar folder to L:\

without create network drive :
robocopy c:\rar \\192.168.2.2\backup\

Regards.
do I need to install anything as it doesn't recognise robocopy?
see http://en.wikipedia.org/wiki/Robocopy

It's on the resource kit...