An error occurred while running the report

[David Carlson]

On 10/22/2014 5:44 AM, comsec wrote:
> Hi:
>
> Many thanks (actually I did upload the whole trace file) but problem solved.
>
> I tried to cancel the post but the link expired.
>
> I unposted the last invoice - saw an error in the due date by one year - 
> re-posted and all back on track.
>
> Sorry for the hassle!
> *
> Regards,
>
> Comsec Networks (Spain)
> Comsec Networks Inc.
>
> office at comsecnetworks.com
> Tel (ES): +34 950 468102
> Tel (UK): +44 208 1332055*
> On 21/10/2014 20:47, Derek Atkins [via GnuCash] wrote:
>> Hi,
>>
>> comsec <[hidden email] 
>> </user/SendEmail.jtp?type=node&node=4673601&i=0>> writes:
>>
>>> Hi:
>>> GnuCash 2.6.1 has worked fine. Suddenly this error when attempting a
>>> receivables ageing. Other reports seem fine but I sort of rely on the
>>> receivables ageing and it would be good to get it running again.
>>> The error started afterv posting a new invoice.
>>> Trace attached but these lines seem to be the error:
>>> C:\Program Files
>>>
>> (x86)\gnucash\share\gnucash/guile-modules/gnucash/report/aging.scm:111:33:
>>> In procedure vector-ref in expression (vector-ref bucket-intervals
>>> current-bucket):
>>> C:\Program Files
>>>
>> (x86)\gnucash\share\gnucash/guile-modules/gnucash/report/aging.scm:111:33:
>>> Value out of range: 5
>>> * 17:31:27  WARN <gnc.scm> In C:\Program Files
>>> (x86)\gnucash\share\gnucash/scm/report.scm:
>>>  743: 21* [receivables-renderer #]
>>> In unknown file:
>>>    ?: 22  (letrec (#) (let* # # #))
>>> In C:\Program Files
>>> (x86)\gnucash\share\gnucash/guile-modules/gnucash/report/aging.scm:
>>>     ...
>>>
>>> Hope there is a solution,
>> You would need to provide the rest of the crash dump.  This isn't enough
>> to say what the issue is.
>>
>>> Paul.
>>> Please remember to CC this list on all your replies.
>>> You can do this by using Reply-To-List or Reply-All.
>> -derek
>>
>> -- 
>>        Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
>>        Member, MIT Student Information Processing Board  (SIPB)
>>        URL: http://web.mit.edu/warlord/    PP-ASEL-IA   N1NWH
>> [hidden email] </user/SendEmail.jtp?type=node&node=4673601&i=1>       
>>                  PGP key available
>> _______________________________________________
>> gnucash-user mailing list
>> [hidden email] </user/SendEmail.jtp?type=node&node=4673601&i=2>
>> https://lists.gnucash.org/mailman/listinfo/gnucash-user
>> -----
>> Please remember to CC this list on all your replies.
>> You can do this by using Reply-To-List or Reply-All.
>>
>>
>> ------------------------------------------------------------------------
>> If you reply to this email, your message will be added to the 
>> discussion below:
>> http://gnucash.1415818.n4.nabble.com/An-error-occurred-while-running-the-report-tp4673579p4673601.html 
>>
>> To unsubscribe from An error occurred while running the report, click 
>> here 
>> <http://gnucash.1415818.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4673579&code=b2ZmaWNlQGNvbXNlY25ldHdvcmtzLmNvbXw0NjczNTc5fDE1NDI3OTQ4NjQ=>.
>> NAML 
>> <http://gnucash.1415818.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> 
>>
>
>
>
>
> --
> View this message in context: http://gnucash.1415818.n4.nabble.com/An-error-occurred-while-running-the-report-tp4673579p4673615.html
> Sent from the GnuCash - User mailing list archive at Nabble.com.
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
>

I do not use that report myself, but I think that such a user error as
an out-of-range date value should simply trigger an appropriate user
error pop-up message rather than cause the entire report process or
program to fail.  That is not at all user friendly.


David C