Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

iWork not iWorking on SMB in Mavericks

I had to apply a hack to get SMB (to Windows Server 2008R2) to even work in Mavericks, but now I have encountered a new problem:


Any file I open in Pages or any other iWork app from an SMB share becomes unsavable, as soon as anything is changed in it.


It starts with an Autosave error: "The document could not be autosaved. You don't have permission to write to the folder that the file is in."


From there, I can't even duplicate it, export it, or anything. Everything I do gives me a "The location of the document xxxx cannot be determined."


Even if I try to do a "Save as", I get the same "You don't have permission to write..." error (even to my own desktop!).


If I try to "Duplicate" the file- I lose all embedded elements (images) and most of my formatting.


I don't recall having this problem before, but I just started testing the iWork applications again since upgrading to Mavericks. I have been looking for an alternative to Microsoft Office for my company's staff, but this really makes iWork "not ready for prime time" in a business environment. I hope this has something to do with the SMB2 issue, and it will be resolved soon, but I am open to any suggestions to try to fix the problem.

iWork-OTHER, OS X Mavericks (10.9), MacBook Pro Retina

Posted on Oct 25, 2013 1:46 PM

Reply
75 replies

Nov 23, 2013 2:03 PM in response to RBuday

Very frustrating!

I use this as workarround: copy the file to the desktop, edit it, copy it back again (replace).


Since I updated to Mavericks on my MacBook Pro, when I try to use it after it's been in sleep mode, it takes "for ever" to reconnect to the NAS and the internet, while the Wifi is connected. It looks like I can speed things up by turning Wifi off and on again. Is this a same sort of issue as the SMB issue?


Peter

Nov 25, 2013 7:14 AM in response to Wolf.NBM

Apple updated iWork over the weekend. Didn't fix this problem!


Also- SMB seems to have gotten even more unstable, although I'm not sure why since I don't believe it is tied to a Mavericks update. I frequently lose my connections to SMB shares now, and the only way I can reconnect is to log out and log back in, or reboot. I tried CIFS as an alternative- and it was even worse (random disconnects), and didn't have any affect on iWork. iWork is completely unusable unless I only work locally.


Yes- I've submitted all of this in Feedback as a Bug Report. They just seem to be ignoring the problem. I guess when you give something away for "free", you don't have to support it anymore. Very dissappointing.

Dec 3, 2013 11:11 PM in response to Wolf.NBM

Same problem here. On Mavericks clients that will default to SMB connections I have instructed fileshare users to use "Go" > "Connect to Server..." and manually enter afp://servername_or_ip . to force AFP connections. I have created aliases for those shares once connected.


Also cannot send/receive the new iWork file format as an attachment from gmail, haven't tested other email servers.

Dec 12, 2013 6:54 AM in response to Petie81

AFP only works on servers/NAS devices that support it. It is Apple's proprietary network file protocol, and I believe they have abandoned it in favor of SMB2. If you use Windows-based servers or NAS devices that only support SMB- it isn't an alternative.


CIFS is an alternative that forces the use of SMB1 in Mavericks, without using the SMB1 hack (earlier in this discussion). For whatever reason- it seems to actually work worse than the old Mac SMB implementation.


iWork is still useless on network shares, and CIFS/SMB1 still randomly disconnect and cause permission corruption for all of our users who we upgraded to Mavericks. For the record- we had random and infrequent permission corruption in earlier versions of OS X, but with Mavericks- we can count on it on a regular basis.


I'll look at Tuxera, but as a rule- we try to keep things as "native" as-possible to avoid future compatibility issues. This is a problem Apple needs to get fixed if they really want to make serious inroads into the Enterprise, which they claim they do. In many ways- their competition is self-destructing and becoming desperate- they should be taking advantage of it. I had to buy six new Windows computers this month for my company, which could have been MacBooks if it wasn't for these problems.

iWork not iWorking on SMB in Mavericks

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.