Moneydance Upgrade Results in Progressively Inaccurate Balances

Kyle Sullivan's Avatar

Kyle Sullivan

22 Sep, 2019 12:52 PM

Hi,
I've been a longtime user (Moneydance 2011) and most recently hold a MD 2017 license (2017.6). I've tried to upgrade to MD 2019 ( 2019.3) so that I can use the dark mode and get the syncing and the mobile app running. However, when I try to upgrade, the data file gets corrupted and my checking balance greatly increases each time I open the upgraded application.

I've tried a few different methods to upgrade, like keeping the data file in place, generating a new data file and doing an import of a backup, etc. Same result. Attaching a screenshot of what it looks like. In order, 2017.6 -> 2019.3 (first open) -> 2019.3 (second open). Notice the great (and growing!) difference in the checking balance and small difference in savings balance.

Anyone seen this?? I could use some help here.

MacOS Mojave
Version 10.14.6

  1. 1 Posted by derekkent23 on 22 Sep, 2019 01:53 PM

    derekkent23's Avatar

    I am not support staff, just a user.

    Have you tried updating 2017.6 to 2017.10 first?
    Make sure your data set is no your hard drive not external say in the cloud.
    2017.10 can be downloaded from https://infinitekind.com/download_2017
    Then FILE (MONEYDANCE on Mac) – EXPORT BACKUP.

    Then upgrade to 2019.3.

    Hope this help.

  2. 2 Posted by Kyle Sullivan on 22 Sep, 2019 02:14 PM

    Kyle Sullivan's Avatar

    Hi, thanks for your response.

    When I upgrade to 2017.10 from 2017.6, same result with ballooning checking
    balance.

    Kyle

  3. 3 Posted by derekkent23 on 22 Sep, 2019 02:33 PM

    derekkent23's Avatar

    I am not support staff, just a user.

    And you data set is on your hard drive?
    Are you syncing to another device, mobile phone?
    What is you computer operating system?
    Can you post your Moneydance errlog.txt file.

  4. 4 Posted by Kyle Sullivan on 22 Sep, 2019 09:46 PM

    Kyle Sullivan's Avatar

    Thanks for helping here Derek. Some answers here:

    -The data set resides on my HDD.
    -I'm not syncing to anything (although I want to!)
    - MacOS Mojave 10.14.6
    - Error log attached (I had to Time Machine back since the error log is overwritten when I reverted back to 2017.6.

  5. 5 Posted by derekkent23 on 23 Sep, 2019 07:37 AM

    derekkent23's Avatar

    I am not support staff, just a user.
    Hi Kyle

    To be of any help the error log needs to be for 2017.10 or 2019 when the problem occurs.
    Make sure you have a backup of your data set sullivan2015.moneydance in a safe place before you update to 2019.
    Open Moneydance 2019. Check the problem has occurred. Make sure you shut down Moneydance normally before you copy the errlog.txt file to post.

    By the way can you determine what transaction get added each time you open Moneydance that would explain the account totals increasing? Are they duplicates of existing transactions or something else? Are you using Direct Connect set to update automatically on Moneydance opening?

  6. 6 Posted by dwg on 23 Sep, 2019 08:39 AM

    dwg's Avatar

    I'm a fellow user.

    The posted error log in incomplete but it does highlight that an attempt has at least been made to set up syncing:

    dropbox folder should be at /Users/kylesullivan/Dropbox and
    exists=true
    base sync folder: /Users/kylesullivan/Dropbox/.moneydancesync
    dropbox folder should be at /Users/kylesullivan/Dropbox and exists=true
    base sync folder: /Users/kylesullivan/Dropbox/.moneydancesync
    base sync folder: /Users/Kyle/Dropbox/Kyle's Files Dropbox/Financial/Moneydance

    I would be inclined to make sure syncing is disabled and that any Moneydance data in the Dropbox folder is removed.

  7. 7 Posted by derekkent23 on 23 Sep, 2019 09:26 AM

    derekkent23's Avatar

    Hi dwg

    When I create a completely new data set on a windows computer I get the following lines in the console log.

    dropbox folder should be at C:\Users\derek\Dropbox and exists=true
    base sync folder: C:\Users\derek\Dropbox.moneydancesync
    dropbox folder should be at C:\Users\derek\Dropbox and exists=true
    base sync folder: C:\Users\derek\Dropbox.moneydancesync

    They don’t indicate that the data set has ever been synced, just that Dropbox client is installed.
    I think the only was to be sure is to see if the folder “.moneydancesync” has been created in Dropbox that contains an alphanumeric folder which has a text file mdsyncinfo.txt in which the data set is named.

    Am I missing something?

  8. 8 Posted by dwg on 23 Sep, 2019 11:36 AM

    dwg's Avatar

    hi Derek,

    You are probably not missing anything.

    Over the time I have been working with Moneydance there have been many changes including what is logged so I may be mistaken here on what the log file is saying.

    I'm of the mindset that if syncing is not being used then Dropbox should not be checked at all, I suspect Sean would disagree with me :)

    Des

  9. 9 Posted by Kyle Sullivan on 23 Sep, 2019 05:44 PM

    Kyle Sullivan's Avatar

    Thanks guys. I'll try some things when I get home. Regarding derekkent23's question to which transactions may be causing the difference: I don't know. What I do know is that there are many more uncleared transactions from much earlier dates. No particular trend noticed.

  10. 10 Posted by Kyle Sullivan on 27 Sep, 2019 08:20 PM

    Kyle Sullivan's Avatar

    If finally got a chance to try this again derekkent23, I think this is more interesting err log.txt file.

  11. 11 Posted by derekkent23 on 27 Sep, 2019 09:14 PM

    derekkent23's Avatar

    I am not support staff, just a user.
    Hi Kyle

    I assume you are still seeing the problem, each time you open 2019 the checking balance greatly increases? Please confirm.

    This one going to need supports help, maybe they can see something in the errlog.txt that I can’t.

    The section starting “java.util.ConcurrentModificationException” may be an issues.

    The section starting “Compressing 242 txn file(s) to 'archive/201811.mdtxnarchive'” is probably part of the process introduced in 2019 to reduce the data set size by compressing the individual “.tnx” files into a single “mdtxnarchive” file and then deleting the individual “tnx” files.

    This happens at regular interval but the first time you close 2019 there a lot of “tnx” files to deal with.

    If support don’t pick this one up, I will post a link to your thread to Sean the Moneydance Software developer in the hope he will take a look, no guarantees.

  12. 12 Posted by Kyle Sullivan on 27 Sep, 2019 10:26 PM

    Kyle Sullivan's Avatar

    Hi Derek,
    Thanks for looking at it. Yes, the issue still exists with the ballooning checking account balance.

    I reverted back to 2017.6 and all's good again.

    Do you recommend I submit a support ticket?

  13. 13 Posted by dwg on 27 Sep, 2019 10:51 PM

    dwg's Avatar

    I'm a fellow user.

    I do not see anything standing out in the log file, as Derek says the cleaning up of archive files is not something that stands out.

    Having tested upgrading from MD2017 to MD2019 many times I have not seen anything inherently wrong in the process - and in any case the low level data structures are fundamentally the same which says to me the probability of an issue should be low.

    I'm more inclined to think there is something in the data that is triggering a problem for the latter version and that is an issue that support will need to pick up.

  14. 14 Posted by derekkent23 on 28 Sep, 2019 06:39 AM

    derekkent23's Avatar

    I am not support staff, just a user.
    Hi Kyle

    By posting on this site you are requesting help and help comes via other users or support whoever reads the post first. If the user can’t help then support should step in.

    SUPPORT PLEASE TAKE A LOOK AT THIS THREAD, THANKS.

    Hope this helps.

  15. Support Staff 15 Posted by Sean Reilly on 02 Oct, 2019 08:30 AM

    Sean Reilly's Avatar

    Hi Kyle,

    I'm sorry about the lack of official response on this problem so far. I think this may be an issue that we've seen with a few others. I've created a script that will fix this if it turns out to be the same problem. Could you perform the following steps?

    1. Open your data file in Moneydance 2019
    2. Select the Window -> Show MoneyBot Console menu
    3. Click the Open Script button and select the downloaded script file (reset_relative_currencies.py)
    4. Click the Run Script (or just Run) button
    5. Give it a few seconds to load and run
    6. Copy and paste the results into a response to this thread?

    Thanks!
    Sean

    --
    Sean Reilly
    Developer, The Infinite Kind
    https://infinitekind.com

  16. 16 Posted by Kyle Sullivan on 02 Oct, 2019 11:59 AM

    Kyle Sullivan's Avatar

    Thanks Sean. I'l give it a try (likely this weekend) and respond with feedback/results. Appreciate it.

  17. 17 Posted by Kyle Sullivan on 06 Oct, 2019 11:50 PM

    Kyle Sullivan's Avatar

    Hi Sean,
    Here's the text file after running the script. Let me know if there's some next steps here. Checking and savings still show inaccurate balances.

  18. Support Staff 18 Posted by Sean Reilly on 09 Oct, 2019 08:42 AM

    Sean Reilly's Avatar

    Hi Kyle,

    Thanks for your message and I'm sorry for taking so long to follow-up with this. The output of the script looks fine and doesn't reveal any errors. One long shot possibility is that maybe the "balance type" preference setting has changed? That would likely cause some balances to be displayed exactly the same as in 2017 but others to be different in 2019 even with no changes to the actual data. Can you check the setting for "Side Bar Balance Type" in your Moneydance preferences? Or you could click the underlined balance number at the bottom of any of your registers to show all of the different kinds of balances (cleared, current, total, online, etc) to see if any of them match up with what you were seeing in 2017.

    Thanks,
    Sean

    --
    Sean Reilly
    Developer, The Infinite Kind
    https://infinitekind.com

  19. Support Staff 19 Posted by Sean Reilly on 09 Oct, 2019 09:00 AM

    Sean Reilly's Avatar

    Hi Kyle,

    I'm sorry, I missed the part from your message where you mention the balances are continuing to change on subsequent runs of MD2019. In this case I think it's probably necessary to do a screen sharing session so that we can get to the bottom of this as quickly as possible.

    If you're ok with doing a screen sharing session can you let me know what dates/times you might be available as well as your time zone?

    Thanks,
    Sean

    --
    Sean Reilly
    Developer, The Infinite Kind
    https://infinitekind.com

  20. 20 Posted by Kyle Sullivan on 09 Oct, 2019 10:42 AM

    Kyle Sullivan's Avatar

    Hi Sean, I'm on ET time here outside of Boston, MA.

    Screensharing works for me. Can we work this out privately? (I'm not sure if this is public or not). Emailing me at the kyle-at-kylesullivan.com works. Or another recommended way to communicate, e.g. private message?

  21. 21 Posted by Kyle Sullivan on 26 Oct, 2019 11:02 PM

    Kyle Sullivan's Avatar

    Just want to publicly thank Sean who got on the phone with me for over 2 hours to drive home a resolution to the complex problem I was having. Thank you Sean. It's rare to see the personal support and dedication in products today. I liked Moneydance before, but now I love it!

  22. 22 Posted by dwg on 27 Oct, 2019 01:57 AM

    dwg's Avatar

    I'm a fellow user.

    It may prove to be useful to post what the problem was and what the solution is in case it should come up again with another user. This sort of knowledge builds up the base of information that is out there.

  23. 23 Posted by derekkent23 on 27 Oct, 2019 08:24 AM

    derekkent23's Avatar

    Hi Kyle

    As a participant to this thread I would also be interested.

  24. 24 Posted by Kyle Sullivan on 27 Oct, 2019 12:26 PM

    Kyle Sullivan's Avatar

    Absolutely, I'll try my best. Sean Reilly may have to come in and explain better. Here's a summary of the situation: After upgrading from 2017, some old deleted reminders returned. The ones that had "auto-commit" enabled, created transactions from years past into my checking account, throwing off the balance. Sean acknowledged that he's never seen it before, and I'll let him comment on the software functionality issue that caused this, but it's clearly limited since I may be the only user to have seen this.

    The resolution was to wipe out these zombie reminders and their associated new transactions (easy to find since they were uncleared). Now I'm on MD 2019 and all's good.

  25. 25 Posted by derekkent23 on 27 Oct, 2019 01:17 PM

    derekkent23's Avatar

    I am not support staff, just a user.
    Hi Kyle

    Interesting.
    Thanks for the explanation.

    Hope this helps.

  26. System closed this discussion on 26 Jan, 2020 01:20 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac