iWork not iWorking on SMB in Mavericks

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.

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.

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.

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.

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.

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.

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???

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

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.

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 "original_filename.pages.sb-[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.