Copying to Network Drive Error code -36

Here's what I've determined so far:

1) Wasn't fixed in 10.6.1
2) Occurs with both Windows shares (SMB) and Time Capsule
3) Occurs with some files but not all
4) Does NOT occur when copying to another Mac with Snow Leopard that uses file sharing
5) Seems to be limited to finder copying, not using cp to copy from the Terminal

I'll chime in with my setup and experience.

I'm getting the Error 36 when trying to copy a 400MB iPhoto Library file to an AFP share on an OS X 10.6.1 Server. The error only started after reinstalling the machine with the final release of OS X 10.6 Server and upgrading to 10.6.1. I never had a problem while I was testing the developer seeds.

I transferred about 200GB of data (including files as large as a couple of GB) to the afp share and only the 400MB iPhoto Library gave the error 36. After zipping the Library it copied over fine.

What file system is being used on the NAS that everyone has the problem with? The NAS I am trying to connect to is a NTFS drive. I have read the seed notes from the latest build of 10.6.2 which state a fix to the following:

"issues when using NTFS and WebDAV file servers"

So hopefully 10.6.2 will resolve the problem!

Message was edited by: Ben_

Solved.

First, I added the users AD account to the network share and granted them

Full Control
Change
Read


I then opened the advanced security settings for the network share on our 2003 file server and edited the permissions to the following

http://img510.imageshack.us/i/permissions.png/

It looks like OS X has a problem Writing Extended Attributes unless the users AD account has specific permission to do so. You also have to make sure that you are connecting to the smb share as the same user that you changed permissions for.

So in summary, you don't need to grant full control, just Write Extended Attributes.

I had these errors all the time, but installing 10.6.2 fixed the problem for me. Now I don't see a single error anymore.
However I haven't used software update to go to 10.6.2, but I installed the update from the downloaded combo installer. Maybe there is a difference in the update procedure??

Hello Dag,

Both .TemporaryItems and .Trash are on the top of your share. As their names begin with a .dot they are invisible.
ls -lA from the CLI and you will find them. As I mentioned before I also changed the owner of the share to make saving of Office docs and xls possible.

One thing I did stumbled over today was the way of mounting the share from the mac. I had problems to save a PDF from Acrobat Prof. when I mounted the share with cifs://... but succeeded when I mounted it with smb://....

I hope this helps.

regards

oliver

It seems as if 10.6x has a problem with the NTFS ownership.
Reassign the owner to "network service", this is a local user of the NAS (in our case a netapp bound to AD)
until Apple fixes this mess, this is the way to read / write files from a SMB share.
regards

Oliver

credits for this hint goes to Chris Eads: http://www.macwindows.com/snowleopardAD.html#121009a

Repeating (from my reply above) what worked for us, trying and succeeding at a connection, from a Mac to a Windows 7 machine:

This works, when trying to connect from a PowerBook G4 running Mac OS 10.4.11 to a Windows 7 Pro 64-bit (BOOTCAMP on a Mac Pro) ...

Connect to Server:

smb://ip address_ofserver/SHARE

Note the capital letters "SHARE" for the network share on the "PC."

Also works from a Mac running Mac OS 10.5.8 "Leopard."

- - - - - - -

Now came the other difficult part - copying.

It seemed to fail 7 times out of 10, with a "Error code -41" if using the Finder, or 3 times out of 10 at the command line, using the "cp" command, with an error, "cannot allocate memory".

We tried the fix recommendation found online, which was to disable SMB2 on the Windows 7 machine. Some Windows 7 users tried this:

http://blogs.technet.com/srd/archive/2009/09/18/update-on-the-smb-vulnerability. aspx

Other Windows 7 users tried that manually - editing the Registry - to disable SMB2.

Disabling SMB2 on the Windows 7 machine, did NOT work for us.

So, we searched more online, using keywords "cannot allocate memory" with "windows 7" and finally found what works:

http://alan.lamielle.net/2009/09/03/windows-7-nonpaged-pool-srv-error-2017

That guy is a genius. Somebody give him a medal. Make him a "Hero of the Soviet Union! Dah!"

He states: "Apparently you need to tell Windows that you want to use the machine as a file server and that it should allocate resources accordingly."

His Registry fixes, at his webpage:

- - - FIRST - - -

Set the following registry key to 1 (Decimal):

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache

- - - SECOND - - -

[S]et the following registry key to 3 (Decimal):

HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\Size

"After making these changes and restarting, I haven’t seen this issue arise again. Fixed!"

Yes, that did fix the copying problem.

I can hardly believe it.

For a single file:

cp filename /Volume/sharename

for a folder/ directory,

cp -r foldername /Volume/sharename

Regards,
David

I have the exact same problem. It only happens when you copy "packaged" files, such as iPhoto Library. I hope Apple solves this bug soon.

It works if you use the "cp -rp" command in Terminal...

Tony, I can confirm that the issue occurs with packaged files. Not with ordinary files. For instance, if you take a file that fails, you can compress it into a ZIP file and copy the ZIP to the share.

My issue with copying files to our Microsoft file server resolved with 10.6.2. No more error code -36. Yay! Good luck to those with issues unresolved. 😟

guys I am having a bit of a breakthrough as I am able to copy to one of the volumes on the windows xp machine fine, I think it might have to do with the characters in the name of the sharepoint, try getting rid of any spaces or brackets

I think it depends on how recent your version of PathFinder is: I have the most recent update, and it definitely has the same problem as Finder.

But you're right, cp seems to work . . .

Regards,
David

As others have described, copying files results in error -36 after one file successfully copies. In addition, the update to 10.6.1 is no help. I am mounted to a distributed file share (DFS) via SMB. Worked before I upgraded to SL.

I am getting around the problem for now by creating a ZIP of local files and copying the single compressed file to the DFS. Once copied, I can successfully decompress the ZIP in the DFS location.

Man! I hope a fix to this is coming soon.