We are using the following settings to connect to a sql server without any issues.   The contents of our ini file is

DBMS="SNC SQL Native Client(OLE DB)"
Database=database
LogId=logid
LogPassword=pass
ServerName=Servername\SQL2012
AUTOCOMMIT=True
Lock="RC"
DBParm = "Database='database',Provider='SQLNCLI10'"

But the following connection parameter gives the error that you mentioned, in few systems recently. Earlier it was working fine.   In the same system, this message started appearing recently.  Since the connection succeeds and the application is working fine, we haven't taken it seriously.

DBMS="OLEDB"
Database=database
LogId=logid
LogPassword=pass
ServerName=ServerName\SQL2012
AUTOCOMMIT=True
Lock="RC"
DBParm="PROVIDER='SQLOLEDB',DATASOURCE='Server\SQL2012',PBMaxBlobSize='100000',PBMaxTextSize='100000',PROVIDERSTRING='Database=database'"

Happiness Always
BKR Sivaprakash

Here is what I would try:

SQLCA.DBMS = "SNC"
SQLCA.ServerName = "xxxxxxxxx"
SQLCA.AutoCommit = False  // or True, depending on your needs...
SQLCA.DBParm = "Database='xxxxxxx',Provider='SQLNCLI11',ProviderString='Server=xxxxxxxxx,nnnn'"

The only way I know to pass the non-default port number into the SQLNCLI11 provider is to use the ProviderString DBParm setting.

As I understand things, the SNC database interface will not examine or validate the content of the ProviderString setting, but will pass it undisturbed to the (SQLNCLI11) provider. However, since I have not ever used the ProviderString DBParm setting, I make no guarantee that it will work. The documentation I can find:

    https://docs.appeon.com/pb2022r2/connection_reference/ProviderString.html

    https://learn.microsoft.com/en-us/sql/relational-databases/native-client/applications/using-connection-string-keywords-with-sql-server-native-client?view=sql-server-ver16#ole-db-provider-connection-string-keywords

suggests that this is the ProviderString value that will work.

Good luck!

Hi Arnell;

  Are those the values of SQLDBCode & SQLErrText on the App's transaction object when the failure occurs?

  Also, any recent changes to the SS environment by your DBA team?

Regards ... Chris

For PORT are you using the actual port the server listens on or the word PORT? Port 1433 is the default port.

https://learn.microsoft.com/en-us/sql/relational-databases/native-client/applications/using-connection-string-keywords-with-sql-server-native-client?view=sql-server-ver16

Hi, Arnell -

I've been connecting to SQL Server databases daily for nearly 15 years using the SNC database interface, and I do not recognize nor can I find any documentation supporting a DBParm setting named "Server".

    https://docs.appeon.com/pb2019r3/connection_reference/ch01s01.html

We identify the server via the SQLCA.ServerName property, but not in DBParm. While there does exist a ServerName DBParm setting, it is described as being for use only with the ORA database interface.

If you are trying to copy configuration settings from ODBC (???), I cannot say with certainty, but I doubt very much that will work.

Using the SQLNCLI11 provider, we set only the following:

SQLCA.DBMS = "SNC"
SQLCA.ServerName = "servername\instance"
SQLCA.AutoCommit = False
SQLCA.DBParm = "dbparm-settings"

DBParm Settings used:
  Database='databasename'
  Provider='SQLNCLI11'
  TrustedConnection=1        (we connect to SQL Server via Windows Authentication)
  TrimSpaces=1
  DateFormat='mm/dd/yyyy'
  TimeFormat='hh:mm:ss.ffffff'
  DateTimeFormat='mm/dd/yyyy hh:mm:ss.ffffff'

Best regards, John