4 Replies Latest reply: Aug 28, 2014 11:39 PM by dzegna
suzannehhsmith Level 1 Level 1 (0 points)

Help.  Pages suddenly won't open.   Shows error -1712.   What's happened?


MacBook Pro, Mac OS X (10.7.4), Pages error -1712
  • Peggy Level 8 Level 8 (38,505 points)

    It's not easy searching for the meaning of error codes, especially negative ones. The best I could find on this was some type of resource error.

    -1712 is apparently a "timeout" error, meaning that some program tried to do something, and it couldn't complete the task and so it "timed out". This would likely occur if you are trying to access some external resource that isn't available.

    I suggest trying several things in this order.

     

    Quit & restart Pages

    Use Disk Utility to repair permissions

    Restart your Mac

     

    Peggy_sig.png

  • PeterBreis0807 Level 7 Level 7 (32,520 points)

    …and give more detail.

     

    e.g. What you were doing at the time, what version of Pages etc.

     

    Peter

  • Dale Gillard Level 5 Level 5 (4,365 points)

    As Peggy notes, a -1712 error is a timeout error for Apple Events. Often your Mac sends an Apple Event to a program asking it to start (when you double click an icon in the Finder) or to open a document (when you double click a document icon in the Finder).

     

    Can you explain to us what action you're trying that causes this timeout error? And as Peter requests, please tell us the version of Pages you're using.

  • dzegna Level 1 Level 1 (0 points)

    Open Activity Monitor located in /Applications/Utiliites

    Select 'View' then 'My Processes' in the menubar across the very top of your screen.

    Type Pages in the search field top right corner of the Activity Monitor window.

    Now select the application Pages (it should say 'not responding') and click the force quit button that looks like a stop sign with an x in it.

    >You should now be able to relaunch Pages.

     

    Force Quitting within Activity Monitor is a quick and efficient way to handle most Applications "Not Responding" or seeming not to open with error -1712.

    Just be aware that you may lose any unsaved work by force quitting an application.

    It can also work great for an Application that "Freezes" and is giving the spinning beach ball beachball of death.gif