"Cannot parse file" and now get different file from backup

[David Carlson]

On 11/26/2013 6:35 PM, Christine wrote:
> Hi,
> Please help me! I've used GNUCash on a mac for almost a year with no
> problems. 
> The other day I tried to open gnucash and got a "cannot parse file" message.
> I then tried to open another file (for my household accounts) with no
> problem. I then tried to open an outdated file with a similar name to the
> file that could not "parse". It opened fine. Then I tried opening one of the
> automatic backup files, and now the file that opens is same file with a
> similar name that I used months ago. It is not the file that I have used in
> the past six months. The same thing happens with every backup file that I've
> tried to open - the difference in the file name is one word, but I keep
> getting a different file!
> What can I do?
>
> Thanks in advance for your kind help!
>
> Christine
>
>
>
>
>
> --
> View this message in context: http://gnucash.1415818.n4.nabble.com/Cannot-parse-file-and-now-get-different-file-from-backup-tp4665755.html
> Sent from the GnuCash - User mailing list archive at Nabble.com.
> _______________________________________________
> 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.
> .
>

It sounds like you have a combination of two problems. 

The first could be an example of a problem that the developers just
recently solved but have not yet had a chance to get the solution into a
stable GnuCash release.  Releases 2.4.13 and earlier may have this
problem.  This problem sometimes causes that 'cannot parse' error.  I
think that the work-around involves taking a backup file and re-entering
the transaction(s) that triggered the error, but I do not know what to
change in the transaction entry to avoid repeating the problem.  There
was some discussion in the developer list about manually un-zipping the
file before opening it with GnuCash, but that is not so easy for most of us.

Perhaps another user or developer may know of a better work-around that
is easier for mortals like us to use in the mean time.

The second problem is your filename issue.  When GnuCash makes a backup
it adds a long appendage to the filename that uniquely identifies the
date and time the backup was made.  If you want to restore a backup and
make it your main file, you need to open the selected backup file and do
a save as to the name that you want to keep.  This may be the same name
as your previous main file if you wish, or it may be different at your
pleasure, but you want to get rid of the long appendages that GnuCash
puts on backup filenames.

David C