Linked Server using custom ODBC is failing

Question

I am hoping someone can help.  We are using a custom ODBC driver and I have opened a case with Microsoft and sought support from the actual developer but have yet to get any help.

I think it is still an access problem.  I needed to set the permissions on DCOM for MSDAINITIALIZE manually attempting to do a query on Server 2016 with SQL 2017 to get past the first issue but ran into a brick wall with executing in process or not selected for the provider.  I don't know where else to go because it seems no one can help me.

error is below that I am getting when attempting to execute the query after fixing the permissions.  It works with SQL 2014 but not 2016 and 2017.  Stuck between a hard place for auditing and using older versions of SQL.

Dump Summary
------------
Dump File: dllhost.exe.12352.dmp : C:\Users\Administrator.DAC\AppData\Local\CrashDumps\dllhost.exe.12352.dmp
Last Write Time: 6/5/2018 10:42:11 AM
Process Name: dllhost.exe : C:\Windows\System32\dllhost.exe
Process Architecture: x64
Exception Code: 0xC0000005
Exception Information: The thread tried to read from or write to a virtual address for which it does not have the appropriate access.
Heap Information: Not Present

System Information
------------------
OS Version: 10.0.14393
CLR Version(s):

Modules
-------
Module Name Module Path Module Version
----------- ----------- --------------
dllhost.exe C:\Windows\System32\dllhost.exe 10.0.14393.0
ntdll.dll C:\Windows\System32\ntdll.dll 10.0.14393.2214
kernel32.dll C:\Windows\System32\kernel32.dll 10.0.14393.2214
KERNELBASE.dll C:\Windows\System32\KERNELBASE.dll 10.0.14393.2189
ucrtbase.dll C:\Windows\System32\ucrtbase.dll 10.0.14393.2097
combase.dll C:\Windows\System32\combase.dll 10.0.14393.2248
rpcrt4.dll C:\Windows\System32\rpcrt4.dll 10.0.14393.2155
bcryptPrimitives.dll C:\Windows\System32\bcryptPrimitives.dll 10.0.14393.2156
kernel.appcore.dll C:\Windows\System32\kernel.appcore.dll 10.0.14393.0
msvcrt.dll C:\Windows\System32\msvcrt.dll 7.0.14393.0
clbcatq.dll C:\Windows\System32\clbcatq.dll 2001.12.10941.16384
user32.dll C:\Windows\System32\user32.dll 10.0.14393.1770
win32u.dll C:\Windows\System32\win32u.dll 10.0.14393.51
gdi32.dll C:\Windows\System32\gdi32.dll 10.0.14393.206
gdi32full.dll C:\Windows\System32\gdi32full.dll 10.0.14393.1770
sechost.dll C:\Windows\System32\sechost.dll 10.0.14393.1613
oledb32.dll C:\Program Files\Common Files\System\Ole DB\oledb32.dll 10.0.14393.2248
advapi32.dll C:\Windows\System32\advapi32.dll 10.0.14393.2248
msdart.dll C:\Windows\System32\msdart.dll 10.0.14393.0
ole32.dll C:\Windows\System32\ole32.dll 10.0.14393.2248
oleaut32.dll C:\Windows\System32\oleaut32.dll 10.0.14393.2248
msvcp_win.dll C:\Windows\System32\msvcp_win.dll 10.0.14393.2097
bcrypt.dll C:\Windows\System32\bcrypt.dll 10.0.14393.576
dpapi.dll C:\Windows\System32\dpapi.dll 10.0.14393.0
comctl32.dll C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.14393.2248_none_7ddece3683436ba6\comctl32.dll 6.10.14393.2248
comsvcs.dll C:\Windows\System32\comsvcs.dll 2001.12.10941.16384
msdaps.dll C:\Program Files\Common Files\System\Ole DB\msdaps.dll 10.0.14393.0
cryptsp.dll C:\Windows\System32\cryptsp.dll 10.0.14393.0
rsaenh.dll C:\Windows\System32\rsaenh.dll 10.0.14393.0
CRYPTBASE.dll C:\Windows\System32\CRYPTBASE.dll 10.0.14393.0
msdasql.dll C:\Program Files\Common Files\System\Ole DB\msdasql.dll 10.0.14393.0
msdatl3.dll C:\Program Files\Common Files\System\Ole DB\msdatl3.dll 10.0.14393.0
odbc32.dll C:\Windows\System32\odbc32.dll 10.0.14393.0
msdasqlr.dll C:\Program Files\Common Files\System\Ole DB\msdasqlr.dll 10.0.14393.0
BBjODBC.dll C:\Windows\System32\BBjODBC.dll 17.1.1.0
comdlg32.dll C:\Windows\System32\comdlg32.dll 10.0.14393.2248
wsock32.dll C:\Windows\System32\wsock32.dll 10.0.14393.0
msimg32.dll C:\Windows\System32\msimg32.dll 10.0.14393.0
ws2_32.dll C:\Windows\System32\ws2_32.dll 10.0.14393.206
SHCore.dll C:\Windows\System32\SHCore.dll 10.0.14393.2248
shlwapi.dll C:\Windows\System32\shlwapi.dll 10.0.14393.0
shell32.dll C:\Windows\System32\shell32.dll 10.0.14393.2248
comctl32.dll C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.14393.447_none_0d5aa7fbb6d35646\comctl32.dll 5.82.14393.447
cfgmgr32.dll C:\Windows\System32\cfgmgr32.dll 10.0.14393.0
windows.storage.dll C:\Windows\System32\windows.storage.dll 10.0.14393.2248
powrprof.dll C:\Windows\System32\powrprof.dll 10.0.14393.0
profapi.dll C:\Windows\System32\profapi.dll 10.0.14393.0
imm32.dll C:\Windows\System32\imm32.dll 10.0.14393.0
winspool.drv C:\Windows\System32\winspool.drv 10.0.14393.2097
oleacc.dll C:\Windows\System32\oleacc.dll 7.2.14393.2156
GdiPlus.dll C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.14393.2248_none_aec9c11bddd5e574\GdiPlus.dll 10.0.14393.2248
winmm.dll C:\Windows\System32\winmm.dll 10.0.14393.0
WINMMBASE.dll C:\Windows\System32\WINMMBASE.dll 10.0.14393.0
uxtheme.dll C:\Windows\System32\uxtheme.dll 10.0.14393.2248
dwmapi.dll C:\Windows\System32\dwmapi.dll 10.0.14393.206
odbccp32.dll C:\Windows\System32\odbccp32.dll 10.0.14393.0
version.dll C:\Windows\System32\version.dll 10.0.14393.0
mswsock.dll C:\Windows\System32\mswsock.dll 10.0.14393.0
dnsapi.dll C:\Windows\System32\dnsapi.dll 10.0.14393.2155
nsi.dll C:\Windows\System32\nsi.dll 10.0.14393.0
IPHLPAPI.DLL C:\Windows\System32\IPHLPAPI.DLL 10.0.14393.953
rasadhlp.dll C:\Windows\System32\rasadhlp.dll 10.0.14393.0
FWPUCLNT.DLL C:\Windows\System32\FWPUCLNT.DLL 10.0.14393.0
sspicli.dll C:\Windows\System32\sspicli.dll 10.0.14393.1770
ntmarta.dll C:\Windows\System32\ntmarta.dll 10.0.14393.0

Unhandled exception at 0x00007FFE77979CC1 (BBjODBC.dll) in dllhost.exe.12352.dmp: 0xC0000005: Access violation writing location 0x00000000B5D30098. occurred

Answer 1

Hi jycornell,

Thanks for posting on MSDN forum.

Unfortunately it's hard to find the root cause of this issue due to it is a custom ODBC driver.

Since it works in SQL Sever 2014, please make sure your referenced assemblies are compatibility with SQL Server 2016 and 2017. You can first test the connection and function programmatically instead of using linked server. Make sure that works fine for all versions of SQL Server.

You can also use other Third-Party ODBC driver to meet your requirements.

Thanks for your understanding and support.

Regards,

Pirlo Zhang 

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].