Re: Upgrade woes - 1.3.46 to 1.4.24

On Sat, Feb 20, 2016 at 10:21 AM, Hilton Day <..hidden..> wrote:

Many thanks Erik for the speedy response.

Upgrade completed to 1.4, and then subsequently to 1.4.24, and I can open the accounts, so upgrade is considered successful.

However, here's a question for the brains-trust of ledgersmb experts on this list :)

I still can't post an AR invoice - I don't get a Post button. This is the issue which caused me to decide to upgrade from 1.3 to 1.4.

The buttons I have are: Update, Save, Schedule, and Save Template, and I'm unable to get a Post/Post as Saved/Post as Shown button to appear. I'm also unable to see any saved drafts, so it seems they're not being created either.

This isn't just for my latest client, but also for clients I've previously posted invoices for back in Dec. 2014..

The missing post button should be replaced by a save button, and then you can post after saving.

If that s missing then the problem may be with books being inappropriately closed. I can help you with that, but let's check first.

Do you have a save button?

To satisfy myself that it wasn't an issue with my host/webserver/postgres configuration or old scripts on my usual installation, I downloaded the Virtualbox image from sourceforge and upgraded that to 1.4.24 separately, and even with a completely separate config, the same issue occurs, so its something in my sqlledger config inside the database.

Have also checked my yearend - its still closed as of 30-06-14 (I haven't filed last tax year ending 30-06-2015 yet) so books are definitely open.

The issue is consistent between my current 1.3.46 install (and also 1.3.44 - tried downgrading slightly), and 1.4.24.

Any ideas what might be causing this? I'm flummoxed!

Thanksin advance,

Hilton.

On Fri, Feb 19, 2016 at 9:09 AM, Erik Huelsmann <..hidden..> wrote:
Hi Hilton,

On Thu, Feb 18, 2016 at 8:33 PM, Hilton Day <..hidden..> wrote:
I'm trying to upgrade my old 1.3.46 database (started life as 1.1 from memory - back at end of 2006), and have worked my way through a few issues so far, like a few duplicate meta numbers, and missing GIFI accounts.

Ok. Then you have the hardest part behind you :-)

Now the upgrade is bombing out with this message:

Error!

Upgrade failed;
logs can be found in /tmp/ledgersmb/dblog_2016-02-18T191531_2606_stdout and /tmp/ledgersmb/dblog_2016-02-18T191531_2606_stderr at LedgerSMB/Scripts/setup.pm line 1002.

dbversion: 1.4.24, company:

Looking in the error log (full version of both the stdout and stderr files attached), the problems look to me like:

psql:sql/modules/Fixes.sql:164: ERROR: duplicate key value violates unique constraint "menu_node_pkey"
DETAIL: Key (id)=(90) already exists.
psql:sql/modules/Fixes.sql:216: ERROR: duplicate key value violates unique constraint "menu_node_pkey"
DETAIL: Key (id)=(129) already exists.

Errors from Fixes.sql are expected, so these two aren't a problem.

psql:/tmp/ledgersmb/upgrade.sql:549: ERROR: column "recurring_interval" is of type interval but _expression_ is of type text
LINE 4: repeat || ' ' || unit as recurring_interval
^
HINT: You will need to rewrite or cast the _expression_.

This is your problem. Fortunately, it's probably easy to work around. Try changing

"""
repeat || ' ' || unit
"""

to
"""
(repeat || ' ' || unit)::interval
"""

That should allow you to get past the current problem. I hope it's the last one on your route to 1.4! Anyway, I'll change this script for 1.4.26 (We just released .25 today, but this problem isn't fixed in it).

The reason I'm trying ot upgrade is having recently picked up my business again I'm doing consulting work, and have discovered that I can't post an AR invoice any more in my current 1.3.46 - so I figured I'd upgrade to 1.4.24 before getting into why (last invoices I posted were a year or so ago).

That's weird. I'm using companies in both 1.3.46 and 1.4.22, but haven't heard about this problem before. Let me know if the upgrade fixed things!

Any help appreciated figuring out this upgrade for now.. I want to get my database moved up to 1.4 successfully before I worry about the functional issue.

The advice above should allow you to continue onto the next upgrade steps.

Regards,

--
Bye,

Erik.

http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Ledger-smb-users mailing list
..hidden..
https://lists.sourceforge.net/lists/listinfo/ledger-smb-users

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Ledger-smb-users mailing list
..hidden..
https://lists.sourceforge.net/lists/listinfo/ledger-smb-users

Best Wishes,

Chris Travers

Efficito: Hosted Accounting and ERP. Robust and Flexible. No vendor lock-in.

http://www.efficito.com/learn_more