Jump to content

Arual

Members
  • Posts

    3
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Arual's Achievements

Seeker

Seeker (1/7)

1

Reputation

  1. We finally found a solution that worked just by continuing to test different options. In case this helps anyone else, here is what we found that finally worked. $sConnStr = "Provider=SQLNCLI11;SERVER=servername,port;DATABASE=dbname;DataTypeCompatibility=80;UID=user;PWD=pass"
  2. We have AutoIt code that performs a connection to an MS SQL database running SQL server 2012, tls 1.0. It has worked successfully for years. Today, our IT department migrated our database to a new server that is running SQL server 2016, tls 1.2. Now our connection string is no longer working. Here is the original that was working in SQL server 2012 $sConnStr = "DRIVER={SQL Server};SERVER=servername,port;DATABASE=dbname;UID=user;PWD=pass" When that would run on the new server in SQL server 2016. We are getting the error [Microsoft][ODBC SQL Server Driver][DBNETLIB]SSL Security error We tried changing the connection string to $sConnStr = "DRIVER={SQL Server Native Client 11.0};SERVER=servername,port;DATABASE=dbname;UID=user;PWD=pass" The new error we received is [Microsoft] TCP Provider: An existing connection was forcibly closed by the remote host. We can log in successfully using SSMS using the server name, port and user/pass. Any suggestions on what we need to change in order to get the connection to work again?
  3. I am also having this same issue. I have code that does data entry that about 150 people are using at my workplace. I had to use mouse clicks because the system we have to enter data into is resistant to using shortcut keys. Two users recently received a new computer. Now, even though their resolution is set to 1280x1024, AutoIt detects the screen size as 819x1024. Any ideas?
×
×
  • Create New...