[GNC] Cannot run v3 on Windows 7 since a year

Oliver Heidelbach ohei2 at yahoo.de
Sun Jun 9 08:35:57 EDT 2019


Hello,

thank you for your detailed answer.

Am 27.05.2019 um 15:53 schrieb Geert Janssens:
> Unfortunately I can't interpret the Sysinternals stuff either.
> 
> Will gnucash 3.x start for a different user on your system ? That is, can you
> log in as a user that never has used gnucash before and then try to start
> gnucash ?

Yes, it did start without problems.

> 
> If it does, it may be tripping over some metadata on your PC or the metadata
> migration, can you test the following:
> - locate the .gnucash directory in your user's home directory
>    This is typically c:\Users\<your-user-name>\.gnucash
> - rename this directory to something else, like .gnucash.bkp
> - locate the %appdata%\GnuCash directory and rename it as well to something
> like GnuCash.bkp
> - then install gnucash 3.5 and see if it starts.
> Let us know if gnucash starts under these conditions.

Yes, it does start now.

> Note this is not intended to be your final setup! It will be missing your
> saved reports, any open reports and tabs and other settings.
> It's a first start in trying to narrow down where it goes wrong.
> 
> Potentially a gdb backtrace could also shed a bit more light. As you had
> Cygwin installed before, you may reinstall it and then use it to install gdb.
> Next run gnucash from within gdb.
> 

Do you still want this? If so it may take another day or two. Please let 
me know.

Regards,
Oliver

> Geert
> 
> On zondag 21 april 2019 20:05:06 CEST Oliver Heidelbach via gnucash-user
> wrote:
>> Yes, I had Cygwin installed and now deinstalled it accoording to their
>> uninstall instructions including removing the registry entries.
>>
>> Same problem as before unfortunately.
>>
>> The following is the call stack from the Sysinternals Process Explorer:
>>
>> wow64cpu.dll!CpuGetContext+0x4
>> wow64.dll!Wow64KiUserCallbackDispatcher+0xcb
>> wow64win.dll+0x32bf9
>> ntdll.dll!KiUserCallbackDispatcher+0x1f
>> wow64win.dll+0x3fd4a
>> wow64win.dll+0x1ad9b
>> wow64.dll!Wow64SystemServiceEx+0xd7
>> wow64cpu.dll!TurboDispatchJumpAddressEnd+0x2d
>> wow64.dll!Wow64SystemServiceEx+0x1ce
>> wow64.dll!Wow64LdrpInitialize+0x42a
>> ntdll.dll!RtlImageDirectoryEntryToData+0x19a3
>> ntdll.dll!longjmp+0x2ca60
>> ntdll.dll!LdrInitializeThunk+0xe
>> USER32.dll!PeekMessageW+0x17b
>> USER32.dll!PeekMessageW+0x197
>> USER32.dll!DialogBoxIndirectParamW+0xfb
>> USER32.dll!DialogBoxIndirectParamAorW+0x108
>> USER32.dll!SoftModalMessageBox+0x757
>> USER32.dll!SoftModalMessageBox+0xa33
>> USER32.dll!MessageBoxTimeoutW+0x52
>> USER32.dll!MessageBoxTimeoutA+0x76
>> USER32.dll!MessageBoxExA+0x1b
>> USER32.dll!MessageBoxA+0x18
>> msvcrt.dll!strerror_s+0x649
>> msvcrt.dll!__threadhandle+0x466
>> msvcrt.dll!abort+0x26
>> libstdc++-6.dll!_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x163
>> libstdc++-6.dll!__cxa_throw+0x5c
>> msvcrt.dll!free+0x39
>> libgnc-core-utils.dll!_ZN5boost9iterators6detail23operator_arrow_dispatchIRN
>> S_10filesystem15directory_entryEPS4_E5applyES5_+0x11 msvcrt.dll!free+0x46
>> libgnc-core-utils.dll!_ZNK5boost9iterators6detail20iterator_facade_baseINS_1
>> 0filesystem28recursive_directory_iteratorENS3_15directory_entryENS0_25single
>> _pass_traversal_tagERS5_iLb0ELb0EEptEv+0x22
>> libgnc-core-utils.dll!gnc_path_find_localized_html_file+0x980
>> libgnc-core-utils.dll!gnc_path_find_localized_html_file+0xfce
>> libgnc-core-utils.dll!gnc_filepath_init+0xca
>> gnucash.exe+0x3b33
>> gnucash.exe+0x138b
>> ntdll.dll!RtlDeactivateActivationContextUnsafeFast+0x35f
>>
>>
>> I cannot interpret that, but maybe someone here can?
>>
>> Oliver
>>
>> Am 20.04.2019 um 11:09 schrieb Geert Janssens:
>>> Do you have other applications on your system that use guile (like
>>> Lilypond
>>> for example) ?
>>>
>>> Regards,
>>>
>>> Geert
>>>
>>> Op donderdag 18 april 2019 13:26:08 CEST schreef Oliver Heidelbach via
>>>
>>> gnucash-user:
>>>> I reinstalled the current version again to see the log.
>>>>
>>>> It does not write any log file since the Visual C++ runtime pops with
>>>> that error.
>>>>
>>>> I don't know if this helps, but I tried to run guile.exe from the
>>>> command line and this happened:
>>>>
>>>> ###############
>>>> C:\Program Files (x86)\gnucash\bin>guile
>>>>
>>>> Throw without catch before boot:
>>>> Throw to key misc-error with args ("primitive-load-path" "Unable to find
>>>> file ~S in load path" ("ice-9/boot-9") #f)Aborting.
>>>>
>>>> This application has requested the Runtime to terminate it in an unusua
>>>> Please contact the application's support team for more information.
>>>>
>>>> ################
>>>>
>>>> If I run gnucash.exe from the command line, I get the same popup error
>>>> message I have gotten before, containing the last part of the above
>>>> error message.
>>>>
>>>> Oliver
>>>>
>>>> Am 09.04.2019 um 11:27 schrieb Colin Law:
>>>>> Have a look in the gnucash trace file after you try to start it.
>>>>> https://wiki.gnucash.org/wiki/Tracefile
>>>>>
>>>>> Colin
>>>>>
>>>>> On Tue, 9 Apr 2019 at 10:25, ohei2 via gnucash-user
>>>>>
>>>>> <gnucash-user at gnucash.org> wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I just tried to install v3.5 on my Win7 64bit. It installed and on the
>>>>>> the
>>>>>> first attempt to start it I get
>>>>>>
>>>>>> /This application has requested the Runtime to terminate it in an
>>>>>> unusual
>>>>>> way. Please contact the application's support team for more
>>>>>> information/
>>>>>>
>>>>>> I also tried an uninstall and deleting the leftover directory like
>>>>>> suggested in a similar thread. Same error message.
>>>>>>
>>>>>> I did switch back to 2.6.21 which runs without any problems.
>>>>>>
>>>>>> About one year ago I tried to install 3.0 which also would not run back
>>>>>> then and switched back to the older version.
>>>>>>
>>>>>> I am a bit clueless on how to proceed. Sitting it out does not seem to
>>>>>> work
>>>>>> obviously.
>>>>>>
>>>>>> Regards, ohei2
>>>>>>
>>>>>>


More information about the gnucash-user mailing list