Home → Problems →

importing .qif file makes moneydance disappear

• Edit

v+ik

17 Jul, 2024 03:13 AM

Version 2024.1 (5118)

The .qif files have been importing correctly in the past, and I haven't updated the program that generates them. But now when I try to import a particular .qif containing one transaction, Moneydance simply disappears/crashes/ends, and I have to restart it. The transaction has not been imported when I restart. How do I diagnose this?

1. 1 Posted by dwg on 17 Jul, 2024 03:38 AM

   

   I would open the QIF file and look at the contents. I would be looking for unprintable characters to start with and then anything else unusual.

   I would also look at the Moneydance error log after a crash to see if it sheds any light.

   You can also post a sample file that displays the problem for others to also test.

   It seems likely that it is something about the file.

   • Edit

2. 2 Posted by v+ik on 17 Jul, 2024 04:18 AM

   

   So I found the error log, eventually. It starts off like this (which doesn't appear to have information about me or my transaction). In fact, I don't see anything personal in the whole file, except for the Environment variables towards the end, and then the SYSTEM information is slightly personal about my computer, but I'd have no problem sharing that. After this header I'll put a sanitized version of the .qif file. But I see no unprintable characters there, or anything unusual (and looking via emacs, there are no unviewable characters). I have successfully imported similar transactions dozens if not hundreds of times, since using Moneydance, and earlier using Quicken.

   #

   A fatal error has been detected by the Java Runtime Environment:

   #

   EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffcce33a88e, pid=39884, tid=31716

   #

   JRE version: OpenJDK Runtime Environment Temurin-21.0.2+13 (21.0.2+13) (build 21.0.2+13-LTS)

   Java VM: OpenJDK 64-Bit Server VM Temurin-21.0.2+13 (21.0.2+13-LTS, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)

   Problematic frame:

   C [awt.dll+0xaa88e]

   #

   No core dump will be written. Minidumps are not enabled by default on client versions of Windows

   #

   If you would like to submit a bug report, please visit:

   https://github.com/adoptium/adoptium-support/issues

   The crash happened outside the Java Virtual Machine in native code.

   See problematic frame for where to report the bug.

   #

   ==== sanitized .qif ===== !Type:Cat !Option:AllXfr !Clear:AutoSwitch !Option:AutoSwitch !Account !Clear:AutoSwitch !Account Naccount name
   TBank
   ^ !Type:Bank D07/16'24
   U30.38
   T30.38
   Cc
   NDEP
   PPayment from person1
   Lcategory3
   Scategory1
   Eexplanation1
   $17.71 Scategory2
   Eexplanation2
   $5.38 Scategory3
   Eexplanation3
   $7.29 ^

   • Edit

3. 3 Posted by v+ik on 17 Jul, 2024 04:19 AM

   

   Not sure why the formatting is weird in the error log.... Every line started with # when I pasted it in.

   • Edit

4. 4 Posted by v+ik on 17 Jul, 2024 04:25 AM

   

   And in the .qif it joined all the lines at the top that started with ! But they are separate lines in my file. Oh I'm seeing now there is a plain text entry option. I'll redo the sanitized file.

   ==== sanitized .qif =====
   !Type:Cat
   !Option:AllXfr
   !Clear:AutoSwitch
   !Option:AutoSwitch
   !Account
   !Clear:AutoSwitch
   !Account
   Naccount name
   TBank
   ^
   !Type:Bank D07/16'24
   U30.38
   T30.38
   Cc
   NDEP
   PPayment from person1
   Lcategory3
   Scategory1
   Eexplanation1
   $17.71
   Scategory2
   Eexplanation2
   $5.38
   Scategory3
   Eexplanation3
   $7.29
   ^

   • Edit

5. 5 Posted by v+ik on 17 Jul, 2024 04:26 AM

   

   Here's a redo of the error log prefix, some lines wrapped, but # started each new line. You've likely seen error logs before.

   #
   # A fatal error has been detected by the Java Runtime Environment:
   #
   # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffcce33a88e, pid=39884, tid=31716
   #
   # JRE version: OpenJDK Runtime Environment Temurin-21.0.2+13 (21.0.2+13) (build 21.0.2+13-LTS)
   # Java VM: OpenJDK 64-Bit Server VM Temurin-21.0.2+13 (21.0.2+13-LTS, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
   # Problematic frame:
   # C [awt.dll+0xaa88e]
   #
   # No core dump will be written. Minidumps are not enabled by default on client versions of Windows
   #
   # If you would like to submit a bug report, please visit:
   # https://github.com/adoptium/adoptium-support/issues
   # The crash happened outside the Java Virtual Machine in native code.
   # See problematic frame for where to report the bug.
   #

   • Edit

6. 6 Posted by v+ik on 17 Jul, 2024 04:28 AM

   

   And multiple spaces in the error log seem to still have been reduced to one, even in plain text mode :(

   • Edit

7. 7 Posted by Stuart Beesley ... on 17 Jul, 2024 05:56 AM

   

   So clearly the JVM has crashed. However that is not the moneydance error log. Launch MD, menu help, show console. Click (…) bottom left, open console error log file/locarion. Now save this location and keep file explorer open. Now import again and then open the error file. Upload that here.

   Also, can you upload / send the qif file in question? Perhaps make this thread private too?

   • Edit

8. 8 Posted by dtd on 17 Jul, 2024 06:02 AM

   

   I think the qif file in question is in post 4?

   • Edit

9. 9 Posted by v+ik on 17 Jul, 2024 07:22 AM

   

   Well, Stuart, thanks for the more explicit directions on how to find the log file location, and I see an "errlog.txt' file there. While you directions were explicit, I couldn't follow them exactly: there was no "..." in the lower left of the "Console Messages" window, insteald there was an icon for a drop-down menu that has a "Files and Folders" entry, which produced another menu which had a "Console Log" entry which produced aonther menu which had a "Show file location" entry, which opened the File Explorer to where I found "errlog.txt".

   Anyway, with the "Console Messages" window open, and the File Manager open, I tried the import, and it worked !! The transaction got imported. So I guess there is nothing wrong with the .qif file.

   So I leave the File Manager window open, close down Moneydance, and try the import again without the Console Messages window open.... and it works again.

   But I tried and It crashed 3 times before I posted here. Hmm. Is this an unsolvable mystery? I see that errlog.txt the first time I looked was 577KB (because I saved a copy), and now it is only 18KB.

   • Edit

10. 10 Posted by dtd on 17 Jul, 2024 07:30 AM

    

    The errlog gets reset each time you use and close (or crash) moneydance...

    • Edit

11. 11 Posted by dtd on 17 Jul, 2024 07:31 AM

    

    You might want to upload the 577kb file if you can't interpret it yourself.

    • Edit

12. 12 Posted by Stuart Beesley ... on 17 Jul, 2024 07:40 AM

    

    See picture for what I was describing

    • Screenshot_2024-07-17_at_08.37.50.png 612 KB
    • Edit

13. 13 Posted by Stuart Beesley ... on 17 Jul, 2024 07:41 AM

    

    OK, do this... Launch MD, open console. Keep it open.... Import the QIF... grab / upload the console error file anyway for us to review..

    • Edit

14. 14 Posted by Glenn on 17 Jul, 2024 08:04 AM

    

    So in the 577KB errlog the quote loader had run. In the 18KB errlog it hadn't. So that appears to be the difference in size. But both logs I still have are of successful imports, unless the errlog is saved in the backup for each run?

    And under what conditions does the quote leader choose to run or not run?

    I also have several accounts that download transaction at each start of MD. I don't know if that runs before or after the quote loader, but I see those status messages at the bottom of the main MD screen, and I don't see any evidence of them in the errlog.

    And errlog is only 2KB when I simply open it and the quote loader doesn't run... well, when I shut it down, it became 16KB.

    I guess Quote Load does run always, but doesn't always produce 577KB errlog files... only 6 lines, in the 16KB, a couple dozen in the 18KB, and loads of lines in the 577KB.

    • Edit

15. 15 Posted by Glenn on 17 Jul, 2024 08:05 AM

    

    Can I sanitize the errlog that shows the transaction data in detail? I've saved all three logs mentioned above.

    • Edit

16. 16 Posted by Stuart Beesley ... on 17 Jul, 2024 08:07 AM

    

    QuoteLoader. You tell it how/when to run.

    Given the qif is working. Yes, redact the qif txn details and then upload the error file

    • Edit

17. 17 Posted by Glenn on 17 Jul, 2024 04:42 PM

    

    I think I tell QuoteLoader to run each time I start MD.

    !!! around the elided part

    • errlog-second.txt 16.6 KB
    • Edit