Wolf.NBM

Q: 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, OS X Mavericks (10.9), MacBook Pro Retina

Posted on Oct 25, 2013 1:46 PM

Close

Q: iWork not iWorking on SMB in Mavericks

  • All replies
  • Helpful answers

first Previous Page 4 of 6 last Next
  • by PeterBreis0807,

    PeterBreis0807 PeterBreis0807 Jan 15, 2014 4:01 PM in response to kginger_consulting
    Level 8 (35,658 points)
    Mac OS X
    Jan 15, 2014 4:01 PM in response to kginger_consulting

    So why have you "updated" your 100+ documents to the new iWork format?

     

    Were all those features in iWork '09 annoying you?

     

    As iWork '09 runs on most Mac hardware and OSes, was that killing your productivity?

     

    Peter

  • by geertss,

    geertss geertss Jan 21, 2014 11:29 AM in response to PeterBreis0807
    Level 1 (0 points)
    Jan 21, 2014 11:29 AM in response to PeterBreis0807

    As long as you don't use icloud there is no problem.  If you do use icloud and you save your iwork '09 document on icloud.  Once you've opened it in the icloud beta version, you can't open it anymore.  That's why you need the new iwork anyway.

  • by PeterBreis0807,

    PeterBreis0807 PeterBreis0807 Jan 21, 2014 12:53 PM in response to geertss
    Level 8 (35,658 points)
    Mac OS X
    Jan 21, 2014 12:53 PM in response to geertss

    Yes I know all that, but iCloud is not the only way to share documents and a heavy price to pay if you can't create what you want in the first place.

     

    Peter

  • by Bill Eccles,

    Bill Eccles Bill Eccles Jan 30, 2014 7:54 AM in response to kginger_consulting
    Level 1 (143 points)
    Apple TV
    Jan 30, 2014 7:54 AM in response to kginger_consulting

    I'm using OSX Server 10.6.8 and have all SMB services turned off, so I have to assume that using AFP doesn't solve the problem. I, too, see the mystery folders appear.

  • by Bill Eccles,

    Bill Eccles Bill Eccles Jan 30, 2014 8:30 AM in response to Bill Eccles
    Level 1 (143 points)
    Apple TV
    Jan 30, 2014 8:30 AM in response to Bill Eccles

    I'm a bit confused by the comment that "This is an option for those who had iWork '09 installed previously" (or words to that effect).

     

    Does reverting to iWork '09 solve the problem regardless if it had been installed or not? I.e., I've got one machine I have only had '13 on. I anticipate that I can put '09 on it and delete '13 and all will be well (after documents are reverted, that is).

     

    Correct?

  • by PeterBreis0807,

    PeterBreis0807 PeterBreis0807 Jan 30, 2014 8:40 AM in response to Bill Eccles
    Level 8 (35,658 points)
    Mac OS X
    Jan 30, 2014 8:40 AM in response to Bill Eccles

    Pages '09 worked and continues to work.

     

    The problem as I understand it is the new Pages/Numbers/Keynote 5 file formats.

     

    Peter

  • by Tim Lings,

    Tim Lings Tim Lings Jan 30, 2014 10:21 AM in response to Wolf.NBM
    Level 1 (45 points)
    Jan 30, 2014 10:21 AM in response to Wolf.NBM

    From my experience, it seems that the .1 update released last week fixes this SMB bug across the iWork suite. Anyone else have similar joy?

  • by natecw16,Helpful

    natecw16 natecw16 Jan 30, 2014 10:26 AM in response to Tim Lings
    Level 1 (5 points)
    Jan 30, 2014 10:26 AM in response to Tim Lings

    It does appear that it might indeed have fixed the SMB issues. I feel like I might jinx it by saying so, but my Pages docs stored on our SMB server appear to be saving correctly.

  • by MarkJamesDolan,Helpful

    MarkJamesDolan MarkJamesDolan Jan 31, 2014 2:52 AM in response to Wolf.NBM
    Level 1 (5 points)
    Jan 31, 2014 2:52 AM in response to Wolf.NBM

    I can confirm that the save bug certainly on my SMB server seems to have gone in .1

  • by Wolf.NBM,

    Wolf.NBM Wolf.NBM Jan 31, 2014 7:03 AM in response to Wolf.NBM
    Level 1 (0 points)
    Jan 31, 2014 7:03 AM in response to Wolf.NBM

    Wow- they appear to have "silently" fixed the problem with the latest iWork updates. There is nothing in the change logs that indicates an SMB fix, but I just tested several documents and they didn't get corrupted and I could actually save them without getting stuck in a black hole of error messages. I'm going to do some more testing and have some more of my staff test it before getting too excited.

  • by Bill Eccles,

    Bill Eccles Bill Eccles Jan 31, 2014 7:14 AM in response to Wolf.NBM
    Level 1 (143 points)
    Apple TV
    Jan 31, 2014 7:14 AM in response to Wolf.NBM

    I've got anecdotal evidence that it hasn't been fixed for AFP, though why there would be a difference, I don't know.

     

    We'll be experimenting over the next day or two with the .1 version and I'll let you know.

  • by Wolf.NBM,

    Wolf.NBM Wolf.NBM Jan 31, 2014 7:17 AM in response to Wolf.NBM
    Level 1 (0 points)
    Jan 31, 2014 7:17 AM in response to Wolf.NBM

    For the record- the only issue I am having now is the Macs still lose access to CIFS (SMB1) shares when they sleep. The only way around this I have found is to logout and log back in again. This isn't quite the same as the original issue though.

  • by Bill Eccles,

    Bill Eccles Bill Eccles Feb 7, 2014 10:23 AM in response to Wolf.NBM
    Level 1 (143 points)
    Apple TV
    Feb 7, 2014 10:23 AM in response to Wolf.NBM

    It appears to save OK with AFP-mounted volumes as well. But how long do we use it before declaring victory, because I just had a user report that she saved it to her local Desktop and it created a new folder for each attempted save, still never saving the actual document. (And she sent a screenshot to me to prove it. Smart woman!)

     

    Anybody else seen this behavior?

  • by Jeff Shenk,

    Jeff Shenk Jeff Shenk Feb 7, 2014 10:45 AM in response to Bill Eccles
    Level 4 (2,803 points)
    Feb 7, 2014 10:45 AM in response to Bill Eccles

    People have reported that Desktop behavior with Pages '09 documents, which are zipped bundles, if they have Stuffit Expander installed, and its preference to automatically expand archives on the Desktop set. But I think you are referring to Pages 5.1 documents, which have a different structure, so that wouldn't apply.

  • by Bill Eccles,

    Bill Eccles Bill Eccles Feb 7, 2014 11:45 AM in response to Jeff Shenk
    Level 1 (143 points)
    Apple TV
    Feb 7, 2014 11:45 AM in response to Jeff Shenk

    Oh. My. Goodness. That is about as unobvious as it gets!

     

    Indeed that one lone client had StuffIt Expander installed. I had her remove it and the problem disappeared. Thank you very much, Jeff!!

     

    The interesting thing is that this is a Numbers 3.1 installation (your assumption is correct, though the version numbers are different across the iWork suite) and it is definitely creating a zipped bundle or something which gets gorked by Expander.

     

    I just tried the process on my desktop with the source document she used (which was a plain old text CSV file) and it does get saved as a package on my desktop. But I don't have Expander installed, so it gets left alone.

     

    Thanks again, Jeff!

first Previous Page 4 of 6 last Next