A client recently called because they could not post a check batch because of the following error message “Long Integer Out of Range”. The user could print the checks but could not post the checks and the batch was stuck in batch recovery. The client is currently using Dynamics-GP v10.
After doing a little research I found that the document date they entered for a credit and a voucher that was being paid by a check had a date in the future that was an invalid date. The year entered was actually 3028. If you are wondering how it got posted, they post using the GL date from the batch, so the document date is more or less irrelevant until the check posting.
What I did to solve it was update transactions in the PM10300, PM20100, PM20000, PM10200 tables where the DOCDATE was incorrect.
