UNSOLVED

revcall1

updated

15 years ago

R

revcall1

27 Posts

1

9461

April 20th, 2012 06:00

Emcopy warnings and errors

I have recently run emcopy on a server share and copied it to our VNX5300 CIFS.  The command I used was:

E:\Operations\Apps>emcopy_v4.14.exe \\Server\operations \\Servertemp\Operation

s\ /o /s /d /sd /log:"c:\emcopy log2.txt"

It seemed to work well but I have received a large number of errors (24,000+).

I've listed the errors below and the definitions given using the "net helpmsg" command:

  • 1307  "This security ID may not be assigned as the owner of this object."
  • 1308  "This security ID may not be assigned as the primary group of an object."

How do I determine what the actual issue is and then go about resolving it?  The files in question copied and I can't tell if there is a difference in the security permissions on any given file. 

I also received a large number of "Warning: skipping the copy of file content (/sd).

After much searching, I cannot find a solution.  I am very grateful for the amount of knowledge the members of this community possess.  Any insight is greatly appreciated. 


  • dynamox

    11 Legend

    •

    20419 Posts

    •

    87439 Points

    2250

    0

    Posted April 20th, 2012 09:00

    if you look at source and targe permissions after the copy ..are ACLs the same ?

  • sthulin

    2 Intern

    •

    181 Posts

    2250

    0

    Posted April 20th, 2012 14:00

    you should look at the files in question and see what is set for SIDs on them.  Perhaps these are local sids to the original server and the users/groups were not copied over to the VNX first.

  • revcall1

    27 Posts

    2250

    0

    Posted May 2nd, 2012 13:00

    Many apologies for letting so much time go by.  An issue came up that caused me to put my migration on hold.

    It seems that correcting the 1307 error also corrects the 1308 error.  For the most part, I have been able to isolate orphaned SIDs on files or folders and then take ownership of them.  Last night I moved on to another share and seem to have quite a few 1308 errors but no 1307.  I'll have to figure out what's going on.  There are also a lot of 1337 errors which are:  "The security ID structure is invalid."  Why can't these errors be a little more clear?

  • bergec

    275 Posts

    2250

    0

    Posted May 3rd, 2012 05:00

    Error codes returned by EMCopy are standard Windows error codes

    You can run "net helpmsg 1308" from Windows command line to get more details

    Those codes correspond to unknown Sids in either owner, group or ACL of the object. Usually Sid is unknown because AD user was deleted or AD server is slow to respond (less likely)

    Claude

  • revcall1

    27 Posts

    2250

    0

    Posted July 31st, 2012 11:00

    Thanks Vince!

    We ended up buying Secure Copy by ScriptLogic.  It works flawlessly.  I simply didn't have the time to comb through the logs and try to figure out what was working and what wasn't.

    I'm sure your post will go a long way in helping others.

    Thanks again!!

  • VinceValenti

    1 Message

    2250

    4

    Posted July 31st, 2012 11:00

    Hi revcall, I'm guessing this issue has been resolved for you, but I wanted to post a reply here with our experience in case it can help somebody else.

    We were receiving a number of 1308 errors when attempting an EMCopy.  After looking at the permissions for the affected files and folders, we didn't see anything wrong.  Nothing was referring to a local user or group; only domain accounts.

    I downloaded a utility from Microsoft called SubInACL (found here: http://www.microsoft.com/en-us/download/details.aspx?id=23510) and ran it against some of the files in question.  I received output like this:


    E:\>SubInACL.exe /file E:\Staff\vince.valenti\docs

    ==================================

    +File E:\Staff\vince.valenti\docs

    ==================================

    /control=0x400 SE_DACL_AUTO_INHERITED-0x0400

    /owner             =bend\vince.valenti

    /primary group     =S-1-5-21-2479175398-2769753764-3671669682-513

    /audit ace count   =0

    /perm. ace count   =4

    Elapsed Time: 00 00:00:00

    Done:        1, Modified        0, Failed        0, Syntax errors        0

    Last Done  : E:\Staff\vince.valenti\docs

    Notice the primary group entry.  As far as I can tell, this is not visible anywhere from within the Windows GUI, and it's set to an unresolvable SID.

    I used a command like this to update the primary group:

    E:\>SubInACL.exe /file E:\Staff\vince.valenti\docs /setprimarygroup="bend\domain users"

    After doing this, EMCopy worked without a hitch.

    SubInACL is incredibly powerful.  I used a command like this to search for that old SID and replace it with domain users:

    E:\>SubInACL.exe /applyonly=group /subdirectories E:\Staff\ /replace=S-1-5-21-2479175398-2769753764-3671669682-513="bend\domain users"

    Anyway, I hadn't seen mention of the primary group entry in the security descriptor, so I wanted to document my findings here.  Hopefully this will help somebody in the future.

  • dynamox

    11 Legend

    •

    20419 Posts

    •

    87439 Points

    2250

    0

    Posted July 31st, 2012 11:00

    love Secure Copy, it used to be affordable when it was still SmallWonders software but then ScriptLogic bought that them and $$$ became ridiculous for what it does.

  • Rainer_EMC

    6 Operator

    •

    8645 Posts

    2250

    0

    Posted August 1st, 2012 06:00

    Good info – thanks for the feedback

  • jessemedina

    1 Message

    2250

    0

    Posted June 4th, 2013 15:00

    Thanks for the info... worked perfectly.