gnu cash crashing

[Geert Janssens]

Hi Edward,

Please remember to answer to the list instead of me personally. You can do this by using the 
reply-all or reply-list features of your mail program.

Regarding the trace file, I added a link to my reply that should help you find the trace file. I'll 
repeat it here:
http://wiki.gnucash.org/wiki/Windows#Error_messages.2C_Trace_file

Hth,
Geert

On Sunday 19 January 2014 18:41:18 Edward Hardy wrote:
> Hi Geert
> 
> How do I find the trace file?
> 
> On 19/01/2014 18:38, Geert Janssens wrote:
> > On Sunday 19 January 2014 18:33:16 Edward Hardy wrote:
> > > Sorry, should have said;
> > > 
> > > 
> > > 
> > > Running GC 2.6 on Windows7.
> > 
> > Can you check the contents of the gnucash trace file for clues or
> > post it to the list.
> > 
> > http://wiki.gnucash.org/wiki/Windows#Error_messages.2C_Trace_file
> > 
> > Geert
> > 
> > > Further info: GC now crashes each time I run a report with same
> > > error
> > > 
> > > messages. Other operations seem fine, e.g. entering an expense and
> > > 
> > > saving.
> > > 
> > > 
> > > 
> > > 
> > > 
> > > Hi there
> > > 
> > > 
> > > 
> > > - Ran a P&L report.
> > > 
> > > - Tried changing the accounting period in Preferences.
> > > 
> > > - Tried refreshing the report
> > > 
> > > - GnuCash crashed.
> > > 
> > > 
> > > 
> > > - Now when I open the file (every time)
> > > 
> > > "GnuCash could not obtain the lock file."
> > > 
> > > Then I click "Open Anyway"
> > > 
> > > Then I try and run a report
> > > 
> > > "This application has requested the runtime to terminate it in an
> > > 
> > > unusual way. "
> > > 
> > > 
> > > 
> > > Any ideas?
> > > 
> > > 
> > > 
> > > Best
> > > 
> > > 
> > > 
> > > Edward
> > > 
> > > _______________________________________________
> > > 
> > > 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.