Bill Appelbe | 21 Oct 18:15 2014
Picon

error when adding item to sales order

Hi
using LedgerSMB 1.4.4.
I am getting an intermittent error.
I have a database set up with a lot of parts (>18,000).
I go to order entry - > sales order.
I enter items (using item number) and a quantity for each item.
This works well.
Occasionally I get an error as below.
I can use back arrow and save the order fine.
I cannot add any more items to this order (I can open a new order and work away). This does not happen at the same point in the order (one order I have 104 items before it happens others fewer).
I get the same error if I add an item by Description.

any pointers? I have been trying to find a non number in a numercal field but can't find one.


thanks

Bill

Error!

'LedgerSMB::PGNumber Invalid Number at LedgerSMB/PGNumber.pm line 167.
'

dbversion: 1.4.4, company: JelanTest


------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
Ledger-smb-users mailing list
Ledger-smb-users@...
https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
Peter van Bussel | 14 Oct 15:48 2014
Picon

LSMB 1.4.4 Goods and Services Search

Hi All,

 

Menu item Goods and Services > Search displays this error:

Error!

Unable to open script: LedgerSMB::Scripts::goods : No such file or directory: Can't locate namespace/autoclean.pm in <at> INC ( <at> INC contains: /etc/perl /usr/local/lib/perl/5.14.2 /usr/local/share/perl/5.14.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.14 /usr/share/perl/5.14 /usr/local/lib/site_perl .) at LedgerSMB/Report/Invoices/COGS.pm line 12.
BEGIN failed--compilation aborted at LedgerSMB/Report/Invoices/COGS.pm line 12. Compilation failed in require at LedgerSMB/Scripts/goods.pm line 9. BEGIN failed--compilation aborted at LedgerSMB/Scripts/goods.pm line 9. Compilation failed in require at (eval 1320) line 1.

dbversion: 1.4.4, company: test3

Any suggestions?

 

Regards,

 

Peter

 

------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
Ledger-smb-users mailing list
Ledger-smb-users@...
https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
Kai Huuhko | 13 Oct 10:20 2014
Picon

Upgrading lsmb-1.2 database

Hi

I'm attempting to upgrade an old database backup that was created back
in 2011 using ledgersmb-1.2.

The pg_restore process completed successfully with just one trivial
error: could not execute query: ERROR:  language "plpgsql" already
exists

Trying to run the upgrade process using lsmb-1.4.4 it errored out
saying I should check the logs in /etc/ledgersmb but I have no such
directory.

With lsmb-1.3.44 the upgrade process completes but with 0 row counts
for all but users (1) and vendors (2). I get no actual data in the
company, even the chart of accounts is empty.

Attached is a syslog dump of entries logged by postgresql during the
upgrade process using lsmb-1.3.44.

Can anyone help me get the database upgraded completely?
Attachment (lsmb-upgrade-pg.log.tar.xz): application/x-xz, 18 KiB
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho
_______________________________________________
Ledger-smb-users mailing list
Ledger-smb-users@...
https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
Peter van Bussel | 13 Oct 00:22 2014
Picon

journal.pl not found

Dear All,

 

After upgrading to 1.4.3 and applying starman, I can login with http://localhost:5000/login.pl, but I can’t get rid of error “The requested URL /journal.pl was not found on this server.”

 

Any suggestions?

 

Regards,

 

Peter

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho
_______________________________________________
Ledger-smb-users mailing list
Ledger-smb-users@...
https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
Peter van Bussel | 12 Oct 23:22 2014
Picon

(no subject)

Dear All,

 

After upgrading to 1.4.3 and applying starman, I can login with http://localhost:5000/login.pl, but I can’t get rid of error “The requested URL /journal.pl was not found on this server.”

 

Any suggestions?

 

Regards,

 

Peter

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho
_______________________________________________
Ledger-smb-users mailing list
Ledger-smb-users@...
https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
Stephen Winnall | 4 Oct 22:28 2014
Picon

Problems with 1.4.2

I have my database (PostgreSQL 9.3) on one Ubuntu 14.04 machine and my LedgerSMB 1.4.2 on another Ubuntu 14.04 machine. I updated LSMB from 1.3.33 (I think) via 1.3.44, 1.4.0  and 1.4.1.

My database contains a small number of entries going back 3 or four years (mainly GL). The language is German (Switzerland).

Problem 1)
My books are closed after a year-end. I tried to reopen them. My browser says:

Error!

Access Denied
More information has been reported in the error logs at LedgerSMB.pm line 775.

dbversion: 1.4.2, company: my-company

I get the following error in my PostgreSQL log:

2014-10-04 20:05:51 GMT ERROR:  permission denied for sequence account_checkpoint_id_seq
2014-10-04 20:05:51 GMT CONTEXT:  SQL statement "INSERT INTO 
                account_checkpoint (end_date, account_id, amount, debits, credits)
            SELECT in_end_date, COALESCE(a.chart_id, cp.account_id),
                    COALESCE(SUM (a.amount),0) + coalesce(MAX (cp.amount), 0),
                    COALESCE(SUM (CASE WHEN (a.amount < 0) THEN a.amount ELSE 0 END), 0) +
                     COALESCE( MIN (cp.debits), 0),
                    COALESCE(SUM (CASE WHEN (a.amount > 0) THEN a.amount ELSE 0 END), 0) +
                     COALESCE( MAX (cp.credits), 0)
                FROM 
                (SELECT * FROM acc_trans WHERE transdate <= in_end_date AND
                 transdate > COALESCE(cp_date, '1200-01-01')) a
                FULL OUTER JOIN (
                        select account_id, end_date, amount, debits, credits 
                        from account_checkpoint
                        WHERE end_date = cp_date
                        ) cp on (a.chart_id = cp.account_id)
                group by COALESCE(a.chart_id, cp.account_id)"
        PL/pgSQL function eoy_create_checkpoint(date) line 27 at SQL statement
        SQL function "eoy__reopen_books_at" statement 2
2014-10-04 20:05:51 GMT STATEMENT:  SELECT * FROM "public"."eoy__reopen_books_at"('2011-10-01')

(Yes, I know it says 2011…)

Problem 2)
When I try to add a new journal entry to GL, the form comes up without a pre-generated reference number although System > Settings shows sensible “Next in Sequence” values.

Attempts at solving this:

- I thought re-running setup.pl might help, but it has not.

- I thought running lamb_reload might help, but it doesn’t appear to work with a remote database, even if I specify the DB machine with “--host”.

I’d be grateful for any assistance on this. My default action will be to back to 1.3.

Steve
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Ledger-smb-users mailing list
Ledger-smb-users@...
https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
R. Ransbottom | 2 Oct 22:10 2014
Picon
Picon

Obselete account query

Hello,

'select * from account' output shows an 'obselete' field.  Grepping
through my ledgersmb directory tree finds nothing.

Is this part of postgresql 9.1 versioning?

I was thinking of obseleting dead accounts so our chart and our
accountants' chart stay in sync.

Thanks,
Rob

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
Frans Star | 2 Oct 18:17 2014
Picon

Re: Ledger-smb-users Digest, Vol 97, Issue 5



On Thu, Oct 2, 2014 at 11:55 PM, <ledger-smb-users-request-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org> wrote:
Send Ledger-smb-users mailing list submissions to
        ledger-smb-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
or, via email, send a message with subject or body 'help' to
        ledger-smb-users-request-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org

You can reach the person managing the list at
        ledger-smb-users-owner-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Ledger-smb-users digest..."


Today's Topics:

   1. Re: setup error (Bill Appelbe)
   2. Chart of Account Query (R. Ransbottom)
   3. Re: Chart of Account Query (Chris Travers)
   4. Printing (Bill Appelbe)


----------------------------------------------------------------------

Message: 1
Date: Thu, 2 Oct 2014 09:13:20 +0100
From: Bill Appelbe <bappelbe <at> gmail.com>
Subject: Re: [Ledger-smb-users] setup error
To: ledger-smb-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Message-ID:
        <CAGyw+papSivGau2M2tj106Hw4mZTU-1xT8Tfu25Ri0Ci3R1pwQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Content-Type: text/plain; charset="utf-8"

Thanks
I had thought that the user was for each company

Bill

On Thu, Oct 2, 2014 at 2:18 AM, Chris Travers <chris.travers-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:

> https://github.com/ledgersmb/LedgerSMB/pull/401 corrects this problem.
>
> On Wed, Oct 1, 2014 at 5:45 PM, Chris Travers <chris.travers-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> wrote:
>
>> Hi Bill:
>>
>> I fixed a similar issue in the main application and apparently neglected
>> to fix it here.  This is a problem with error handling.  It is supposed to
>> handle the error more gracefully.  I will get a fix in for 1.4.3 today.
>> The desired behavior is to notify the user and present the form again with
>> the import option selected.
>>
>> In the mean time, this happens when the user already exists in the
>> database cluster.  If you are importing the user, select the 'yes' radio
>> button while creating the user.  In this case you can leave the password
>> blank and it will nto change the password or set an expiration.  This
>> allows the sharing of accounts between databases, but we naturally don't
>> want to do this in a way which makes it too easy for users to be
>> accidentally shared.....
>>
>>
>>
>> On Wed, Oct 1, 2014 at 1:33 PM, Pongr?cz Istv?n <
>> pongracz.istvan <at> gmail.com> wrote:
>>
>>>
>>>  Hi,
>>>
>>> If you try to add the same user to the system, which exists in other
>>> instances on the same postgresql, you have to select *import* option.
>>>
>>> This is because the user is system wide in the database level and linked
>>> to one or more ledgersmb databases. If the username does not exist, itt
>>> will be created (system wide) and linked to this database.
>>>
>>> Could you confirm, that username existed in your database and you did
>>> not select import on creating?
>>>
>>> Cheers,
>>>
>>> Istv?n
>>>
>>>
>>>
>>> ----------------eredeti ?zenet-----------------
>>> Felad?: "Bill Appelbe" <bappelbe-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>>> C?mzett: ledger-smb-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>>> D?tum: Wed, 1 Oct 2014 17:35:09 +0100
>>> ----------------------------------------------------------
>>>
>>>
>>>  Hi
>>> while creating a new company I got an error in LedgerSMB 1.4.2
>>> I go through the setup.pl steps and when it press "create user" I get
>>> Error!
>>>
>>>
>>> *Error from Function: ERROR: Duplicate user More information has been
>>> reported in the error logs at LedgerSMB.pm line 775. *
>>>
>>> dbversion: 1.4.2, company:
>>>
>>>
>>>
>>>
>>>
>>> I attach the postgres and apache log file extracts for this.
>>>
>>> I have been playing a lot with the database in another company - but
>>> that shouldn't cause this - or would it?
>>>
>>>
>>>
>>> Bill
>>>  ------------------------------
>>>
>>> ------------------------------------------------------------------------------
>>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
>>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzerhttp://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>>>
>>> ------------------------------
>>>
>>> _______________________________________________
>>> Ledger-smb-users mailing listLedger-smb-users-5NWGOfrQmneRv+LV9MX5ug@public.gmane.orge.nethttps://lists.sourceforge.net/lists/listinfo/ledger-smb-users
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
>>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>>>
>>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Ledger-smb-users mailing list
>>> Ledger-smb-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>>> 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
>>
>
>
>
> --
> Best Wishes,
> Chris Travers
>
> Efficito:  Hosted Accounting and ERP.  Robust and Flexible.  No vendor
> lock-in.
> http://www.efficito.com/learn_more
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Ledger-smb-users mailing list
> Ledger-smb-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

Message: 2
Date: Thu, 2 Oct 2014 08:20:17 -0400
From: "R. Ransbottom" <rirans-Wuw85uim5zDR7s880joybQ@public.gmane.org>
Subject: [Ledger-smb-users] Chart of Account Query
To: ledger-smb-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Message-ID: <20141002122017.GA6003-Wt+tKfSqHxRwKoX9GjgWag@public.gmane.org>
Content-Type: text/plain; charset=us-ascii

Hello,

Regarding CoA implementation:

Can a account_heading be referenced by discontiguous accounts.
My experience indicates that discontiguous records are
GAAP-improper.

By discontiguous I mean, given (100 Cash), (110 Petty Cash),
(130 A/R), that (100) and (130) have one account_heading parent
while (110) has a different one.


Thanks,
Rob




------------------------------

Message: 3
Date: Thu, 2 Oct 2014 05:40:40 -0700
From: Chris Travers <chris.travers-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [Ledger-smb-users] Chart of Account Query
To: LedgerSMB Users <ledger-smb-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
        rirans <at> comcast.net
Message-ID:
        <CAKt_Zfs0=03zKopUFnJXzFzXUoYe9S1=g3CAHp-RZsZi56za0g-JsoAwUIsXov1KXRcyAk9cg@public.gmane.orgl.com>
Content-Type: text/plain; charset="utf-8"

On Thu, Oct 2, 2014 at 5:20 AM, R. Ransbottom <rirans-Wuw85uim5zDR7s880joybQ@public.gmane.org> wrote:

> Hello,
>
> Regarding CoA implementation:
>
> Can a account_heading be referenced by discontiguous accounts.
> My experience indicates that discontiguous records are
> GAAP-improper.
>

For reasons below, we can't enforce a contiguousness rule very well.
However, as you point out breaking that rule on a logical level is
dangerous.

>
> By discontiguous I mean, given (100 Cash), (110 Petty Cash),
> (130 A/R), that (100) and (130) have one account_heading parent
> while (110) has a different one.
>

I can't imagine a case where you'd want to do that, unless you wanted to be
able to aggregate a bunch of petty cash drawers together, and have that
header have its parent be the same as for 100 and 130.

Let's look at a more likely example:

heading 13000 Accounts Payab,e
- 13000-00-00 Accounts Payable Corporate
- 13001 -- Heading: Clients Payable
-- 13001-00-01 - Clients Payable US
-- 13001-00-02 - Clients Payable MX
-- 13001-00-03 - Clients Payable CA
- 13002 -- Reserves Payable
-- 13002-00-01 - Reserves Payable US
-- 13002-00-02 - Reserves Payable MX
-- 13002-00-04 - Reserves Payable CA
- 13999-00-00 Accounts Payable Misc

I can think of cases where people have books which are logically like this,
where everything contiguously is descended from the same header, but may
not be directly so.  Consequently, the subtotal of the 13000 heading will
be the exact same whether or not the 13001 and 13002 headings are in place,
but these provide some  intermediate points of aggregation which may or may
not be helpful.

I am not aware of any GAAP issues with the above setup, because 13000
aggregates represents a contiguous block of accounts.  supporting this use
case, however, does mean we can't enforce things remarkably strictly so
people can mess up their books.

It is further worth noting that generally there are plenty of places where
we assume that these blocks are contiguous.  We certainly do not consider
it good practice to break that rule.

>
>
> Thanks,
> Rob
>
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Ledger-smb-users mailing list
> Ledger-smb-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> 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
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

Message: 4
Date: Thu, 2 Oct 2014 16:54:50 +0100
From: Bill Appelbe <bappelbe <at> gmail.com>
Subject: [Ledger-smb-users] Printing
To: ledger-smb-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Message-ID:
        <CAGyw+pb+JDdovcfhoG3Pq_9YWVimq=hLgkEcK9LTsgbxXq1vQg-JsoAwUIsXov1KXRcyAk9cg@public.gmane.orgl.com>
Content-Type: text/plain; charset="utf-8"

Hi
I have been trying to set up printing on my install of LedgerSMB 1.4.2 on
Linux Mint 17.
for starters I needed to install package libtex-encode-perl (which as far
as I can see is not in the install instructions).

Now I am trying to print a sales order that I have to PDF, Screen. I am
getting the error below.

Am I missing something obvious?

thanks

Bill

Error!



















*'Attribute (format) is required at
/usr/local/lib/perl/5.18.2/Moose/Exception.pm line 34
Moose::Exception::_build_trace('Moose::Exception::AttributeIsRequired=HASH(0x837fda0)')
called at reader Moose::Exception::trace (defined at
/usr/local/lib/perl/5.18.2/Moose/Exception.pm line 6) line 7
Moose::Exception::trace('Moose::Exception::AttributeIsRequired=HASH(0x837fda0)')
called at /usr/local/lib/perl/5.18.2/Moose/Exception.pm line 46
Moose::Exception::BUILD('Moose::Exception::AttributeIsRequired=HASH(0x837fda0)',
'HASH(0x8616a30)') called at /usr/local/lib/perl/5.18.2/Class/MOP/Method.pm
line 123 Class::MOP::Method::execute('Moose::Meta::Method=HASH(0x8dfec10)',
'Moose::Exception::AttributeIsRequired=HASH(0x837fda0)', 'HASH(0x8616a30)')
called at /usr/local/lib/perl/5.18.2/Moose/Object.pm line 52
Moose::Object::BUILDALL('Moose::Exception::AttributeIsRequired=HASH(0x837fda0)',
'HASH(0x8616a30)') called at /usr/local/lib/perl/5.18.2/Moose/Meta/Class.pm
line 278
Moose::Meta::Class::new_object('Moose::Meta::Class=HASH(0x86dd0d8)',
'HASH(0x8616a30)') called at /usr/local/lib/perl/5.18.2/Moose/Object.pm
line 23 Moose::Object::new('Moose::Exception::AttributeIsRequired',
'params', 'HASH(0x8648a28)', 'class_name', 'LedgerSMB::Template::DB',
'attribute_name', 'format') called at constructor
LedgerSMB::Template::DB::new (defined at LedgerSMB/Template/DB.pm line 170)
line 30 LedgerSMB::Template::DB::new('LedgerSMB::Template::DB',
'HASH(0x86dd348)') called at LedgerSMB/Template/DB.pm line 68
LedgerSMB::Template::DB::get_template('LedgerSMB::Template::DB',
'envelope', undef, 'tex') called at LedgerSMB/Template/LaTeX.pm line 140
LedgerSMB::Template::LaTeX::process('LedgerSMB::Template=HASH(0x85cecf8)',
'HASH(0x876d0f8)') called at LedgerSMB/Template.pm line 351
LedgerSMB::Template::render('LedgerSMB::Template=HASH(0x85cecf8)',
'Form=HASH(0x2593708)') called at bin/io.pl <http://io.pl> line 1994
lsmb_legacy::print_form(undef) called at bin/io.pl <http://io.pl> line 1578
lsmb_legacy::print at old-handler.pl <http://old-handler.pl> line 206
lsmb_legacy::try {...} at /usr/local/share/perl/5.18.2/Try/Tiny.pm line 81
eval {...} at /usr/local/share/perl/5.18.2/Try/Tiny.pm line 72
Try::Tiny::try('CODE(0x26ed950)', 'Try::Tiny::Catch=REF(0x79ddd50)') called
at old-handler.pl <http://old-handler.pl> line 225 require old-handler.pl
<http://old-handler.pl> at /usr/share/ledgersmb/oe.pl <http://oe.pl> line
7'*

dbversion: 1.4.2, company:
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk

------------------------------

_______________________________________________
Ledger-smb-users mailing list
Ledger-smb-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ledger-smb-users

 

End of Ledger-smb-users Digest, Vol 97, Issue 5
***********************************************
Did you install live-latex recommended?
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Ledger-smb-users mailing list
Ledger-smb-users@...
https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
Bill Appelbe | 2 Oct 17:54 2014
Picon

Printing

Hi
I have been trying to set up printing on my install of LedgerSMB 1.4.2 on Linux Mint 17.
for starters I needed to install package libtex-encode-perl (which as far as I can see is not in the install instructions).

Now I am trying to print a sales order that I have to PDF, Screen. I am getting the error below.

Am I missing something obvious?

thanks

Bill

Error!

'Attribute (format) is required at /usr/local/lib/perl/5.18.2/Moose/Exception.pm line 34
Moose::Exception::_build_trace('Moose::Exception::AttributeIsRequired=HASH(0x837fda0)') called at reader Moose::Exception::trace (defined at /usr/local/lib/perl/5.18.2/Moose/Exception.pm line 6) line 7
Moose::Exception::trace('Moose::Exception::AttributeIsRequired=HASH(0x837fda0)') called at /usr/local/lib/perl/5.18.2/Moose/Exception.pm line 46
Moose::Exception::BUILD('Moose::Exception::AttributeIsRequired=HASH(0x837fda0)', 'HASH(0x8616a30)') called at /usr/local/lib/perl/5.18.2/Class/MOP/Method.pm line 123
Class::MOP::Method::execute('Moose::Meta::Method=HASH(0x8dfec10)', 'Moose::Exception::AttributeIsRequired=HASH(0x837fda0)', 'HASH(0x8616a30)') called at /usr/local/lib/perl/5.18.2/Moose/Object.pm line 52
Moose::Object::BUILDALL('Moose::Exception::AttributeIsRequired=HASH(0x837fda0)', 'HASH(0x8616a30)') called at /usr/local/lib/perl/5.18.2/Moose/Meta/Class.pm line 278
Moose::Meta::Class::new_object('Moose::Meta::Class=HASH(0x86dd0d8)', 'HASH(0x8616a30)') called at /usr/local/lib/perl/5.18.2/Moose/Object.pm line 23
Moose::Object::new('Moose::Exception::AttributeIsRequired', 'params', 'HASH(0x8648a28)', 'class_name', 'LedgerSMB::Template::DB', 'attribute_name', 'format') called at constructor LedgerSMB::Template::DB::new (defined at LedgerSMB/Template/DB.pm line 170) line 30
LedgerSMB::Template::DB::new('LedgerSMB::Template::DB', 'HASH(0x86dd348)') called at LedgerSMB/Template/DB.pm line 68
LedgerSMB::Template::DB::get_template('LedgerSMB::Template::DB', 'envelope', undef, 'tex') called at LedgerSMB/Template/LaTeX.pm line 140
LedgerSMB::Template::LaTeX::process('LedgerSMB::Template=HASH(0x85cecf8)', 'HASH(0x876d0f8)') called at LedgerSMB/Template.pm line 351
LedgerSMB::Template::render('LedgerSMB::Template=HASH(0x85cecf8)', 'Form=HASH(0x2593708)') called at bin/io.pl line 1994
lsmb_legacy::print_form(undef) called at bin/io.pl line 1578
lsmb_legacy::print at old-handler.pl line 206
lsmb_legacy::try {...} at /usr/local/share/perl/5.18.2/Try/Tiny.pm line 81
eval {...} at /usr/local/share/perl/5.18.2/Try/Tiny.pm line 72
Try::Tiny::try('CODE(0x26ed950)', 'Try::Tiny::Catch=REF(0x79ddd50)') called at old-handler.pl line 225
require old-handler.pl at /usr/share/ledgersmb/oe.pl line 7
'

dbversion: 1.4.2, company:


------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Ledger-smb-users mailing list
Ledger-smb-users@...
https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
R. Ransbottom | 2 Oct 14:20 2014
Picon
Picon

Chart of Account Query

Hello,

Regarding CoA implementation:

Can a account_heading be referenced by discontiguous accounts.
My experience indicates that discontiguous records are
GAAP-improper.

By discontiguous I mean, given (100 Cash), (110 Petty Cash),
(130 A/R), that (100) and (130) have one account_heading parent
while (110) has a different one.

Thanks,
Rob

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
Bill Appelbe | 1 Oct 18:35 2014
Picon

setup error

Hi
while creating a new company I got an error in LedgerSMB 1.4.2
I go through the setup.pl steps and when it press "create user" I get

Error!

Error from Function:
ERROR: Duplicate user More information has been reported in the error logs at LedgerSMB.pm line 775.

dbversion: 1.4.2, company:



I attach the postgres and apache log file extracts for this.

I have been playing a lot with the database in another company - but that shouldn't cause this - or would it?


Bill


Attachment (apachelog): application/octet-stream, 8 KiB
Attachment (postgreslog): application/octet-stream, 17 KiB
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Ledger-smb-users mailing list
Ledger-smb-users@...
https://lists.sourceforge.net/lists/listinfo/ledger-smb-users

Gmane