I’m using ODBC 32-bit,
Have the server as erpus-read08.epicorsaas.com, XXXXX
For How should SQL Server verify the authenticity of the login ID? I have With SQL Server Authentication using a login ID and password entered by the user.
the database name as SaaSXXX1_XXXXX
When I click Finish I get this
Microsoft ODBC Driver for SQL Server Version 17.05.0001
Data Source Name: Kinetic
Data Source Description:
Server: erpus-read08.epicorsaas.com, XXXXX
Use Integrated Security: No
Database: SaaSXXX1_XXXXX
Language: (Default)
Data Encryption: No
Trust Server Certificate: No
Multiple Active Result Sets(MARS): No
Mirror Server:
Translate Character Data: Yes
Log Long Running Queries: No
Log Driver Statistics: No
Use Regional Settings: No
Use ANSI Quoted Identifiers: Yes
Use ANSI Null, Paddings and Warnings: Yes
And when I click Test Data Source and get the following.
Microsoft ODBC Driver for SQL Server Version 17.05.0001
Running connectivity tests…
Attempting connection
[Microsoft][ODBC Driver 17 for SQL Server]TCP Provider: An existing connection was forcibly closed by the remote host.
[Microsoft][ODBC Driver 17 for SQL Server]Communication link failure
TESTS FAILED!
I really would like to be able to connect to this via ODBC since we have a label printing program that uses an ODBC connection to get the UPC from the Part Table when we print a Part Label.
we can access the database using the Azure Data Studio.
Any thoughts?
Karen Skipper
currently testing our Kinetic /cloud environment