Ali Kaylan
Level 1 (5 points)

Q: Copy fails with error -36 (introduced with 10.9.2)

10.9.2 seems to have introduced a new bug that surfaces during a Finder copy from local volumes to remote volumes on Mavericks server 3.0.2. Copies partially fail with error message -36. This new problem was not there with 10.9.1 & Server 3.0.2. A video is of this behavior can be found here.

 

In summary:

 

  • A single file copy fails with Error -36, but the file is actually copied.
  • Multi-file copy also fails with Error -36, but the first file is actually copied.

 

There are no permissions issues locally, or on the server, so this is not a permissions failure. Server is running 3.0.2. Any solutions would be greatly appreciated.

MacBook Pro with Retina display, OS X Mavericks (10.9.1)

Posted on Feb 26, 2014 4:15 AM

by BenPridmore,Solvedanswer
BenPridmore BenPridmore
Level 1 (10 points)
A:

You can try turning off smb on your file share. Forcing connecting macs to use afp. Windows machine will be unable to connect of course. If you try this can you let me know how it goes.

 

Thanks

Posted on Feb 26, 2014 5:40 PM

Close
Ali Kaylan

Q: Copy fails with error -36 (introduced with 10.9.2)

  • All replies
  • Helpful answers

first Previous Page 3 of 3

  • by Ali Kaylan,

    Ali Kaylan Ali Kaylan May 22, 2014 8:46 AM in response to odx
    Level 1 (5 points)
    May 22, 2014 8:46 AM in response to odx

    I can also testify that 10.9.3 and Server 3.1.2, I no longer have this problem, and can turn SMB back on. It took many months to get to this point.

  • by Maurits Sanders,

    Maurits Sanders Maurits Sanders May 23, 2014 3:28 AM in response to Ali Kaylan
    Level 1 (30 points)
    May 23, 2014 3:28 AM in response to Ali Kaylan

    I can confirm too that 10.9.3 solved this irritating issue.

     

    I did not update the server.app on the server (still running 3.0.3), only the OS on server and clients to 10.9.3 and the error 36 is gone, we can copy files to our server using sbm (v2) again.

     

    A very welcome bugfix in our mixed Mac / PC environment with Mavericks Server.

  • by FlyingLemming,

    FlyingLemming FlyingLemming May 23, 2014 7:56 AM in response to Ali Kaylan
    Level 1 (0 points)
    May 23, 2014 7:56 AM in response to Ali Kaylan

    Updating the server to 10.9.3 fixed it for me as well, also when accessing the server from a 10.9.2 client. Finally...

  • by Fredrokk,

    Fredrokk Fredrokk May 24, 2014 1:19 AM in response to Dario Pompei
    Level 1 (0 points)
    May 24, 2014 1:19 AM in response to Dario Pompei

    Happy to hear that the new update solved the problem for most. It seems that those who still experience error 36 conserns instances where the server isn't an apple server. In my case a NAS running *nix still gives me same error which was introduced with 10.9.2

    The nas has been working flawlessly for many years but I guess there is no way to solve this other than reverting to 10.9.0.

  • by FlyingLemming,

    FlyingLemming FlyingLemming May 24, 2014 2:00 AM in response to Fredrokk
    Level 1 (0 points)
    May 24, 2014 2:00 AM in response to Fredrokk

    That sounds plausible, since the error obviously has been introduced with the 10.9.2 update on the CLIENT side (tested with server still running 10.9.1), but the fix with 10.9.3 on the SERVER side (tested with client still running 10.9.2). It appears that there still is a flaw in the client implementation, which might show up with certain other unix based servers besides Mac OS Server pre-10.9.3.

first Previous Page 3 of 3