SQL 2017 / Windows Server 2016 / S1000 Error

We are trying to get OpenLink to work with SQL 2017 which is on Windows Server 2016. When we connect to a 2008 R2 box, it works but the new box isn’t working. We are getting a generic error that isn’t much help when troubleshooting.

Attached is our logs:

		Tue Mar 19 2019
17:44:31 INFO (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\mapsglbl.c:298): using rulebook C:\Program Files\OpenLink Software\UDA\bin\oplrqb.ini
17:44:31 INFO (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\prot_tcp.c:53): bound TCP protocol to 0.0.0.0.5000
17:44:31 DEBUG (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\wnt\ntjob.c:112): created job for controlling agents
17:44:31 INFO (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\wnt\ntbroker.c:1644): request broker started by system
17:44:31 DEBUG (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\wnt\ntproc.c:770): spawning "C:\Program Files\OpenLink Software\UDA\bin\www_sv.exe" +debug +internal 4844 
17:44:31 INFO (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\dbserv.c:612): started persistent www_sv (pid=3928)
17:44:46 DEBUG (c:\hfw-port-tree-62\pkg\openlink\libsrc\rpc/svc_tcp.c:380): enabled keepalive on socket 512
17:44:46 DEBUG (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\mapscode.c:178): ssis called (10.10.10.2.49988)
17:44:46 INFO (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\mapscode.c:194): request: domain=SQLServer database=DB03 serveropts=
17:44:46 INFO (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\mapscode.c:196):   connectopts= user=DB03 opsys=win32 readonly=0
17:44:46 INFO (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\mapscode.c:198):   application=ODBCAD32 processid=2352
17:44:46 DEBUG (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\maprule.c:109): solve mapping: sql:DB03:DB03:msdos:ssis:ODBCAD32:rw
17:44:46 DEBUG (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\maprule.c:145): using mapping: sql:*:*:*:*:*:*
17:44:46 DEBUG (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\mapscode.c:252): using [generic_sql] ServerProgram=sql_mv.exe
17:44:46 DEBUG (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\mapscode.c:327): connect params: domain=SQLServer db=DB03 serveropts= readonly=0
17:44:46 DEBUG (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\mapscode.c:329):   connectopts= user=DB03 opsys=win32 machine=ssis application=ODBCAD32
17:44:46 DEBUG (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\wnt\ntproc.c:770): spawning "C:\Program Files\OpenLink Software\UDA\bin\sql_mv.exe" +debug +internal 4844 +noautocommit
17:44:46 DEBUG (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\mapsglbl.c:324): setting Environment SQLSERVER
17:44:46 DEBUG (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\mapsglbl.c:331): change environment 'CURSOR_SENSITIVITY' -> 'LOW'
17:44:46 DEBUG (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\mapsglbl.c:331): change environment 'DSQUERY' -> 'SQLSERVER'
17:44:46 DEBUG (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\mapsglbl.c:331): change environment 'FREETDSCONF' -> 'c:\program files\Openlink Software\UDA\bin\freetds.conf'
17:44:46 DEBUG (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\mapsglbl.c:331): change environment 'TDSHOST' -> 'HSSQLDW123.hcgg.fr.co.hennepin.mn.us'
17:44:46 DEBUG (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\mapsglbl.c:331): change environment 'TDSPORT' -> '1433'
17:44:46 DEBUG (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\mapsglbl.c:331): change environment 'TDSVER' -> '10.0'
17:44:47 DEBUG (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\mapscode.c:431): asking agent for server handle
17:44:47 DEBUG (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\mapscode.c:453): got it!
17:44:47 DEBUG (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\mapscode.c:561): asking agent for connection handle
17:44:54 INFO (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\mapscode.c:589): agent generic_sql rejected connection (reason 53: [SQL Server]SQLServer connection failed (20002)[SQLSTATE:S1000])
17:44:54 INFO (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\mapscode.c:612): rejected DB03@ssis.ODBCAD32 ([SQL Server]SQLServer connection failed (20002)[SQLSTATE:S1000])
17:44:54 DEBUG (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\wnt\ntproc.c:233): pid 2684 died with exit code 0
17:44:54 DEBUG (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\dbserv.c:243): agent died (pid=2684)
17:44:54 DEBUG (c:\hfw-port-tree-62\pkg\openlink\binsrc\oplrqb\dbserv.c:128): removing agent generic_sql with 0 connections

I had thought this comment already posted…

Noting that this issue was also raised within the Case System.

Analysis revealed that this connection was being attempted with Enterprise Edition Release 6 components, which fully support SQL Server 2008 and previous, but do not fully support more recent security, data type, and other features.

Enterprise Edition Release 7 has been recommended, and it is now being tested to confirm that the connection to SQL Server 2016 succeeds, as is expected.