[Microsoft][ODBC SQL Server Driver]Dialog failed

Databases
1

after windows 10 update this error show now [Microsoft][ODBC SQL Server Driver]Dialog failed

any idea what is this using msSQLserver 2012 sp2

2

Is that with MBS Plugin?

3

if the client is Windows 10 1803 64-bit, there is a good chance that the 1803 update broke the connexion. As of now, I am not aware of a fix. There are several threads on the subject on various forums. It broke connexions with ODBC, ADODB. Even SSMS can’t connect anymore! 32-bit systems appear to be immune.

You may also look at the issue of SMB V1 if your SQL Server sits on an older Windows version. You can repair that issue.
Edit: KB4284848 would apparently fix this issue.

This whole mess is why I am porting my databases (and code) to PostgreSQL. A lot of work. Thank you MS!

4

no
i have to try with Christian plugin

5

It works here with Win10 1803 on 2018 R1.1 in 32 or 64 bit mode. I use the ODBC API.

6

hey Tanner can you show the connection string to look it on my Dev computer no works

7

Sure Alex. Here’s the routine I use in my apps that use SQL Server. (Pls ignore the Linux parts, I’ve been hacking to get them to work with PopOS.)

[code]// preload libs, this helps on Linux to find them
#if TargetMacOS then
Dim libtdsodbc As Folderitem = GetFolderItem(“libtdsodbc.dylib”)
#endif

// NEED FIX to use with PopOS
#If TargetLinux
// Dim libodbcinst As Folderitem = GetFolderItem(“/usr/lib/x86_64-linux-gnu/libodbcinst.so.1”)
Dim libtdsodbc As FolderItem = GetFolderItem(“/usr/Lib/x86_64-linux-gnu/odbc/libtdsodbc.so”)
Dim s As New SoftDeclareMBS
// Call s.LoadLibrary(libodbcinst.AbsolutePath)
Call s.LoadLibrary(libtdsodbc.AbsolutePath)
#EndIf

// connect
BC_CON = New SQLConnectionMBS

Try
// we used Microsoft SQL Server 2008 and run app on Windows to test this (works on 2005 as well - mas)
#If TargetWindows Then
Dim cs As String = “Driver={SQL Server};Server=” + serverAddress + _
“;UId=” + serverLogin + _
“;PWD=” + serverPassword + _
“;Database=” + serverDatabase + _
“;TDS_VERSION=7.2;Port=” + serverPort.ToText
#EndIf

#If TargetLinux Then
Dim cs As String = “DRIVER={FREETDS};Server=” + serverAddress + _
“;UId=” + serverLogin + _
“;PWD=” + serverPassword + _
“;Database=” + serverDatabase + _
“;TDS_VERSION=7.2;Port=” + serverPort.ToText
BC_CON.Option(BC_CON.kOptionLibraryODBC) = libtdsodbc.AbsolutePath
#EndIf

#If TargetMacOS Then
// *** NOTE *** manual ODBC connection not required (i.e. no ActualTech named DSN needed)
Dim cs As String = “DRIVER={FREETDS};Server=” + serverAddress + _
“;UId=” + serverLogin + _
“;PWD=” + serverPassword + _
“;Database=” + serverDatabase + _
“;TDS_VERSION=7.2;Port=” + serverPort.ToText
#EndIf

#If Not TargetWindows Then
BC_CON.SetFileOption BC_CON.kOptionLibraryODBC, libtdsodbc 'not for Win32
#EndIf

BC_CON.Option(“UseAPI”) = “ODBC”
BC_CON.Connect(cs, “”, “”, SQLConnectionMBS.kODBCClient)
BC_CON.Scrollable = False // disabling scrolling cursors is much faster for Microsoft SQL Server…
If DebugBuild Then System.Debuglog currentMethodName + “: BC_CON connected”

Catch r As RuntimeException
If DebugBuild Then System.Debuglog currentMethodName + “: BC_CON connection error”
MsgBox r.message
End Try[/code]

8

There is the difference! you are using FreeTDS! I was using the native client.

You had me scratching my head for a while! Good to know that FreeTDS works fine! Thank you!

9

Please also read my blog article here:
https://www.mbsplugins.de/archive/2018-03-03/Microsoft_SQL_Server_connectiv