[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 1.0.0 -> 1.1.1d upgrade issues

Ok.  Let me explain this error and what it means.  It means that a
financial transaction is posted against an account that currently does
not exist.  Most likely, this was created againt an account that was
deleted, or a bug in the software has caused it to post against a
non-existant account.

So the first question is:

1)  What is the transaction?  What account should it have been posted under?
To determine this, in psql, pgadmin, or the like, run the following query:

select * from acc_trans where chart_id = 10030;

You may want to save these to a file.

Then run:
select * from transactions where id IN (select trans_id from acc_trans
where chart_id = 10030);

Then you can run similar queries against the statements here.

Note that you can get 1.0.0p1 releases from Sourceforge if you need to
go back.  I think you have to expand the tree or click older releases.

Best Wishes,
Chris Travers

On 10/23/06, Michael Schultheiss <..hidden..> wrote:
Chris Travers wrote:
> A few quick questions before we go further:
> 1)  Do your books currently balance?  I.e. of you run a chart of
> accounts report or a trial balance (without dates) do you have the
> same number of credits and debits?

I would assume so - I haven't tried it yet and I assume unless I find a
copy of ledgersmb 1.0.0 I can't easily run a trial balance since logging
into 1.1.1 immediately attempts to update.

> 2)  Have you ever deleted any accounts that had transactions against
> them?


Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
Ledger-smb-users mailing list