Copying to Network Drive Error code -36

Anyone else having any problem copying to a shared network drive on Snow Leopard?

Every time I copy to out corporate shared network drives, I get an Error -36

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

Can anybody hep with this? It started ONLY AFTER upgrading to Snow Leopard.

MacPro 3.0 Xeon, MacBook Pro 17" C2D, MacBook Pro 15" LED C2D, Mac OS X (10.5.4)

Posted on Sep 1, 2009 3:01 PM

Reply
Question marked as Top-ranking reply

Posted on Jan 9, 2010 4:35 PM

I'm not sure if anyone have already posted this (long thread), but here's how I learned to remedy Error code -36 issues. The problem, I've found is when you copy files from non-apple formatted (HFS) devices (FAT32 windows drives, thumbdrives, smb or nsf network shares etc) into a Mac and then at some later point try to copy them back into those non-HFS devices.

It's something to do with the ._ files that get generated and then not properly restored. The solution I've found whenever an Error code -36 error appears is to open the troublesome folder (or folder containing the files) that Finder refuses to copy in a Terminal, run the command dot_clean and then try the copy again. It always works.
199 replies

Dec 2, 2009 6:36 AM in response to Magic__Dan

Hello Magic Dan,
I get a bit suspicios about XP64 and the LaCie drive.
Can you first of all try to download a new drive for the LaCie drive?
One which is suitable for XP64.

To alter in the registry is as I said something one would do as a last
resource.

As a second suggestion I would recommend you to search the net
for "error code 36" to get some more explanations.

Best regards
Dag S.

Dec 3, 2009 11:31 AM in response to Stuart Marden

Hmm, this doesn't solve my problem. I get this error when I try to copy my 240 GB iPhoto library via Gigabit Ethernet network from my Mac Pro over to my Mac Mini's attached Drobo which is formatted as Mac OS Extended (Journaled).

I raised a bug report on the 15th September. Apple has asked for some more detail from me. Haven't heard anything further. It is still open.

I shouldn't need to tweak or change anything to security settings. This is clearly a bug with copying packages. I can copy other files just fine.

Dec 3, 2009 11:37 AM in response to Stuart Marden

Before anyone thinks of following the actions in the KB article that Stuart Marden linked to ( http://support.apple.com/kb/TS2207), please note that the article does not apply to OS X.

The KB article specifically targets ancient versions of MacOS (system 7 through system 9), and trying to trash the Finder in OS X will probably cause more harm than good.

Dec 12, 2009 9:26 AM in response to rwlMac

i appear to have the same problems, however i cant believe i would, bearing in mind the simple connection i am trying to make.

i have a macbook and an external harddrive (samba) connected via SMB using my wireless router. Itunes and movies are stored on this drive.

the solution worked perfectly in Leopard. The upgrade to Snow Leopard now provides me with -36 errors everytime itunes looks for a song or i try to open a file from finder. if i copy from the network drive to my desktop it works fine.

i cant burn cds in itunes either as it tries to add them into the share drive. same for downloading podcasts!

so what are my options, surely this is a simple bug? maybe i am connecting in the wrong manner??

i cant believe i can no longer access my music?

help me obi-wan, your my only hope....

Jan 1, 2010 5:02 PM in response to MacUser4_20YRS

Same problem here...I bought a Time Capsule, completed a full backup of my mbp (Leopard) and then completed an erase and install of Snow Leopard. Now I can't restore any files from my backup. What a kick in the stomach.

For example:

The Finder can’t complete the operation because some data in “03 What's Up.mp3” can’t be read or written.
(Error code -36)

Thanks, Apple.

Jan 3, 2010 8:15 AM in response to Dogcow-Moof

If Apple does not "officially" read and respond on these boards, then why is it on the Apple website under the Support category? And even so, this problem was opened up on this "discussion board" more than 3 months ago. Various people have said that they have taken it to the Apple support team, and have discussed the issue with them. It was reported that it was supposed to be fixed in 10.6.2, but wasn't. And I have heard that it is supposed to be addressed in 10.6.3, but who knows when that is coming out.

In today's world of social networking, every community forum, especially those on your own site, should be monitored and issues addressed appropriately. It could be from someone in the PR department letting us know that the issue has been entered into the bug system and even providing us with some tracking number or something.

Apple has the reputation of being elitist, and this is one of the reasons why.

Message was edited by: gswd

Jan 5, 2010 4:52 AM in response to CarCode

CarCode wrote:
By the way who is William? Does he belongs to the Apple staff?
So why he does not post something like: Yes, the bug is known and Apple works for an update.


I'm just a user like you - I do not now nor never have worked for Apple.

If you want to know whether Apple knows about the issue and/or is working on it, for the third time contact AppleCare or join ADC and file a bug report.

Jan 10, 2010 1:48 PM in response to MacUser4_20YRS

William, please.
Submitting a bug report to Apple does not help me with this issue. I'm quite sure without bug reports Apple would still know about this issue as well. Even still, to answer your question. Yes, I have contacted Apple...and nothing. It's another problem with Snow Leopard and I am guessing certain drives. Problem is, I am having this problem too. It's pretty bad when there are over 10 pages of this stuff and this question still has not been answered. As much as people want to say Apple has nothing to do with these forums is complete bs as well. This *****.

Jan 12, 2010 12:49 PM in response to MacUser4_20YRS

I have exactly the same problem. Files downloaded from an FTP server, copied from a PB 12" running 10.5, copied to a USB key, then copied to a Windows network server, then recopied to a USB key..

And then I copy it to from the USB to my 15.4" running 10.6, and then copy it back to the USB key.... error code -36 on some files that I never even touched/modified using the 10.6 machine...

I can't even delete them from the trash and there's a "read/write error".. or "file is currently in use" which is BS as I've just rebooted...

Very, very frustrating

Feb 24, 2010 8:02 AM in response to MacUser4_20YRS

any further updates. i am still struggling to use itunes (it wont burn any songs if i use my sharedrive as the location folder for songs) or watch any videos/files kept on the share either.....

just to add, it all worked fine in the previous version, it appears to be purely snow leopard related.

Tried dot clean and the stream fix.
Using snow leopard and a landrive using SMB.

james

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.

Copying to Network Drive 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.