Currently Being ModeratedOct 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.
Currently Being ModeratedOct 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.
Currently Being ModeratedOct 28, 2013 6:42 AM (in response to Wolf.NBM)
At least I know I'm not crazy and others are having similar issues. There are lots of other reports of the problem on other forums as-well. I did report it in Feedback as a bug, but at least here you can usually-eventually get some kind of an answer from someone at Apple.
The only "solution" I have found online is to use CIFS, which still doesn't work on Windows networks. It may work on some NAS devices that support it, but it is not an option for anyone running SMB1. Some have also said it is an actual permissions issue. I have "full" read/write access to the volumes I am accessing (I'm also the sysadmin), and I even changed one to allow for "everyone" access- no dice.
Currently Being ModeratedOct 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.
Currently Being ModeratedOct 28, 2013 7:39 AM (in response to dwb)
iWork does seem to be saving everyting ot packages now, but that seems irrelevant, since the network volumes still have permissions for it to do whatever it wants. And, as you said- there is no option to turn that off anymore.
Currently Being ModeratedOct 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.
Currently Being ModeratedOct 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.
Currently Being ModeratedOct 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???
Currently Being ModeratedOct 29, 2013 9:16 AM (in response to Wolf.NBM)
There is more information and a partial work-around for general SMB issues here:
Unfortunately, this does not fix the problems with iWork and other apps trying to use SMB network shares at-all. In my own experience using Mavericks for a week- I am constantly having SMB issues I didn't have before Mavericks, including losing connections to shares at-random and having to reboot to get them back. This is almost like the "dark ages" when Apple dropped SAMBA.
iWork is still completely unusable on an SMB network, and no fixes have been even hinted-at. I just finished pitching iWork as a replacement of MS-Office at my company, and this happened.(!)
Currently Being ModeratedOct 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.
Currently Being ModeratedOct 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 "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.
Currently Being ModeratedOct 30, 2013 11:10 AM (in response to Wolf.NBM)
Just to add to this- we allowed some other users at my company to "upgrade" to Mavericks. Even with the SMB1 trick that has been posted- they are reporting issues with other software beyond iWork having the same problems, including MS-Office and Adobe products. There is a permissions issue that seems to be a throw-back to earlier versions of OS X.
iWork just takes it to an extreme because of its versioned auto-save system that gets stuck in an unrecoverable loop thanks to this SMB problem.