Went through the steps below and tried to install the version I downloaded from the link below but it didn't work so here attached is the .log file. The log file may be pointing to issues with Java? I'm running Java 6
On Thursday, March 14, 2019, 12:45:30 AM PDT, derekkent23 <[email blocked]> wrote:
I don’t see the i4j_nlog_3.log attached indicated in one of the messages in your first post at C:\users\Doug\AppData\Local\Temp\i4j_nlog_3.log
The attachment in you last post, as you say, indicates you have java 6 installed.
Moneydance 2019.2(1860) uses an embedded version of Java, Java: 11.0.2 (Oracle Corporation). This is installed as part of the installation when you run Moneydance_windows_amd64.exe
Moneydance, including the embedded java would be installed at C:\Program Files\Moneydance\ Java is in the folder \lib
Its only used by Moneydance. A separate version of java is not required to run Moneydance.
On my window 7 computer and two windows 10 computers I have Java 8 installed to support another application without any issues. I can’t say that uninstalling your Java 6 would help but may be worth a try. I am not an expert on Java but thought Java 6 is old, not supported and thus could be a security risk?
Here attached is the "log" file, please let me know if this helps. This log file was generated from the downloaded .exe version you recommended below. I deleted all other previous "log" files so when I tried launching this latest .exe download, I would get a clean _1 file. I'll await your response - - thanks - -
On Friday, March 15, 2019, 2:24:18 AM PDT, derekkent23 <[email blocked]> wrote:
Sean Reilly on 18 Mar, 2019 09:49 AM
Thank you for sending the log files and such complete information. As Derek mentioned the currently installed version of java shouldn't make any difference since moneydance bundles and uses its own version of java.
Can you confirm if your computer is 32 or 64 bit? Moneydance 2019 is limited to 64 bit computers, so if your computer is only 32 bit or if your Windows version is only 32 bit then it won't work. In most cases I've seen where people have 32 bit versions of windows installed their computer is actually 64 bit. If your computer is 32 bit or you wouldn't like to upgrade windows then the most recent version of Moneydance you'll be able to run on this computer will be 2017.10 which can be downloaded from here: https://infinitekind.com/download_2017
Sean Reilly on 18 Mar, 2019 11:19 AM
I missed the part where you say your computer and windows is 64 bit, but after some more research the messages in your log are indicative of a 32 bit platform being unable to load a 64 bit binary (the dll files mentioned). It would be great to completely confirm that. If that's definitely not the problem then maybe we could try a screen sharing session so that I could try to figure out the problem in real-time?
You screen shot does not indicate that you have Windows 7 Service Pack 1 installed. It is my understanding that SP1 is a requirement for Java 11. This may or may not have an impact on the installation.
I updated Windows 7 to "SPI" (see below) and tried to load Moneydance and received the same ERROR (see below), so for your review, I've attached the latest "* _2.log" file which does read differently than the recent " *_1.log" file
On Tuesday, March 19, 2019, 1:29:38 AM PDT, derekkent23 <[email blocked]> wrote:
Can you confirm that under Control Panel > System and Security >Windows Update > Change Settings the dropdown Important updates is selected for “Install updates automatically (recommended)”. Also, to ensure your computer operating system is up to date clicked “Check for updates” under Control Panel > System and Security >Windows Update
Assuming you are up to date and dwg has no more thoughts, time to take up Sean’s, the Moneydance’s software developers offer of a screen share session to see if he can work out what the issue is. Perhaps suggest a set of days and times when you would be available, remembering he is in the UK.
I looked at the log again and the system information and there is nothing standing out to me, it looks pretty standard. Yet I think the problem is specific to this system for some reason that we are not seeing, perhaps it is as simple at Java 6 getting in the way perhaps it is something else.
I feel that Sean will need to do a screen sharing session, perhaps even doing something like an install in debug mode.
I'm certainly curious as to the cause as I haven't seen a problem like this before with Moneydance.