EndNote X6 "EndNote is not responding. Error = -1712" Word Mac

EndNote EndNote How To
10

Well…  that certainly seems odd.

That search, which should function the same externally to everyone, should bring up the article.

Instead, we’ll dispense with links, and I’ll just post it’s contents here…

There is a known issue with OSX 10.8.2 that will cause Cite While You Write to either freeze while formatting or give you a -1712 (time out error). While a bit technical, this is what is currently “known” about the problem:

  • The problem is specific to the OS X 10.8.2 update specifically, not EndNote or Word.
  • The problem is directly related to the use of the AESendMessage/AESend functions used with typeApplicationBundleID or typeApplSignature for the target type.
  • Using typeKernelProcessID for the target type still works. However EndNote uses the bundle signature.
  • Killing the appleeventsd daemon fixes the problem temporarily (Antonin Hildebrand discovered this fact). This can also be done by logging out then logging back in.

Note: We recommend those experiencing this issue should contact Apple directly. This can help prioritize the effort. Here is the link to contact Apple : http://www.apple.com/feedback/macosx.html

To kill the appleeventsd process directly please do the following:

  1. If EndNote or Word are stuck, restart both applications.
  2. Go to Applications : Utilities.
  3. Run the Activity Monitor found there.
  4. Set the “Show” option at the top of the window to All Processes (not My Processes which is default). 
  5. Click the column header “Process Name” to sort alpabetically.
  6. Highlight the appleeventsd process.
  7. Click the “Quit Process” button.
  8. Try using EndNote or Word now.

The above indicates that the problem is likely to be some kind of stale cache used by appleeventsd for mapping bundle ids and 4-letter application signatures to process ids. It also indicates that triggering this problem involves relaunching the target application (in order to give it a new process id). This has been confirmed by a user (Torsten Grust) in the context of MailMate/SpamSieve.

More information can also be found on the following pages:


http://openradar.appspot.com/12424662
http://brian-webster.tumblr.com/post/32830692042/a-workaround-for-aesendmessage-hanging-on-os-x-10-8-2
http://mjtsai.com/blog/2012/10/04/aesendmessage-bug-in-mac-os-x-10-8-2/
And many others.

I do hope this proves useful.

Thanks!

Steve