Updating to Version 2.6.14 (according to portableapps.com) results in not being able to start GnuCash on Windows 7. I have both a 32bit and 64bit computer running W7 and get the same result on both computers. Also, tried running as administrator but same result. When trying to launch the program a window is briefly displayed which closes immediately.
New: Supermium (Apr 11, 2024), Platform 29.4 (Apr 10, 2024)
1,000+ portable packages, 1.1 billion downloads
Please donate today
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
It's working without issue on Windows 7 here. Could you please try running gnucash.exe within GnuCashPortable\App\GnuCash\bin directly? This will run it in local mode but allow you to view errors generate by GnuCash itself.
Sometimes, the impossible can become possible, if you're awesome!
John,
I'm not sure what you mean by run directly (or within ...)! However, what I did try is opening a command prompt window and then making the directory you specify the current directory and then execute gnucash.exe from the command line. The result was that the command prompt returned without displaying any messages and the windows showing the tip of the day as well as a the main gnucash window displayed briefly and then closed. In that, pretty much the same result.
I also used the Computer Management event viewer to inspect the windows logs and found nothing that could be attributed to gnucash.
Within the forum I noticed some other posts which indicated the gnucash uses the windows registry which I found surprising for a portable app. Therefore, I did search the registry to see if I could find any keys related to gnucash. While I don't really know what I'm looking for I couldn't find anything that appeared related to gnucash.
Also, it might be worth pointing out that today's experiment is being done on a computer where gnucash has never been previously used with success (i.e., other than yesterday's attempt which produced this failure). When this problem first arose I was using a different computer on which there was a older version of gnucash installed (i.e., not portable) which had been previously used.
Upon inspection I also noticed a folder named ./GnuCashPortable/Data/settings which contained files with extension of either .ini or .reg which where created/modified yesterday. Therefore, I renamed that directory and created a new empty folder named "settings" to see if that might make any difference. However, the result is the same but interestingly that new settings directory remained empty.
A few more findings. I reinstalled the portable apps platform on another thumb drive. Then I installed GnuCash and it works properly. I also thought I'd try to remove (i.e., uninstall) it from the failing thumb drive and then reinstall it. However, the portable apps platform produces an error saying that GnuCash cannot be uninstalled. These results strongly suggest that the problem is with the software on the failing thumb drive and circumstances suggest it may have been caused by making the updates suggested by portable apps.
Is there a suggested approach for repairing the portable apps on the failing thumb drive or is it time to simply delete all of the files and start over? I do have quite a few apps installed on that drive.
I think it more likely a program wasn't able to read from the drive, GnuCash needs a complete file or a file plus the generations before to recreate itself to make sense. GnuCash generates a whole bunch of files for just this purpose and they will normally be near your data file with a time stamp.
Unless you are using one of the SQL backends in which case it isn't a PA issue and you should visit the GnuCash bits.
HNY
Wm
That sounds very much like a failing drive. You should backup everything ASAP. You can try reformatting and scanning for errors, but I'd treat the drive as suspect going forward.
Note that a shorting USB port can also cause issues like this. It's rarer than a failing drive, but I have seen it happen.
Sometimes, the impossible can become possible, if you're awesome!