DataServer client terminates with errors (1461) and (6028)

DataServer client terminates with errors (1461) and (6028).

DataServer client terminates with errors (1461) and (6028) after changing to an alternative ODBC driver.

Pro2 thread fails to starts with errors (1461) and (6028) after changing the ODBC driver.

DataServer client terminates with errors (1461) and (6028) when attempting to use the SQL Server Native Client (SQLNCLI11.dll) against a schema holder generated using the SQL Server ODBC driver (SQLSRV32.DLL).

Schema holder has not been re-generated against the new ODBC driver.

For Pro2SQL, client logging shows that the thread is attempting to load replication procedures.

Some replication procedures have loaded successfully.

4GL 4GLTRACE       RUN ReplLogPost in bprepl/ReplLib.p "4 Successfully Loaded Procedure for s2k.Invoice." [Main Block - bprepl/LoadProcLib.p @ 157]
4GL 4GLTRACE       Func getProperty "LOG_FILE_SUFFIX" [ReplLogPost - bprepl/ReplLib.p @ 649]
4GL 4GLTRACE       Return from getProperty ".log" [bprepl/ReplLib.p]
4GL 4GLTRACE       Return from ReplLogPost [bprepl/ReplLib.p]
4GL 4GLTRACE       Return from PUBLISH ReplLogPost [bprepl/LoadProcLib.p]
4GL 4GLTRACE       PUBLISH ReplLogPost "4 Loading Procedure for s2k.Item." [Main Block - bprepl/LoadProcLib.p @ 115]
4GL 4GLTRACE       RUN ReplLogPost in bprepl/ReplLib.p "4 Loading Procedure for s2k.Item." [Main Block - bprepl/LoadProcLib.p @ 115]
4GL 4GLTRACE       Func getProperty "LOG_FILE_SUFFIX" [ReplLogPost - bprepl/ReplLib.p @ 649]
4GL 4GLTRACE       Return from getProperty ".log" [bprepl/ReplLib.p]
4GL 4GLTRACE       Return from ReplLogPost [bprepl/ReplLib.p]
4GL 4GLTRACE       Return from PUBLISH ReplLogPost [bprepl/LoadProcLib.p]
4GL 4GLTRACE       Run bprepl/repl_proc/rs2k_Item.p PERSIST [Main Block - bprepl/LoadProcLib.p @ 120]
4GL 4GLTRACE       Return from Main Block [bprepl/repl_proc/rs2k_Item.p] ERROR
4GL -- (Procedure: 'bprepl/LoadProcLib.p' Line:120) Schema holder does not match database schema -- file s2k_503.dbo.item field catdescription.Aborting execution in order to protect database and application integrity. (1461)
4GL 4GLTRACE       Return from Main Block [bprepl/LoadProcLib.p]
4GL 4GLTRACE       Return from Main Block [bprepl/ReplProc.p]
4GL -- SYSTEM ERROR: A/R block doesn't match caller's. Transaction inconsistency. (6028)

Error (6028) disappears after update to 11.7.5; error (1461) persists:

4GL 4GLTRACE       Run bprepl/repl_proc/rs2k_Item.p PERSIST [Main Block - bprepl/LoadProcLib.p @ 120]
4GL 4GLTRACE       Return from Main Block [bprepl/repl_proc/rs2k_Item.p] ERROR
4GL -- (Procedure: 'bprepl/LoadProcLib.p' Line:120) Schema holder does not match database schema -- file s2k_503.dbo.item field catdescription.Aborting execution in order to protect database and application integrity. (1461)
4GL 4GLTRACE       Return from Main Block [bprepl/LoadProcLib.p]
4GL 4GLTRACE       Return from Main Block [bprepl/ReplProc.p]
4GL 4GLTRACE       Return from Main Block [bprepl\RunReplProc.p]
...
 

Definition of "catdescription" field from the Sports2000.Item table generated by SQL Server ODBC driver:

ADD FIELD "catdescription" OF "item" AS character 
  FORMAT "x(320)"
  INITIAL ?
  POSITION 3
  ORDER 5100
  FOREIGN-POS 10
  FOREIGN-NAME "catdescription"
  FOREIGN-TYPE "LONGVARCHAR"
  DSRVR-PRECISION 2147483647
  DSRVR-SCALE 0
  DSRVR-LENGTH 2147483647
  DSRVR-FLDMISC 0
  FIELD-MISC22 "Y"
  QUOTED-NAME """catdescription"""
  MISC-PROPERTIES ""

Definition of "catdescription" field from the Sports2000.Item table generated by SQL Server Native Client ODBC driver:

ADD FIELD "catdescription" OF "item" AS character 
  FORMAT "x(320)"
  INITIAL ?
  POSITION 3
  LENGTH 32000
  ORDER 5100
  CASE-SENSITIVE
  FOREIGN-POS 10
  FOREIGN-NAME "catdescription"
  FOREIGN-TYPE "VARCHAR"
  DSRVR-PRECISION 32000
  DSRVR-SCALE 0
  DSRVR-LENGTH 32000
  DSRVR-FLDMISC 0
  FIELD-MISC22 "Y"
  QUOTED-NAME """catdescription"""
  MISC-PROPERTIES ""

This is expected behavior. The data type for the field returned by the ODBC driver differs from the data type of the field stored in the schema holder. 

Re-generate the schema holder against the new ODBC driver.

For OpenEdge applications using the DataServer where the original OpenEdge database is still available with definitions that match the SQL Server database:

1) Create a new empty database.
2) In Data Administration

• Go to DataServer > MS SQL Server Utilities, run the Create DataServer Schema utility to pull the definitions from SQL Server with the new ODBC driver.
• Connect to the original OpenEdge database.
• Go to Database > Select Working Database => choose the DB where Type = MSS.
• Go to DataServer > MS SQL Server Utilities > Schema Migration Tools > Adjust Schema.
• Enter the name of the Original OpenEdge DB and click OK.

For OpenEdge applications using the DataServer where the original OpenEdge database is not available:

1) Go to article#  How to migrate the DataServer schema between 2 major releases?.
2) Follow the steps in the "In OE 11.x Data Administration Tool" section.


For Pro2:

1) Connect to the existing schema holder with Data Administration.
2) Go to Database > Select Working Database => choose the DB where Type = MSS.
3) Click OK then No.
4) Select DataServer > MS SQL Server Utilities > Delete DataServer Schema => Yes.
5) Select DataServer > MS SQL Server Utilities > Create DataServer Schema to pull the definitions from SQL Server with the new ODBC driver.
 

References to other documentation:

Progress article(s):
 ODBC errors occur when using VARCHAR(MAX) type field in WHERE clause of query run via DataServer for MS SQL Server
 SQL DataServer connection fails after changing to TLSv1.2