Currently Being ModeratedDec 12, 2012 6:35 AM (in response to rossannett)
You could try deleting the com.apple.iwork.pages.plist from the preference folder on the users Library folder. To find that Library you click on Go in the Finder menu bar while holding down the Option/Alt key. Do this with Pages quitted.
Currently Being ModeratedDec 12, 2012 10:09 AM (in response to rossannett)
I'm having the same issue. When I attempt to email from the share menu, nothing happens. If I attempt to export Word from the Share menu, I get a error that an unknown error has occurred. I have deleted preferences. Deleted Pages and reinstalled as well. Issue is still happening.
Currently Being ModeratedDec 12, 2012 12:02 PM (in response to Escaport)
Yeah, tried deleting and reinstalling too.. Still no joy.
I've submitted a negative review in the App Store so hopefully someone from apple reads it and can release a patch.
It's a major PITA when everything else just works!
Currently Being ModeratedDec 13, 2012 9:59 PM (in response to Escaport)
When an application isn't working as it should there are several things to try. Repair permission using the free Onyx application, delete cashes, delete and reinstall Pages.
You could first try Pages in another user account on the computer. You can create a new account in System Preferences > Accounts
Currently Being ModeratedDec 17, 2012 2:43 AM (in response to Jeff Shenk)
oh man.... i am very embarrassed to say, but that is exactly what the problem was.
i was trying to email "filename 12/12/12" and because they were special characters it wouldnt let me do it.
I feel quite silly now......
Currently Being ModeratedDec 17, 2012 4:25 AM (in response to rossannett)
You shouldn't be too embarrassed; it doesn't seem like it would have been too difficult for the developers to display some kind of error message like "The operation failled because the filename contained an illegal character."
That would, of course, violate the Guidelines for Error Messages (based, I believe, on the older Code for Carnival Fortunetellers) that stipulates that error messages should be sufficiently cryptic that they are only meaningful after the error has been independently explained, and that furthermore they should be ambiguous enough to apply to a multitude of possible failures.
Currently Being ModeratedDec 17, 2012 5:27 AM (in response to Jeff Shenk)
Just verified, and that does not solve my issue. Using iCloud, I can convert to Word in my iPad. Just the updated MBP is having issues. My desktop that has not been updated can convert as well.
Currently Being ModeratedDec 17, 2012 7:40 AM (in response to Escaport)
I am not sure what you verified and what you tried that did not solve your issue.
I do not use Mountain Lion, I don't export to Word and if I did, I probably would not use the Share menu to do it. I just asked a question, based on what I have read here, which apparently did answer Ross' issue.
Based on what I've read, there are two common reasons why the Share > Send via Mail > Word process fails on Mountain Lion.
First, apparently Mountain Lion has tightened its requirement that filenames not include illegal characters (possibly only when exporting to a Mail attachment). Earlier systems would let these illegal names pass, and often there would be no problems. If your desktop is not running Mountain Lion, it would not have this issue, nor, as faar as I have read, would your IPad. If the Share > Send via Mail > Word process fails on your MacBook Pro, even though you specify a filename that contains only letters, this is not your issue.
The second reason I've seen for this process to fail is when Mail is not set up to send email. Some people mistake the menu item to mean email as a generic term, whereas, at least on my Snow Leopard system (and in Jerry's screenshot), it specifically refers only to Apple's Mail program. Since you report problems with a simple export as well as with sending to Mail, I would not expect this to be your problem.
Does it still fail to export if you create a very simple document, say one word: "Test." typed into the blank wordprocessing template and exported as test.doc?
Currently Being ModeratedDec 17, 2012 8:15 AM (in response to Jeff Shenk)
I am using Mountain Lion. I'm not aware of any differences between File>Export>Word and Share>Export>Word. Share>Send via Mail>Word is as far as I know, an normal export with an added script of sending via Services to Mail. Apparently it does have the added issues of suppressing export error dialogs though.
So the plot thickens a bit now. I tried a few things.
- Altering the name of an existing document that was exhibiting the issue and save. Then export.
- Creating new basic test document. Then export.
The first case still showed the issue. The second case worked as expected. From this I looked a bit more into the first case's document. The only part of the document that was not just standard text was a few unordered bullet points and a page break or two.
This led to creating a third test document that had bullet points and page breaks. This document exported without issues as in the second test case.
After this I coppied the text of the first case's document and pasted it into a brand new test document. Then tried to export. The new document failed to export and resulted in the "An unknown error has occurred" error dialog. (Note: This is using Export>Word, not the Word>Send via Mail command. Word>Send via Mail results in no action at all, as if you have not given a command. For all purposes it reacts exactly like the Export>Word command to these test, just without the error dialog.)
I'm guessing that there is some corruption with my document that didn't show itself until the v4.3 update.