tag:infinitekind.tenderapp.com,2009-01-14:/discussions/problems/1140-spinning-ball-of-death-aieeeeInfinite Kind: Discussion 2018-10-18T13:55:45Ztag:infinitekind.tenderapp.com,2009-01-14:Comment/16053712010-05-05T23:51:25Z2010-05-05T23:51:25ZSpinning ball of death! Aieeee!<div><p>Here's what I would try (except I don't know how this works on
MacOSX). Start Moneydance with a non-existing file from a command
line or RUN command. Like this (from a Linux shell): <strong>md
nosuchfile</strong>. This should start it up without trying to load
the last file. You can create a new file now (and see what version
you have). If MD starts and runs OK on a new file, you may have a
damaged data file. Try your backup files. If MD does not start on a
new file, you either have a messed up preferences file
(config.dict) or a broken installation.</p></div>ljbtag:infinitekind.tenderapp.com,2009-01-14:Comment/16053712010-05-13T19:50:05Z2010-05-13T19:50:05ZSpinning ball of death! Aieeee!<div><p>JWC,</p>
<p>Are you still experiencing the spinny ball of death? Please do
let me know, and I would suggest trying to update to 748, available
<a href=
"http://moneydance.com/trac/wiki/Moneydance2010Beta">here</a>. Then
at least we'll all know what version is crashing. This will also
not cause you to lose any data (unless of course the file is
already corrupted, in which case you should go into your
backups).</p>
<p>Please let me know how I can be of further assistance,</p>
<p>Angie Rauscher<br>
Moneydance Support</p></div>Angie Rauschertag:infinitekind.tenderapp.com,2009-01-14:Comment/16053712010-06-08T18:44:14Z2010-06-08T18:44:14ZSpinning ball of death! Aieeee!<div><p>Angie,</p>
<p>Thanks for following up. I am using 751 now. I basically just
went back and opened an auto-backup, and things started working
again. I may have lost some data but I decided to suck it up rather
than muck with the terminal.</p>
<p>I also turned off encryption, but I hope that wasn't key,
because I hate entering all those passwords all the time, so I'm
about to turn it back on. But for now this issue seems fixed.</p></div>jwc