Microstrategy desktop odbc driver for sql server professional#
Pinal is an experienced and dedicated professional with a deep commitment to flawless customer service. To freely share his knowledge and help others build their expertise, Pinal has also written more than 5,500 database tech articles on his blog at. Pinal has authored 13 SQL Server database books and 40 Pluralsight courses. He holds a Masters of Science degree and numerous database certifications. Pinal Dave is an SQL Server Performance Tuning Expert and independent consultant with over 17 years of hands-on experience. Have you encountered a similar error? If yes, what was the solution in your case? There could be many other issues of client connectivity and it all depends on error message. The ideal solution was to make sure the firewall is configured correctly as mentioned in books online Configure the Windows Firewall to Allow SQL Server Access Once the alias were created, we could connect to the SQL server successfully using SQLMACHINE\INSTANCE_NAME. SOLUTION / WORKAROUNDĪs a workaround, we went ahead and created the SQL alias for the TCP/IP protocol. If we connect using SQLMACHINE,2433 then it works.Īt this point we anticipated the UDP port is FILTERED for some reason and hence we are not able to get the instance names mapped to the port numbers.If we connect using SQLMACHINE\INSTANCE_NAME then it fails.Ping was working fine and we could get the response.SQL Server instance which we were trying to connect was a named instance, which was listening on non-default port 2433.
We tried below steps to narrow down the issue. We looked into the application and found that the SQL connection from the client application were constantly failing with the following connection error: We all joined the call and desktop sharing to learn more about the issue. As a part of my quick consultancy, I was contacted by a client who was having trouble where the application was not able to connect to SQL Server.