Home Quicken for Windows Errors and Troubleshooting (Windows)

Unexpected Error when adding transaction

ceschnurrceschnurr Member ✭✭
I've been a Quicken user for 15 years.  I am currently using Quicken Starter on computer with Windows 10.  Today, I started getting an Unexpected Error whenever I add, accept, or change any transaction.  

Comments

  • splashersplasher SuperUser ✭✭✭✭✭
    edited October 2018
    Unless you tell us the error, screenshot would be nice, it is impossible for anyone to help you.
    -splasher  using Q since 1996 -  Subscription  -  Win10
    -also older versions as needed for testing
    -Questions? Check out the  Quicken Windows FAQ list

  • thecreatorthecreator SuperUser ✭✭✭✭✭
    edited December 2018
    Hi @ ceschnurr ,

    See this Article:  https://getsatisfaction.com/quickencommunity/topics/add-your-quicken-information-to-your-posts-plus-...

    Have you ever scanned the File System for File System Errors?

    Comment Back with additional information.

  • ceschnurrceschnurr Member ✭✭
    edited October 2018
    My Canadian software was up to date, but a similiar post (https://getsatisfaction.com/quickencommunity/topics/quicken-keeps-crashing-when-i-am-downloading-tra...
    suggested I download the Mondo file.
    This seemed to fix my problem.

    Sorry for my vague post, but there was no error number or description.  The error message was titled 'Unexpected Error' and asked for my description of what I was doing at the time of the error to report to Quicken. I can no longer recreate iit for a screen shot.

    Thanks
  • Unknown Member
    edited September 2018
    ceschnurr said:

    My Canadian software was up to date, but a similiar post (https://getsatisfaction.com/quickencommunity/topics/quicken-keeps-crashing-when-i-am-downloading-tra...
    suggested I download the Mondo file.
    This seemed to fix my problem.

    Sorry for my vague post, but there was no error number or description.  The error message was titled 'Unexpected Error' and asked for my description of what I was doing at the time of the error to report to Quicken. I can no longer recreate iit for a screen shot.

    Thanks

    Just for the record.  "Unexpected Error" means that Quicken crashed and the crash handler caught the error, and then is going to send information about that crash to Quicken Inc.

    That is the reason there is no error code, it is basically an internal error and until someone actually debugs the problem, there isn't any real way to say what happened.

    The best you can do is say what you were doing at the time, and the "might" lead to what caused the problem.  And it might not.  For instance on the US side they made changes recently that have caused lots of these kinds of crashes and they seem to be related to Online Bills (a feature I don't believe the Canadian version has).  So people posts go like I was updating my bills, or I just ran One Step Update, and Quicken crashed.

    I might add that if Quicken crashes on One Step Update, one idea to try to track down what is causing it, is to deselect things to update, and see if there is just one feature or even financial institution that is causing the problem.

    Past that if there is any fix other than say avoiding the feature that is causing the crash, then it most likely going to be doing just what you did or maybe trying to see if your data file got corrupted.
  • Unknown Member
    edited September 2018
    ceschnurr said:

    My Canadian software was up to date, but a similiar post (https://getsatisfaction.com/quickencommunity/topics/quicken-keeps-crashing-when-i-am-downloading-tra...
    suggested I download the Mondo file.
    This seemed to fix my problem.

    Sorry for my vague post, but there was no error number or description.  The error message was titled 'Unexpected Error' and asked for my description of what I was doing at the time of the error to report to Quicken. I can no longer recreate iit for a screen shot.

    Thanks

    Oh one more thing.  It is very important that you state what version of Quicken you are using.  Just knowing that you are using the Canadian version would point to even though your problem looks like the one everyone is posting about, it can't be exactly the same because that was caused by an update that the Canadian version didn't get.

    Every problem should include the version number (full version number or Rxx version and state it is Canadian or US) and if it is Windows or Mac.
This discussion has been closed.