On Sat, Dec 3, 2011 at 1:10 AM, Robert Fraser <r...@egressive.com> 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. Best Wishes, Chris Travers ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Ledger-smb-users mailing list Ledger-smb-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
