Moneydance 2022.1 (4059) Will Not Start

FuzzyJohn's Avatar

FuzzyJohn

27 Oct, 2021 04:30 AM

Windows 7 32-bit VM fully updated.
Moneydance 2022.1 build 4059
Moneydance data file is password protected.

After upgrading from Moneydance 2022.1 build 4058 (which ran without a problem) to 2022.1 build 4059 Moneydance will not start.
I am never asked for the data file password.
The Moneydance screen does not appear.
If I delete the errorlog.txt file a new one will be created but nothing else happens.
I attached the errorlog.txt file that was created the first time I ran Moneydance 2022.1 build 4059 after the upgrade.

I have tried the upgrade 4 times.

  1. Support Staff 1 Posted by Maddy on 27 Oct, 2021 10:15 AM

    Maddy's Avatar

    Hi,

    We are sorry to hear about the problem you have encountered.

    Could you try removing the extension Moneyforesight?
    To do so, you should navigate to Local Disk (C:)>Users>Yourname>.moneydance>fmodules. Then select Moneyforesight and delete it.

    You may want to reboot your computer after that and try to launch Moneydance again.

    --
    Maddy, Infinite Kind Support

  2. 2 Posted by Stuart Beesley ... on 27 Oct, 2021 10:18 AM

    Stuart Beesley - JUST A FELLOW USER and Toolbox ‘guy’'s Avatar

    If that doesn't work, you might need a manual edit of config.dict....

    Look for config.dict. With MD closed, make a backup of this file and then edit config.dict with a text editor...

    Look for:
    moneyforesight

    There will be sections for
    "gui.home.unused" = ( ... ) "gui.home.lefties" = ( ... ) "gui.home.righties" = ( ... )

    delete: "com.moneydance.apps.md.view.gui.moneyforesight.homepage.reminderreview"
    and
    "com.moneydance.modules.features.com.moneydance.apps.md.view.gui.moneyforesight.moneyforesight.homepage" from lefties and righties... Be careful to leave the closing bracket )

    save

    restart MD

    (not support, just a fellow user)

  3. 3 Posted by FuzzyJohn on 27 Oct, 2021 12:26 PM

    FuzzyJohn's Avatar

    Thank you Maddy and Stuart. Unfortunately neither of your suggestions worked.

    Maddy,
    Again I installed Moneydance 2022.1 build 4059 Windows 32-bit over a working build 4058.
    I checked the fmodules folder prior to the installation and there was no Moneyforesight extension present. Only findandreplace and updater.
    After installing build 4059 but before 1st run again the Moneyforesight extension was not in the fmodules folder.
    Ran the program for the first time and it failed to start.

    Stuart,
    I did the manual edit of config.dict as you suggested. The program still did not start.
    Sidenote: Before I posted my first message yesterday I did rename config.dict. The program created a new one but still did not start.

    I am attaching a newly created errorlog.txt file generated after following Stuart's suggestions.

    Thanks!

  4. 4 Posted by FuzzyJohn on 27 Oct, 2021 12:50 PM

    FuzzyJohn's Avatar

    I tried installing build 4059 in a clean Windows 7 32-bit VM (as a first time install) with the same result of not starting.
    Build 4059 works OK under Ubuntu.

  5. 5 Posted by Stuart Beesley ... on 27 Oct, 2021 01:12 PM

    Stuart Beesley - JUST A FELLOW USER and Toolbox ‘guy’'s Avatar

    …. And is there any error message or crash report at all?

    Can you run the app from the command line with the -d parameter?

    What memory is allocated to the VM?

  6. 6 Posted by FuzzyJohn on 27 Oct, 2021 02:06 PM

    FuzzyJohn's Avatar

    With the same clean Windows 7 32-bit VM (2 GB memory allocated) first time installation of Moneydance 2022.1 build 4059, running moneydance -d from the Command Prompt while in the C:\Program Files\Moneydance folder produces the same result. Nothing related to Moneydance comes up on the screen. This being the first time Moneydance is run the .moneydance folder is created. This folder contains 5 subfolders (archive, Documents, fmodules, python and tmp) all empty and a ui_properties.css file.
    This time the config.dict and errorlog.txt files were not created.
    No error message came up on the screen.

  7. 7 Posted by FuzzyJohn on 27 Oct, 2021 02:18 PM

    FuzzyJohn's Avatar

    Just ran another test, this time under a clean Windows 7 64-bit VM with 2 GB memory allocated and in this environment Moneydance starts normally. Looks like the problem is the 32-bit Moneydance and/or the new Java 17.

  8. 8 Posted by Stuart Beesley ... on 27 Oct, 2021 02:21 PM

    Stuart Beesley - JUST A FELLOW USER and Toolbox ‘guy’'s Avatar

    ... sorry, I am at a bit of a loss with that if you are getting no errors or messages at all....

  9. 9 Posted by Stuart Beesley ... on 27 Oct, 2021 02:23 PM

    Stuart Beesley - JUST A FELLOW USER and Toolbox ‘guy’'s Avatar

    which install package did you run? The 32-bit or the 64-bit?

  10. 10 Posted by FuzzyJohn on 27 Oct, 2021 02:34 PM

    FuzzyJohn's Avatar

    In the 64-bit VM I installed the 64-bit package. That is the one that worked.
    I just reset the clean Windows 7 64-bit VM and installed the 32-bit package and guess what... it didn't start.
    I guess that for now, maybe until the next build, I'll stick with build 4058. I prefer it running in a 32-bit environment because the VM is faster than 64-bit.

  11. 11 Posted by Stuart Beesley ... on 27 Oct, 2021 03:03 PM

    Stuart Beesley - JUST A FELLOW USER and Toolbox ‘guy’'s Avatar

    What processor are you running? Will it support 32-bit code...? Has 32-bit MD ever worked on your 64-bit setup?

  12. 12 Posted by FuzzyJohn on 27 Oct, 2021 03:19 PM

    FuzzyJohn's Avatar

    What I am currently using with build 4058 is a 32-bit Windows VM with the 32-bit Moneydance package. This worked with all past builds since I started using Moneydance.
    This VM runs on a QNAP TS-451+ NAS under Virtualization Station. The QNAP NAS emulates the Intel Core i7 (Nehalem Class Core i7). The QNAP NAS supports both 64-bit and 32-bit operating systems and never had a problem so far. The only thing is, as I mentioned, the 64-bit OS runs a little slower than the 32-bit OS, so if I have a choice I use 32-bit.
    I mentioned in my previous message that I had tried installing the 32-bit package under the 64-bit Windows 7. While the installation completed, the 32-bit Moneydance did not start in 64-bit Windows 7. It should have but it didn't. The 64-bit package installed in 64-bit Windows 7 and runs OK.

    To make matters a little more muddy than they are I also tried the 32-bit Moneydance package in my Windows 11 Hyper-V with a 32-bit Windows 7 installation. Same result... did not start.

    In all these configurations Moneydance build 4058 and earlier (32-bit package) always worked. So I guess the problem is what changed from build 4058 to build 4059 in the 32-bit package. The biggest change as it looks to me, is Java 17.

  13. Support Staff 13 Posted by Sean Reilly on 27 Oct, 2021 08:25 PM

    Sean Reilly's Avatar

    Hi John,

    Would it be possible to try running Moneydance from a command prompt, passing the -d parameters? Can you open a command prompt (usually by clicking the Start button and typing "cmd" and then pressing return) and type the following two lines?

    cd "c:\Program Files\Moneydance"
    Moneydance.exe -d
    

    That should print extra debugging information directly to the command prompt window that you can hopefully copy and paste or screen shot into a response?

    Thanks!
    Sean

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

  14. 14 Posted by FuzzyJohn on 27 Oct, 2021 08:54 PM

    FuzzyJohn's Avatar

    Hello Sean,

    Tried what you asked and nothing happens. Here is a screenshot of the command prompt window after I run the moneydance.exe -d command. This is under Windows 7 32-bit with the 32-bit package of Moneydance 4059 installed. The Moneydance application did not start.

    As a test I reset the Windows 7 32-bit VM and I installed the 32-bit package of Moneydance 4058. The I ran the moneydance.exe -d command and the command prompt window behaved the same way as with build 4059. There was no extra debug information showing in the command prompt window. However with the 4058 package the Moneydance application started and took me thru the first time run steps.

  15. Support Staff 15 Posted by Sean Reilly on 27 Oct, 2021 09:03 PM

    Sean Reilly's Avatar

    Hi John,

    OK, I forgot that moneydance detaches from the command line when running on windows, so I shouldn't have expected any output there.

    When you say you're running in a VM, is there a reason for that? Would it be possible to run moneydance outside of the VM?

    Thanks,
    Sean

  16. 16 Posted by FuzzyJohn on 27 Oct, 2021 09:15 PM

    FuzzyJohn's Avatar

    It is a matter of personal preference and extra layer of protection for the data files. I prefer not to have financial data on a computer that is used for Internet browsing. And I would like to continue this way.

    As I mentioned in the other posts Moneydance 64-bit build 4059 will run on Windows 7 64-bit and on Linux Ubuntu 64-bit. It is only Moneydance 32-bit build 4059 that does not run on either Windows 7 32-bit or Windows 7 64-bit. And that is only build 4059. Builds 4058 and earlier back to Moneydance 2020 have no problem running on Windows 7 32-bit.

  17. 17 Posted by -Kevin N. on 27 Oct, 2021 09:25 PM

    -Kevin N.'s Avatar

    Hi Sean,

    Win 7 32-bit not using a VM
    4059 32-bit

    There is an error log created in 'C:\Program Files\Moneydance', I've attached it here.

    -Kevin N.

  18. 18 Posted by FuzzyJohn on 29 Oct, 2021 04:44 PM

    FuzzyJohn's Avatar

    I guess that at least for now I will have to switch to the 64-bit package of Moneydance and Windows 7 64-bit.

    -Kevin N: You gave me a glimmer of hope but that didn't last long. No such error log on my Windows 7 32-bit installation.

  19. 19 Posted by dwg on 29 Oct, 2021 08:03 PM

    dwg's Avatar

    FWIW the 32 bit kit is not working on Windows 64 bit either. Build 4049 moved to Java 17 so there may be a problem there.

  20. 20 Posted by -Kevin N. on 30 Oct, 2021 01:09 AM

    -Kevin N.'s Avatar

    Hi FuzzyJohn,

    The error log only generated (for me) when I set vmoptions to 1MB. With vmoptions set to 2MB, there was no error log created.

    There's no mention of 32-bit Windows work in the 4060 change log. : (

    -Kevin N. (not a member of MD support)

  21. 21 Posted by FuzzyJohn on 30 Oct, 2021 01:13 AM

    FuzzyJohn's Avatar

    I tested the 32-bit package of build 4060 earlier today and it's the same situation.

  22. 22 Posted by FuzzyJohn on 15 Jan, 2022 03:50 AM

    FuzzyJohn's Avatar

    Is there a resolution on this issue?
    I see that Windows 32-bit packages are still provided as of build 4063 but they don't work (at least in my case).

  23. 23 Posted by dwg on 15 Jan, 2022 04:30 AM

    dwg's Avatar

    I last tried build 4062 and that also did not work. There is nothing in the change log that would indicate that there would be any difference in build 4063.

  24. 24 Posted by FuzzyJohn on 15 Jan, 2022 04:38 AM

    FuzzyJohn's Avatar

    Thanks @dwg. Understood... I was just thinking that new 32-bit builds are continuing to be released without any mention of Java 17 issues in the List of Change. On the other hand, this would not be the first software that is released with known bugs or issues.

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:

»

Already uploaded files

  • errlog.txt 1.17 KB

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

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