#19100
MSchappler
Moderator

I suspect you are using Print > Account Ledgers > Advanced with Historic Aging set to Yes. Set Historic Aging to No and you will not receive this error.

This problem will be fixed in the upcoming update 2.29.0 which should be released in early July 2016.

Regards to All,

Martin