This discussion is archived
99480 Views 199 Replies Latest reply: Apr 8, 2010 8:35 PM by Robert Bosch
Currently Being ModeratedSep 16, 2009 4:27 PM (in response to belms)Oooh, Apple updated my bug report asking for clarification on a particular item.
I guess someone from Apple is looking at this problem! Yay.
Will keep you guys posted.Mac Pro Quad 2.66 GHz, Mac OS X (10.6.1)
Currently Being ModeratedSep 16, 2009 8:12 PM (in response to Tony Kambourakis1)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.Mac Pro, iMac, MacBook, iPhone, AppleTV, several iPods, Mac OS X (10.6)
Currently Being ModeratedSep 16, 2009 9:05 PM (in response to MacUser4_20YRS)I am having the same problem while trying to access my .psd and .avi files. They are stored on a NexStar LX NAS enclosure which contains a 500 GB drive. This drive had been working in 10.4, and I can still access it from my Vista and Ubuntu machines.
I have tried accessing the files from Adobe Bridge and from Finder, with no luck.
One thing that I have noticed with this upgrade is that when I connected to the network drive under 10.4, I would get an external drive icon on my desktop that I would then use to open the drive again later if needed. Now I do not get that icon.Mac Mini, Mac OS X (10.6.1)
Currently Being ModeratedSep 17, 2009 10:44 AM (in response to Apples_Rulez)Apples_Rulez suggestion regarding changing my status on the Security Tab of the Windows Server from "modify" to "full" worked - partially. I am now able to copy files from my machine onto the server without throwing the Error -36. But, when I open and modify a file on the File Server with MS Word, and then try to save it, I get an error from Word saying "the disk may be full or write protected..." I do not get this error if I do this with Pages. The Security status change and the Word problem may be two different issues.iMac 24; MBP 15"; iMac 20, Mac OS X (10.6)
Currently Being ModeratedSep 17, 2009 8:34 PM (in response to MacUser4_20YRS)Same problem but only with a NAS, I can access through SMB to a windows PC.... Apple please fix that since I work with files located in my NAS all the time.MacBook Unibody 5,1 (2008), Mac OS X (10.5.6), iPhone 2G| Ipod Nano 2nd, 4th & 5th Gen| MacBook Pro 13" (2009)
Currently Being ModeratedSep 18, 2009 5:58 AM (in response to MacUser4_20YRS)Let's make it a bit weirder....
I had the same problem, the error -36, when trying to copy a file / folder to my SMB drive.
I changed the security settings for this share to full access, saved, waited a bit until the operation was finished. Then I unmounted this share and mounted it again.
I tried to copy and it worked well, no more errors anymore.
I rebooted my machine, and tried packages, zips, large files, small files, everything seems to be fine.
But I am not happy with the full access settings.
So I reverted this setting, saved this, waited a bit until the operation was finished, remounted the share....
And it still works....
I tried that with other shares from different servers, windows 2003, xp and my netapp shares and the problem seems to be solved.
A miracle? I don't know...
I guess I have to be pragmatic and be happy that it works now. I do not need to understand everything...
Currently Being ModeratedSep 18, 2009 9:53 AM (in response to Daniel Palmer)The problem started to reoccur... Then I went to upgrade the VMFusion (vmware) the Snow Leopard machine that was having problems (to give the user an alternative method to get files out to a SMB share) and noticed that MACFUSE was still 1.5x and the newest version of MACFUSE is 2.x. After upgrading the VMFusion which also upgraded the MACFUSE to version 2.x, the user was able to transfer files to a SMB share on a Windows Server without any errors.
Quote from Google "MacFUSE allows you to extend Mac OS X's native file handling capabilities via 3rd-party file systems. It is used as a software building block by dozens of products."
I hope this solves everyone's problems.iMac 24" 2.66GHz; MBP 15.4" 2.8GHz; MBP 15.4 2.0 GHz; iPhone 3G; and lots of older G4 QuickSilver Ma, Mac OS X (10.6.1)
Currently Being ModeratedSep 18, 2009 11:34 AM (in response to Apples_Rulez)This should not be related at all.
This is a problem with net shares, and when accessing net shares you're not only not using, but you do not in fact need a filesystem driver.
P.S. I have the same issue, on two different machines. One of them is using nothing and the other is using Paragon NTFS.Macbook 2.0GHz, 2gb ram, Mac OS X (10.6.1)
Currently Being ModeratedSep 18, 2009 7:50 PM (in response to Oliver Kess)Confirming some of Oliver's findings:
1) My Share permissions were set so that Authenticated Users had read and write but not Full Control. Against the underlying directory, Authenticated Users had Full Control (file system permissions are different than share permissions).
2) Finder always gives Error -36 when copying to the share.
3) Set Share permissions so that Authenticated Users have Full Control.
4) Finder error goes away.
However, when I reverted the Share permissions to Read and Write, I got the Error -36 back. I can live with Full Control since this is just the Domain Controller in my home, not so sure I'd want that setting in a different environment.iMac / MacBookPro, Mac OS X (10.6)
Currently Being ModeratedSep 18, 2009 8:00 PM (in response to herveyw)More data:
Whilst setting Full Control on the Share seems to get the files across, I still occasionally get Error -36 when the copy completes. I also seem to have a side-effect in that now file deletes on the share take much, much longer to complete.iMac / MacBookPro, Mac OS X (10.6)
Currently Being ModeratedSep 20, 2009 11:24 AM (in response to herveyw)Hi,
I got the file copying errors too, and the situation is the following:
1. I got a Synology DS-107+ NAS, and I got different shared mapped to my Mac using SMB.
2. I got a Windows XP PC using the same drives.
Before I upgraded to Snow Leopard all was working perfectly on both Windows and Mac using these shares, and to be honest I am unsure if the problems occurred with the SL 10.6 version or with the update to SL 10.6.1. The Windows PC still works perfectly, but when I attempt to copy any file to the shared drives on my Mac I get an error telling me that the action could not be completed as I do not have the rights to one or more of the items. (attempt to translate the Danish message I get to English). In any case it complains about missing rights.
Interestingly enough I am allowed to create a new folder, and delete this folder too, but an attempt to copy any type of file to the new folder or any existing path on the drives fail. There is no doubt it is an error in Snow Leopard, and I just came from the Synology support forum where people reported this error too, and someone referred to this discussion, and here I can see it is a general problem with NAS devices, and not just the Synology boxes.
I sure hope Apple reads through these discussions and takes immediate action (meaning fixing it with highest possible priority). I am new to the Mac side (just 3 1/2 month into my Mac life), but after many years in the Windows world I would say that one point where Apple falls through hard is their ability to send out updates that really screws up things that worked before the update. :/ I hope my future Mac experience will prove me wrong.MacBook Pro, Mac OS X (10.6.1), 13.3" Model with 2.53GHz. CPU and 4GB Memory.
Currently Being ModeratedSep 22, 2009 2:26 AM (in response to MacSnow)Hi everybody! Have tried zipping a file but to no avail. Doc-type was .chm. Dragged and dropped file onto Windows share with full control in Finder. Got error -36 and unzipped file was damaged. Share connected to using CIFS. C'mon Apple...imac, macbook, macbook pro, power mac, Mac OS X (10.6.1)
Currently Being ModeratedSep 25, 2009 2:22 AM (in response to MacUser4_20YRS)Same problem with a SMB external drive.
As you mentioned the problem is in finder. I cannot copy, modify or just read my files on the external drive connected by ethernet to my router.
But if open the files directly with a program (quicktime for videos) or I just try the preview with spacebar everything works fine.
If U have any suggestion, please post a message. ThanksMacbook Pro 3,1, Mac OS X (10.6.1)
Currently Being ModeratedOct 2, 2009 12:46 AM (in response to Aragorn77)I have been having all the same problems you all have had with this error -36 when copying to an SMB drive (actually a Microsoft SBS 2003).
After following these discussions for a while I have now tested changing the permissions on the drives to "full control" and this has fixed my issues when copying to these drives - for all file types.
While I agree with one of the other posters here that some network admins may not actually agree to giving people "full control" for us in our company it was the only way around the issue until an Apple solution is released.
(now if I could just fix my supposedly bad battery that was fine before the 10.6.1 upgrade!)MacBook Pro 15" (Pre-Unibody), Mac OS X (10.6.1)