Help get this topic noticed by sharing it on Twitter, Facebook, or email.

SQL Server is crashing, could it be related to DBAmp?

We installed DBAmp v3.6.5.0 on a new server (SQL 2016 13.0.4001.0) a few weeks ago, and today it has experienced multiple crashes with Fatal Error Severity 25 alerts in the ntdll.dll module. Some internet research suggested this could be caused by third-party providers. This server also has Oracle and ADSI providers, but I think only the DBAmp providers were in use today.

Is there any way to prove this was not related to DBAmp, or is there any suggested corrective action if it is?

Some of the error logging:
(Same code for at least 3 crashes)
Faulting module name: combase.dll, version: 6.2.9200.22376, time stamp: 0x5a90b7a6
Exception code: 0xc0000005
Fault offset: 0x0000000000009198

(Same code for at least 4 crashes)
Faulting module name: ntdll.dll, version: 6.2.9200.22376, time stamp: 0x5a90c271
Exception code: 0xc0000374
Fault offset: 0x00000000000da535

We have several other servers (SQL 2008 R2 10.50.4042.0) running DBAmp V3.1.4, which have worked flawlessly for years.
1 person has
this problem
+1
Reply