It actually looks like your PI AF server cannot connect to its own back-end SQL server. You might want to check your AF Service and its connection to SQL on that machine. As the message suggests, you can check the AFService.exe.config (in the installation directory of PI AF) to make sure it is pointed to the correct SQL server and database. If the connection string looks correct, then you may want to check the SQL server and make sure it is available to your PI AF service.
5 of 5 people found this helpful
It is also possible that you do have the SQL Server Native Client installed but you may have enabled a TLS version that is not compatible with the Native Client you have installed. PI OLEDB itself doesn’t use the TLS protocol to talk to the PI AF Server, but the PI AF Server uses the SQL Server native client to communicate with SQL when a OLEDB connection is made.
You can inspect what versions of TLS you have enabled by inspecting these keys on your SQL server:
DisabledByDefault set to 0.
Enabled set to 1
Microsoft has released a version of SQL Server Native Client that supports newer TLS versions. You can download and install that here.