Hallo Paul, thanks for your answer. I read through the knowledgebase article. My scenario is nr 1, slightly changed: my network administrator installed the “default” Sql Server instance for me and therefore I don’t need to give an instance name - just localhost is enough. Please consider that Ms Sql Server Managment studio can connect to that database both from the same machine and from another machine on the same network by using Sql Server Authentication. So I wouldn’t look for an incorrect parameter in the server installation, neither in the connection string. So where is the problem? The only difference I see between Management Studio and Ignition is the communication library: .NET vs JDBC. But again this is my 10th project with Ignition and Sql Server and this is the first time I cannot communicate with the database. Only difference from preceding projects: Windows Server 2016 instead of Windows 7 through 10 Professional and the machine is in a Windows domain instead of a stand alone machine.
Any more ideas?
Thanks again, regards
EDIT: solution found
Never had the need to do this before, but this was the way to go: just tell SQL Server that you want it to listen to port 1433 (it’s just the default port for the default instance as in my case).
I had to configure