Skip navigation

iWork not iWorking on SMB in Mavericks

8528 Views 67 Replies Latest reply: Feb 25, 2014 6:39 AM by Wolf.NBM RSS
1 2 3 ... 5 Previous Next
Wolf.NBM Level 1 Level 1 (0 points)
Currently Being Moderated
Oct 25, 2013 1:46 PM

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, OS X Mavericks (10.9), MacBook Pro Retina
  • RBuday Calculating status...
    Currently Being Moderated
    Oct 25, 2013 8:30 PM (in response to Wolf.NBM)

    I have the same problem. I'm using Tuxera on Mavericks to read/write files on an NTFS server. iWork 09 worked fine on Mountain Lion and Tuxera, and continues to work fine on Mavericks. Other applications have no problem with Mavericks and Tuxera (TextEdit, MS Office, Photoshop, etc). The problems seems only with iWork 2013 and SMB shares.

  • Segalla Calculating status...
    Currently Being Moderated
    Oct 26, 2013 9:14 AM (in response to RBuday)

    Same problem here with a linux samba server.


    If I make a copy of the file (don't rename it after copying), open with Pages 13 (Pages and Keynotes too) then I can save it but if rename the copy then a i get the same error I got with the original file.

  • dsacgt Level 1 Level 1 (0 points)
    Currently Being Moderated
    Oct 27, 2013 10:39 PM (in response to Wolf.NBM)

    Same problem here with new iWork under Mavericks using windows SMB drives. I can't save any of my work to the network!


    I've submitted the bug to Apple via feedback.

  • dwb Level 6 Level 6 (19,705 points)
    Currently Being Moderated
    Oct 28, 2013 7:16 AM (in response to Wolf.NBM)

    In Pages 4 you could choose to save as package or a flat file. What is your default (look in Pages' Preferences). At work when we switched to Windows server I had to switch iWork so it didn't save as a package. Since Pages 5 doesn't have that option and only saves a package I'll bet that's why you are having the problem. I see it on some other (but not all) Mac applications that save files as packages.

  • dwb Level 6 Level 6 (19,705 points)
    Currently Being Moderated
    Oct 28, 2013 7:56 AM (in response to Wolf.NBM)

    True it shouldn't be a problem but like you I have full admin rights to the servers at work and I've seen the same problems with other programs that save as packages - an early release of Art Text for example. There is something special about a package or how a program updates a package once it has been saved that must cause the problem. Belight did eventually release an update that resolved the problem so we can hope Apple will too.

  • Segalla Level 1 Level 1 (0 points)
    Currently Being Moderated
    Oct 28, 2013 8:38 AM (in response to dwb)

    I set Pages 09 to save new documents as a package and it worked as it should in our smb linux server (mac os thinks it is a windows server).


    Any iwork 13 app can't save on the same shared driver except when we make a copy of the original file and use it without renaming it, if we rename it we get the same permission error we got with the original file.

  • _cpo_ Calculating status...
    Currently Being Moderated
    Oct 28, 2013 10:54 AM (in response to Wolf.NBM)

    same problem for me in mavericks and iwork 13. f.e. pages yells at me it cannot save files even I created them.


    I think I already know where the problem is: access rights are being changed when saving a document. It definately screws up the ACLs and then complains it cannot save, because the ACL which gives the user write access is removed (even so the parent folder has ACLs which should be inherited by all new files automatically - and do, but not when pages saves a document). Some ACLs are inherited, but not those giving the user write acces.


    Why the **** is pages touching the acls???

  • natecw16 Calculating status...
    Currently Being Moderated
    Oct 29, 2013 7:27 AM (in response to Wolf.NBM)

    I also have this issue, and am also experiencing similar save-to-SMB problems from Preview.

  • WLWEsq Level 1 Level 1 (45 points)
    Currently Being Moderated
    Oct 29, 2013 9:41 AM (in response to Wolf.NBM)

    Yep, same problem here—even though I can save to my Desktop and then copy the file to the proper place on the server, it's hardly an efficient workaround.


    Maybe it's just me, but the "upgrade" seems to be oxymoronic in this case. Disappointing.

  • _cpo_ Level 1 Level 1 (0 points)
    Currently Being Moderated
    Oct 29, 2013 11:24 AM (in response to Wolf.NBM)

    just noticing that weird new folders are created when saving a pages document (on share simply having rwx rights for everyone). the folders have the name "[8 random lowercase chars]-[6 random chars]". maybe some temporary files it fails to clean up - might be related to this issue ...


    what a mess.

1 2 3 ... 5 Previous Next


More Like This

  • Retrieving data ...

Bookmarked By (4)


  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.