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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics SL (Archived)

Database Physical Integrity check crashes

(0) ShareShare
ReportReport
Posted on by 382

Hello, 

We are working on SL2011 SP1

We noticed a mismatch after having run a GL Integrity Check (01.990.00) I wanted to Validate Application Records by checking Database Physical Integrity (95.500.00) and eventually repair records.

However, the process Validate Application Records always crashes with the following error message;

System Message 10232: Assertion failure!

File: sqlodbc.cpp
Line: 8964

Expression: odbcStmtHandle != SQL_NULL_HSTMT

Hit OK to stop program, and report the error to Microsoft Support, noting the failed expression, file name and line number.

System Message 6130: Fatal error. Process must be stopped at this time

I checked on a few other DB's (Companies) that we have and the problem seems to appear on all of them. 

Anyone here who has a clue what can be done in order to fix this? 

Many thanks

*This post is locked for comments

I have the same question (0)
  • CFROTON Profile Picture
    4,710 on at

    SLK,

    Thank you for posting your question to the forum.

    If you look in your Event Log, do you see a log for the integrity? Often there will be an error that comes before the Assertion Failure that is what we would want to look into.

    Hope this helps.

    Carolyn

    MSDSL Technical Support

  • Svante Kandel Profile Picture
    382 on at

    Hello Carolyn and many thanks for picking up this thread.

    The integrity check runs normally for some minutes and the section I pasted below is from line 3000 something.  I ran the check on different application databases and it looks as they all crash during RQReqHist and thereafter yield an endless loop of System (error) messages.  

    In the log I can however not see that there is any specific message that comes before the Assertion Failure.

    Kind regards,

    Steve

    ...

    Logical Record

    RQReqDet Count: 0

    === RQReqHdr ===

    Logical Record

    RQReqHdr Count: 0

    === RQReqHist ===

    Logical Record


    ==================================================
    System Message 10232: Assertion failure!

    File: sqlodbc.cpp
    Line:
    8964

    Expression: odbcStmtHandle != SQL_NULL_HSTMT

    Hit OK to stop program, and report the error to Microsoft
    Support, noting the failed expression, file name and line
    number.

    System Message 6130: Fatal error. Process must be stopped at this time.

    System Message 6129: Last item(s) processed: , , , , 
    ==================================================

    System Message 6125: Process ended: Tue Jun 12 04:34 P.M.

  • Svante Kandel Profile Picture
    382 on at

    Hello again,

    We should perhaps have done this test before my earlier answer; but, trough a series of trial-and-error-tests we found out that if unchecking RQReqHist and RQVendEval the integrity test passes. It seems however most unlikely that we should have any records in that specific RQ-module(?).

    Kind regards.

    Steve

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…

Leaderboard > 🔒一 Microsoft Dynamics SL (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans