10-30-2012 04:01 AM
I did not much of testing, but killing this process seems to solve the problem for now despite the fact that it pops up again in the activity log after restarting Endnote (so this will be no definitive cure i guess).
As one can see this process seems to interfere with several other applications as well (simply google it). I am not an expert in this field but it would be interesting to know more about this process.
10-30-2012 02:24 PM
I had the same problem, but your fix seems to work. I have a MacBook Air 1.8 Ghz, 4 Gig RAM running 10.8.2. Previously, I was thinking about switching back to Endnote X5, as the speed issue was really serious.
Thanks --- but will there be a more permanent fix soon?
10-30-2012 02:26 PM
From a non-Mac user, this sound like Apple's problem, not Endnotes?
10-30-2012 04:17 PM
Does not help I keep getting this message:
EndNote is not responding. Error = -1712
for both x5 and version x6
Please assist
10-30-2012 06:23 PM
EMAH and matlinn,
I'm glad to hear the Activity Monitor steps have temporarily cured the slowness you've encountered. These steps should definitely be considered a temporary workaround until the issue is addressed by Apple. If anyone cares to read a technical description of this underlying bug within Apple's 10.8.2 operating system update, the following blog post outlines the issue:
http://brian-webster.tumblr.com/post/32830692042/a-workaround-for-aesendmessage-hanging-on-os-x-10-8...
Best Regards,
Jimmy M.
Customer Technical Support Representative Scientific
Thomson Reuters
Phone: +1 800 336 4474
ResearchSoft Product Support
thomsonreuters.com
10-30-2012 06:27 PM
endnoteuser20,
Sorry to hear this workaround didn't help. You may want to try calling our Technical Support department in order to see if you experience a different outcome when walking through the Activity Monitor steps with a Technical Support representative on the line with you:
EndNote Technical Support
800-336-4474
press 4, then 1
Another possible workaround involves temporarily logging out of your user account (which you should be able to do from the Apple drop-down menu) and then logging right back in. Of course, you would want to save any work before performing these steps.
Best Regards,
Jimmy M.
Customer Technical Support Representative Scientific
Thomson Reuters
Phone: +1 800 336 4474
ResearchSoft Product Support
thomsonreuters.com
10-31-2012 01:28 AM
killing appleeventsd did indeed get ENX6, Word 1.4.2.4 and Mac OS 10.8.2 behaving considering better. Was getting COM errors and today "error = -1712".
appleeventsd will relaunch at some stage though, after reboot for sure and in my experiments, by quitting Word and starting at again.
Are we waiting for an EndNote update or 10.8.3?
10-31-2012 09:20 AM
Hello, gchallis:
As you can see in the article that JimmyM posted earlier, the underlying issue is an Apple one, so I'm afraid Apple will have to address it. Here's that link again, in case you missed it the first time:
Or, simply Google "-1712 10.8.2" or "appleeventsd 10.8.2" to learn more about this Apple issue. There's a lot of information out there as the problem affects more than just Word or EndNote.
By the way, another effective means of quitting that process is simply to restart or log on and off your Mac. This solution may be simpler for some users, but both accomplish the same thing.
I hope this helps.
10-31-2012 11:49 AM
That worked very well. Is there a plan for an update so it doesn't need to be performed all the time?
10-31-2012 12:10 PM
As has been mentioned in earlier posts, this is an Apple bug so there will not be an EndNote update for this issue. We have brought this to Apple's attention through our development channels but I recommend those experiencing this should contact Apple directly too. This can help prioritize the effort. Here's the link - http://www.apple.com/feedback/macosx.html.
- Mathilda, the ENdNote team