2.4.0 Windows version and using shared folders

Iñaki Grao injaki at gmail.com
Thu Feb 24 17:53:55 EST 2011


By the way, Should I report this 2.4 behaviour to the buglist? Does anybody
else experienced this behaviour? (GnuCash 2.4.0 and 2.4.2 crashing until it
is ran as Administrator, then it is able to launch again wit no "run as
Administrator" label)

Regards

                    Iñaki



2011/2/24 Iñaki Grao <injaki at gmail.com>

> Hello Geert,
>
> I think I've found  the cause (althoug not the root cause) and a workaround
> for the problem. Your sugestion of type the full path helped me to find it
> (it didn't recognize the path using the drive letter, but using the UNC was
> fine).
>
> The cause (not the root cause):
> I forgot to mention that GnuCash 2.4 executable was running as
> Administrator, since first launches crashed (the process arose for two
> seconds in Windows Task manager, then gone). Running as Administrator seems
> to isolate in some way the executable so as to prevent wrong use, and that's
> why network drives were not visible.
> Removing the "Run as Administrator" label to the executable solved the
> problem, and this time the application ran ok.
>
> I repeated the instalation on another Windows 7 machine with similar
> environment, just to test it, and I saw the same behavior:
> -First (several) launches of GnuCash 2.4.2 crashed, with no error on
> GnuCash log (except a warning "WARN <qof.engine> [guid_init()] only got 2633
> bytes. The identifiers might not be very random" that always arose and
> arises on my GnuCash log)
> -Running GnuCash 2.4.2 as Administrator finally launched the executable,
> but then maped network drives were not visible on "open" window.
> -Closing GnuCash, removing the "run as administrator" label from the
> executable, and running it again solved the problem: it launched ok, and
> then the network drives were visible on "open" window.
>
>
> I really don't know why GnuCash 2.4.0 and 2.4.2 crashes with no error
> message on my two Windows 7 machines, since version 2.2.9 didn't show that
> behaviour before. And I don't know why running just once as Administrator
> solves that crash.
> I hope this workaround helps somebody else.
>
> Thank you for your help.
>
>
>
>                     Iñaki
>
>
>
> 2011/2/24 Geert Janssens <janssens-geert at telenet.be>
>
>> On donderdag 24 februari 2011, Geert Janssens wrote:
>>
>> > On donderdag 24 februari 2011, Iñaki Grao wrote:
>> > > Hello Geert, thank you for your answer
>> > >
>> > > I think that is not the problem. I experienced that problem before
>> (with
>> > > Windows XP), but in this case that's not the problem. In fact, the
>> share
>> > > (maped to drive letter F:) is always available to any other
>> application,
>> > > and trying to force a mount as you propose does not solve the problem
>> > > with GnuCash 2.4  (GnuCash 2.2 have no problem in my case, with same
>> PC
>> > > and environment).
>> > >
>> > > As nobody tells that GnuCash 2.4 is *not* able for some reason to
>> access
>> > > a Windows shared folder (Samba shared folder in my case) I understand
>> > > that it *is* able,
>> >
>> > I would expect it to be able to do so. I don't have access to a GnuCash
>> 2.4
>> > setup, so I can't verify that myself. I can only tell it works on
>> Windows
>> > XP here.
>> >
>> Hmm, I meant to say "I don't have access to a Windows 7 system" here...
>>
>> Geert
>> _______________________________________________
>> gnucash-user mailing list
>> gnucash-user at gnucash.org
>> https://lists.gnucash.org/mailman/listinfo/gnucash-user
>> -----
>> Please remember to CC this list on all your replies.
>> You can do this by using Reply-To-List or Reply-All.
>>
>
>


More information about the gnucash-user mailing list