Thanks,
I ran the subinacl command and I've only got 10 or 12 files that won't cooperate now. It took me a while to figure out that I had an older version of the subinacl application and the old version uses different commands to execute. Other than that it works great. One question that I will find that answer to shortly is, when you take ownership does the file or folder reset the permissions on that file or folder or does subinacl have some way of preventing this from happening? Thanks, Josh From: James Rankin [mailto:[email protected]] Sent: Thursday, January 29, 2009 12:37 PM To: NT System Admin Issues Subject: Re: Copy files error I used to see that on and off when I worked for an outsourcer. Could be a permissions or ownership error if I remember rightly. I used to use subinacl.exe to take ownership of "dodgy" file structures before hitting it with robocopy, and sometimes used to blast Administrators:Full Control down it as well for good measure. 2009/1/29 <[email protected]> I am in the process of moving all files from a data drive on a server 2003 standard machine. I am using robocopy /s /e /v /sec /w:0 /r:0 /log:c:\robocopy to copy the files. This is the error I get (about 11,850 of them) New File 8938 ._9073-12.jpg 2009/01/28 09:24:56 ERROR 123 (0x0000007B) Creating Destination Directory X:\Data\Media\~Photos\Drop Files Here\IMB Portraits Archive \ The filename, directory name, or volume label syntax is incorrect. If I go to the individual files or folders where I received this error from and right click them and go to properties I get this. (folder) (file) I know these are files created by Macs. If I try to copy the files or folder manually I get this. I did a chkdsk /f on the server and I also checked the consistency of the Raid 5. Any suggestions? I don't really want to manually move all 11,850 files and folders and reassign NTFS permissions... Thanks, Josh ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
<<image001.png>>
<<image002.png>>
<<image003.png>>
