Skip to main content

Notifications

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

GP 2018 Crashes on Checkbook Balance Inquiry

(0) ShareShare
ReportReport
Posted on by 383

Hi,

We are upgrading to GP 2018 and during testing we discovered that GP crashes when we do a checkbook balance inquiry.  It does it for multiple users in multiple companies for different checkbooks in each company.  DEXSQL reveals it is calling the stored procedure itcmPopulateHistChkBalTemp and then throws a long series of errors "Cannot insert the value NULL into column 'HISTINDX', table 'tempdb.dbo.##1951628'; column does not allow nulls. INSERT fails" before the proc terminates and crashes GP.  

Here's what I've reviewed:

  • Can edit checkbook with no issues
  • Can view checkbook register with no issues
  • Can reconcile checkbook with no issues
  • Disabled Mekorma MICR in case this could be impacting things but got the same result
  • Issue does not exist in newly installed TWO company
  • Looked for all tables with column HISTINDX in them but found none.  One internet search says CM30400 has this column but no such table exists in my companies

I found a related post on this forum from 2016 by Bill Marshall that hinted at a bug in the checkbook balance code related to the HISTINDX column but that one sounded like the balance inquiry form was displaying correctly but the data displayed was not correct.  

Any insights are appreciated!

*This post is locked for comments

  • JGarcia123 Profile Picture
    632 on at
    RE: GP 2018 Crashes on Checkbook Balance Inquiry

    Was this issue ever resolved?  We are running into the same with a recent GP 2018 upgrade.

    Please advise.  

    JG

  • Angela Eckman Ebensteiner Profile Picture
    1,216 on at
    RE: GP 2018 Crashes on Checkbook Balance Inquiry

    Hi,

    Take a look at the CM20200 and the CM20300 table for any records with blank fields.  Especially the CMRECNUM field.   See if anything stand out there that could be causing it.

    Otherwise the Dexsql.log typically helps to see where it's looking or stopping on. Right before the error see what it's hitting and if it sheds any light.  If you need assistance digging into it you can open a case for assistance and attach the log to the case. We would be happy to help.

    Warmest Regards,

    Angela Ebensteiner

    Microsoft Dynamics - GP support

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Jainam Kothari – Community Spotlight

We are honored to recognize Jainam Kothari as our June 2025 Community…

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Almas Mahfooz Profile Picture

Almas Mahfooz 3 User Group Leader

Featured topics

Product updates

Dynamics 365 release plans