User profile for user: brycesteiner
brycesteiner Author
User level: Level 2
204 points

File copy Error code -36

I see there are quite a few people having Error code -36 when copying files.User uploaded file

Some have stated that it's file corruption, but it's not. The files are on a Mac Mini server that was upgraded to Yosemite. When running Samba (SMBup) there was no errors (losing the ability to tag files and search is why we want apple's implementation). There is also no errors when the connections are AFP. The problem is though Apple is convinced that SMB is the future and that is now the default.

I've read that it's a permissions problem, but can't seem to get it fixed.


I've tried :

disk check and repair

the dot_clean command

deleting the .ds_store hidden files


I'm using Yosemite with the Server app. The windows and mac machines are connecting to it just fine but when it comes to copying, both have issues. The files are successfully copied even though the error happens. This error happens to every file every time. Yosemite and El Capitan clients are effected. Windows users are also effected but with a different error.


I can't do anything right now because the server is in use, but I might be able to get at it tonight.


thanks for your insight.

iMac, OS X Yosemite (10.10.5), 27"

Posted on Nov 4, 2015 8:37 AM

Reply
8 replies
User profile for user: bill.the.cat
bill.the.cat
User level: Level 1
8 points

Jul 29, 2016 12:08 PM in response to brycesteiner

I am now having this exact issue as I am upgrading a client's computers to El Capitan with Yosemite server. The problem is not related to the ds_store files or anything else that has been suggested about "cleaning up" files. This only happens when copying even a single solitary file from an El Capitan computer (I've now tried three different computers) to a particular server volume. And, it doesn't happen with all server volumes, only two out of the five. And, it doesn't happen with any of the 10.8.x, 10.9.x or 10.10.x computers, only those with 10.11.x.


Any ideas would be greatly appreciated.

Reply
User profile for user: brycesteiner
brycesteiner Author
User level: Level 2
204 points

Jul 30, 2016 7:35 PM in response to bill.the.cat

You say it only happens with the clients running 10.11.6?


Are you running 10.11.6 Server or only the file sharing built in? If you are trying to install Yosemite Server on 10.11.x it will not work. You must run the current Server with the current OS.


I haven't had issues since I upgraded the computer HDD's to SSD's and then to the newest server software. I had a few permissions problems but I got the worked out.

Reply
User profile for user: bill.the.cat
bill.the.cat
User level: Level 1
8 points

Jul 31, 2016 5:58 AM in response to brycesteiner

I have only tested with clients running 10.11.6 and 10.8.5/10.9.x. All non-El Capitan clients work perfectly. All 10.11.6 clients do not. The error is generated even though the file is copied properly. As stated in my original post, the server is 10.9.x server. This has nothing to do with the drives as there are four shared volumes on two external drives and this only happens on one volume. We have no interest in upgrading to 10.11.x server as that is also not the issue. It would appear that El Capitan, either all versions or the latest, does not properly implement SMB such that this error is generated. I have found instances where forcing the El Capitan client to connect with SMB1 makes the error disappear. I also found that by switching off SMB from all my shares, the problem has also gone away. This appears to be a bug with the implementation of SMB in El Capitan ... again, in all versions of just the current. But, given that AFP is probably going away before too long, I'd rather not wait around for a proper fix.

Reply
User profile for user: brycesteiner
brycesteiner Author
User level: Level 2
204 points

Aug 1, 2016 7:18 PM in response to bill.the.cat

I'm wondering if you have a permissions problem on the volume that has the issue. I have had much less problems since switching to the newest OS and Server. I started completely over instead of just upgrading and planned it all out on paper ahead of time with new drives and switching all to SMB (Time Machine still requires AFP, I believe).

If you want to keep the older server I would suggest going with the third party app SMBup (it uses Samba). It worked very well for PC's and Appletalk worked great with it. There are also many more options for choosing versions for compatibility.

I was using 10.8 server. I almost wished I never upgraded because It worked so well and when I did. SMBup never worked right with the newest SMB protocol made by Apple.

Reply
User profile for user: Eric Root
Eric Root
User level: Level 10
685,221 points

Sep 11, 2016 10:58 AM in response to Alissymccracken

You might want to start your own post since this one is from last year. A new post would be much more visible. You can link to this one.

Finder - How to Quickly Fix Error Code -36 in Finder of Mac OS X


Finder - Mac Error Code 36 when transferring files


Finder - Solution to Finder “Error code -36″ in 10.6 when copying


Finder - What to do about error -36 and other I/O errors in OS X

Reply

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

File copy Error code -36

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.
Learn more Sign up