The OLE DB provider "MSDASQL" for linked server " " supplied inconsistent metadata for a column.The column " " (compile-time ordinal 2) of object " " was reported to have a "DBCOLUMNFLAGS_ISLONG" of 0…

Applies To: SQL 2012 and above. (Requires supportability towards Multi-Subnet Failover) Understanding of the Issue: Let us consider a situation where we want to create a Linked Server to pull data from SQL Server Always On (using the Listener name) onto our local SQL Server (or another SQL Server) and along with it also leverage…


Error while connecting to SQL Server – “Could not connect because the maximum number of ‘1’ user connections has already been reached.”

Applies To: Tested on SQL Server 2008, 2008 R2, 2012 and 2014. Issue: In this blog, I would like discuss about one of most commonly faced issues that you may encounter when connecting to the SQL Server. When you try to connect SQL Server you may get the error below. The error can occur while connecting…


Report Manager: “System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.”

Applies To: Tested on SQL Server Reporting Services 2008, 2008 R2, 2012 and 2014. When you browse Report Manager URL, you get an HTTP 500 error or a blank page (in case if you have disabled friendly HTTP messages) on the browser window. When you check the Reporting Services log files you would find the…


Import / Deployment / Execution of SSIS packages fails after you migrate SSISDB from SQL Server 2012 to SQL Server 2014.

  In this blog, I would like to discuss about one of the interesting scenarios that you would witness after you migrate your existing SSISDB catalog from SQL Server 2012 to SQL Server 2014. Issue: Whenever you try to deploy your new Integration services projects to the migrated SSISDB catalog (of SQL Server 2014) using…


“… an error occurred during the pre-login handshake.” & “[DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error” when connecting to SQL Server.

This blog is regarding one of most commonly faced issues that you may receive when connecting to the SQL Server. Mostly you may run into this issue after some improper Windows security update (say KB2655992 in my case) or improper application of Poodle security fix.   ISSUE DESCRIPTION FROM SQL CONNECTIVITY STANDPOINT: When we try…