Overview
In some situations, the Microsoft SQL Server may create stack dumps from the M-Files database. A stack dump is a file that is written to disk with an ".mdmp" extension when SQL Server encounters a running condition that it does not have a built-in error to handle. It contains the call stacks and memory information of the threads running when this situation happened, and it’s done so that it can be used for troubleshooting. Even though the related BugCheck dump text file would contain M-Files database query, possibly always from the same situation, it is possible that the root cause is on the SQL Server side.
Example
In one case, Microsoft SQL Server 2017 (MS SQL 2017) started to create stack dumps shortly after the end users started to utilize it for an M-Files vault. MS SQL 2017 computer's Windows Event Log contained SQLException64 event with sqlservr.exe and sqllang.dll in the problem signature. Also, another error event from MSSQLSERVER was "Internal Query Processor Error: The query processor could not produce a query plan." The BugCheck dump text file next to the .mdmp file had always a query that contained a certain M-Files view number. One could think that the M-Files view would cause the issue here, but it wasn't the case.
Solution
In the example case, the MS SQL 2017 had a General Distribution Release (GDR) version installed. That is simply a kind of hotfix, or patch that contains specific fixes. Updating the SQL Server version to a recent one (in this case CU27) fixed the issue. So, if you experience MS SQL 2017 based M-Files database causing similar issues, please check that you are running the most recent version.
