![]() ![]() ![]() The beta release will replace your current version of EndNote X6.EndNote X6.0.1 must already be installed on your Mac and you must be running OS X 10.8.2.No other updates or new functionality will be included in this release.īefore participating in beta testing, you should understand the following: We are currently beta testing a release designed to specifically address the “EndNote is not responding : error -1712” when using EndNote X6 with Word 2011 on OS X 10.8.2 Mountain Lion. I’m sure if this issue occurred on the Windows platform it would be dealt with promptly. Once the refund is available I can move on to a competitors product that is designed TO WORK WITH MAC OSX.Ĭlearly the MAC version is an afterthought and not your priority concern. Your are essentially selling a problem/non-working product right out of the gate. If there is truly no solution except sit and wait for Apple to resolve the problem then I suggest everyone on this forum or anyone experiencing this issue demand a refund based on the simple fact the the software does not perform as described and advertised/marketed. Therefore I suggest Thomson Reuters gets their team of technical experts, which we all know you have as you are quite a large corporation, and get off your high horse and provide an acceptable solution. As I have purchased a hardcopy of this software there is probably no possible way that I can get a refund from my local supplier (software nowadays is non-refundable). As a customer I would appreciate a realistic and permanent solution to this issue and not a temporary work around. MAC OSX is not designed in mind to work with your software. I don’t think this is an acceptable response from a third party supplier as your product is “DESIGNED” to work with MAC OSX and not vice versa. More information can also be found on the following pages: This has been confirmed by a user (Torsten Grust) in the context of MailMate/SpamSieve. It also indicates that triggering this problem involves relaunching the target application (in order to give it a new process id). 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. Click the column header “Process Name” to sort alpabetically.Set the “Show” option at the top of the window to All Processes (not My Processes which is default).If EndNote or Word are stuck, restart both applications.To kill the appleeventsd process directly please do the following: Note: We recommend those experiencing this issue should contact Apple directly. This can also be done by logging out then logging back in. Killing the appleeventsd daemon fixes the problem temporarily (Antonin Hildebrand discovered this fact).However EndNote uses the bundle signature. Using typeKernelProcessID for the target type still works.The problem is directly related to the use of the AESendMessage/AESend functions used with typeApplicationBundleID or typeApplSignature for the target type.The problem is specific to the OS X 10.8.2 update specifically, not EndNote or Word.While a bit technical, this is what is currently “known” about the problem: 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). ![]() Instead, we’ll dispense with links, and I’ll just post it’s contents here… That search, which should function the same externally to everyone, should bring up the article. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |