[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Upgrade issues from 1.2.21 to 1.3.5
- Subject: Re: Upgrade issues from 1.2.21 to 1.3.5
- From: Chris Travers <..hidden..>
- Date: Sat, 3 Dec 2011 01:16:32 -0800
On Sat, Dec 3, 2011 at 1:10 AM, Robert Fraser <..hidden..> wrote:
> Hi All
> I am having trouble upgrading to 1.3
> I run through the process, and it appears that all the tables in the
> database have been truncated - I can log into LedgerSMB after the upgrade
> and there's no transactions, no chart of accounts etc.
> I am testing this on a freshly installed VM with a copy of my live database
> ( Debian Squeeze, Postgresql 8.4)
> I am unsure what needs to be entered to commence the db upgrade - I used
> * NZ for the country code (New Zealand)
> * and two unused account numbers for the AR and AP fields - I wasn't sure
> if they'd be created automatically or not.
No, these should be your existing accounts.
One common cause of problems is a lack of contrib modules (locate tablefunc).
However, you can attach /tmp/dblog (may be at /tmp/ledgersmb/dblog) if you like.