web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics SL (Archived) / AP Check printing sys ...
Microsoft Dynamics SL (Archived)

AP Check printing sys msg 10232 SL2015

(0) ShareShare
ReportReport
Posted on by Community Member

We are testing the SL2015 in our test environment and encountered a very strange issue. When we try to print AP Checks, we received the message 10232 -

Assertion failure!

File : sqlodbc.cpp

Line: 10248

Expression: tmpdeconn !=SQL_NULL_HDBC

This problem only occurred at client machines (at least 2 machines so far), I can't reproduced the same error on the server. In addition, we get the same error when we try to view selections prior printing checks.

Thanks in advance.

Wenchi Wang

*This post is locked for comments

I have the same question (0)
  • pstgeorge Profile Picture
    pstgeorge 30 on at

    By any chance did you get to the bottom of this?  I cannot find much on the matter... :)

  • Suggested answer
    Community Member Profile Picture
    Community Member on at

    I have run into the 10232 error on workstations when the server has the Windows firewall enabled and it has not created an exception to allow sqlserver requests through.  However, if you had this issue then I would think that not much of anything would be working.  However, just through this out in case.

  • Joseph Capallo Profile Picture
    Joseph Capallo 2 on at

    We are having the same issue. Windows firewall is off. Multiple cores. Can print on app server but not on terminal server or clients.

  • Joseph Capallo Profile Picture
    Joseph Capallo 2 on at

    For us, we were able to get it work by changing the preprocess in report control maintenance for 03620. They added a new check format that prints project information and in order to support this, they replaced the old preprocess with one that does the project related work, THEN calls the old preprocess (0362010). Since they don’t use project here, we can just bypass the new preprocess and go directly to 0362010 by reconfiguring the report control maintenance record, which seems to be working so far.

  • Suggested answer
    Laura Profile Picture
    Laura 460 on at

    This resolution worked perfectly for an SL 2015 CU2 workstation that was getting System Message 10232 Assertion failure! File:sqlodbc.cpp Line: 10248  Expression: tmpdbconn !=SQL_NULL_HDBC

    Changed preprocess from GRRSW00 to 0362010 and printed without error - client was not using Project

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics SL (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans