Error code -36

Question

Level 1

0 points

Error code -36

Just updated to 10.9.2 on both my imac and my mac mini server.

I share a drive on my mac mini server using server's file sharing, and I mount it with SMB on my iMac. Well I should say prior to 10.9.2 I did now everytime I do and I move a file to the mounted drive from my imac to my server I get this error.

The Finder can’t complete the operation because some data in “filename” can’t be read or written.(Error code -36)

As far as I can tell the files copy perfectly and if I mount the drive with afp it works just fine as well same drive mounted over SMB well same error. Anyone else notice anything like this? Id like to use SMB as it seems to work a little faster.

The drive in question is a drobo but it seems to affect any drive mounted with SMB after the update.

iMac (27-inch Mid 2011), OS X Mountain Lion (10.8.2)

Posted on Feb 26, 2014 9:49 PM

Reply

Answer 1

Feb 27, 2014 7:04 PM in response to sp1te

I'm experiencing the exact same problem after updating to 10.9.2 and the latest version of OSX Server. In my case my server is a mini with a 4TB WD Firewire Drive. Everything was working fine with my laptop running 10.9.1, and the mini running 10.9.2.

Reply

Answer 2

Feb 28, 2014 4:46 AM in response to sp1te

We're having this issue too after updating our mac mini server. Did you find any solutions? We've tried fixing permissions and changing user permissions with no joy.

Reply

Answer 3

Feb 28, 2014 5:01 AM in response to King Monkey

For now, I'm using AFP instead of SMB.

Reply

Answer 4

Feb 28, 2014 5:14 AM in response to jsstrongarm

Tried turning off SMB, but then couldn't connect with AFP...

Reply

Answer 5

sp1te Author

Level 1

0 points

Feb 28, 2014 9:02 AM in response to sp1te

So far I'm just using AFP, Ill have to test further but it is mardigras and I live in new orleans, so basically I'm out for another week. Just glad some other people (well not glad for you all) are also having the same issue and its not me just having some weird one off problem.

Reply

Answer 6

Feb 28, 2014 9:15 AM in response to sp1te

We're having the same issue as well. Mac Mini 2013, System: 10.9.2, Server: 3.0.3.

It happened after the 10.9.2 update, which we did before the 3.0.3 update. We only have SMB and AFP turned on. If I uncheck SMB, it removes the folder from the list of available shares (while going through the sidebar on the client machines).

Reply

Answer 7

Mar 1, 2014 12:32 PM in response to sp1te

Same problem here. Error when using SMB; works fine with AFP.

Reply

Answer 8

Mar 1, 2014 5:47 PM in response to sp1te

Count me in as well. Upgraded to 10.9.2 on a mac mini server with external storage connected via firewire. Happens regardless of whether the copy takes place over physical ethernet drop or wi-fi. Sounds like Apple forgot to check SMB in this patch. The files don't actually appear to be corrupted but would be nice if apple could patch this quickly to make this error code go away.

Reply

Answer 9

rsnowbdc

Level 1

0 points

Mar 2, 2014 4:29 PM in response to sp1te

Same problem here! Very frustrating.

Reply

Answer 10

Mar 3, 2014 3:20 AM in response to sp1te

We've tried to switch to AFP (unchecking SMB in file sharing), but when we do our users cannot connect to the server (the passwords don't work).

Is there any other settings we need to change? As we could be waiting a while for a software fix...

Reply

Answer 11

Mar 3, 2014 4:25 AM in response to King Monkey

I didn't disable SMB for mine. Instead, what I've been doing is connecting by pressing CMD+K in Finder, and then entering afp://server/share (see image).

Reply

Answer 12

Mar 3, 2014 5:37 AM in response to jsstrongarm

Thanks for the reply jsstrongarm

I've tried to connect this way, but it keeps saying access denied when using my log-in....

Reply

Answer 13

rsnowbdc

Level 1

0 points

Mar 3, 2014 5:50 AM in response to sp1te

Spent a great deal of time on the phone with Apple about this last night. Basically sounds like a bug that has been escalated up to the engineers. We had issues with AFP and had to delete the LDAP on our server and create new to get AFP to work. We had no problem with PC to the Mac Server, just Mac to Mac Server. So for Mac to Mac Server we are now using AFP until there is a fix, PC to Mac Server is fine. They think it may have something to do with using SMB2/3 protocol.

Reply

Answer 14

Mar 4, 2014 6:45 AM in response to sp1te

Same problem. AFP working, SMB connection from 10.9.2 not working. PC also have locked file problems. Stil no solution in 10.9.2 and Server 3.0.3

See in the log hile a lot of errors over ARTIbute not supported in filesystem.

File are copied to server Volume but one file at the time, because of te error.

Reply

Answer 15

Mar 4, 2014 6:51 AM in response to sp1te

After a lenghty phone call with Apple support it was decided that the recent updates had currupted our Open Directory, which then affected our DNS. So with Apples help we set up a new Open Directory and Users and now we have a working server over SMB and AFP.

Reply