SAGE error "unable to read full transaction tree"

SAGE file is corrupted - error message "unable to read full transaction tree"

Didn't find your answer?

We run SAGE 50 2012 & send the file back and forth to our client. We check out with the last transaction number at one end and the receipient confirms that this has been restored. Last month the size of the file being returned to us was half the size it should have been, which we have only just noticed. This doesn't seem to have caused a problem until we tried to amend allocated payments - one cusomer has multiple accounts and we needed to switch a payment from one account to another. This prompted the message "unable to read full transaction tree", which I can't find anything on Google to match. So we have restored the last clean file & wish to export data from the latest version to a CSV file, which we will map & import it into the last clean file. Is the way to do it, or do we have to import all customer records, then supplier records, then Audit Trail, or is there another simpler way?

Replies (5)

Please login or register to join the discussion.

avatar
By paulwakefield1
27th Sep 2018 08:58

Has this arisen from a corruption in the clients copy of Sage or was it a backup (or even download) error? Have they run Check data?

If it is a backup/download error, would it not be simplest to get a fresh copy of the client's version and repost any transactions that you have posted?

Thanks (1)
Replying to paulwakefield1:
avatar
By vinced
27th Sep 2018 10:39

We've come to the conclusion overnight that, although labourious, we go back to an uncorrupted file and repost from there. Thanks

Thanks (0)
By mjcpage
27th Sep 2018 09:13

Hi
I'd contact John Donnelly at Leyburnsolutions.com
I've used him in the past & is excellent & very reasonable fees
[email protected]

Alternatively I'd register (free) with www.sageforum.co.uk
and ask the question there - there are some very helpful experts there ( Including John)

Thanks (2)
avatar
By kiwilondon99
27th Sep 2018 15:19

you can use uploads files to repost the majority of transaction from the audit trail - rather than REPOST
there are some file types which do not upload via the standard sage audit template-they will be manually posted
of course any alloactions will need to be redone - this is just a cut and paste of transactions and re upload from clean file

sure sage power users can ellaborate - WHAT EVER HAPPENED TO THE OLD BULLETIN BOARDS FROM OLD AWEB..that were to be reintroduced...

Thanks (0)
avatar
By johndon68
27th Sep 2018 18:40

A smaller backup isn't necessarily a problem - for example, clients often send me backups that contain reports and layouts and I just return a data files only backup to them which is much smaller but isn't missing anything that they need.

That is not an error message I've seen very often...

Whilst you can export transactions which,unless you amend the report, will not include sales receipts and purchase payments, you may find that it won't solve the problem.

You've not said if Check Data returns any errors but, if it does, and you run a transaction export, there is no way of knowing if the transactions in that export are correct as any corruption in the Audit Trail will simply be repeated in the export...

John

Thanks (0)