Skip to content

How to fix an error of OLE DB provider SQLNCL11 has not been registered in MS SQL Linked Server

'I am getting this email from my client as follows:

We seem to have an issue with the with the drill down app. It appears that we are not getting any results for our company inventory and from the XYZ database in the drill down, we believe the last time this specific function was working correctly was Jan 30 2019.

I have attached some screenshots which Susan has sent to me that should be of some help to you. In addition, I have checked a couple of known part numbers in the supplier website drill down and also checked stock directly in the XYZ function and no results were returned.

We think the other functions are still working fine.
Can you investigate please?

As the result of the above email, I logged into client’s server and run one particular MS SQL Stored Procedure. Its purpose was to add records from 2 different databases whenever and inventory part numbers were requested. In this scenario, the client gets the Inventory from the local database and from another remote database which is from a different company. The two companies share the same inventory. To explain the reason it is working this way, it is beyond the scope of this article.

This is the error I got when I run the Stored Procedure:
Msg 7403, Level 16, State 1, Procedure GetInventoryBasedOnPN, Line 34 [Batch Start Line 17] The OLE DB provider "SQLNCLI11" has not been registered.

What I suspected happened is that there were 3 versions of Ms SQL installed on that server and 2 of them were un-installed lately. It seems the sql native client driver was removed as well.'...

https://www.dfarber.com/computer-consulting-blog/articles/how-to-fix-an-error-of-ole-db-provider-sqlncl11-has-not-been-registered-in-ms-sql-linked-server/

T-SQL Script to Check SQL Server Job History

'Yesterday my long time customer from New Zealand asked me during our regular weekly meet of Comprehensive Database Performance Health Check if I know a T-SQL Script to Check SQL Server Job History.

Absolutely, here is the simple script, I use to check all the SQL Server Agent Job History. Please note that while writing this script, I have taken help of the function agent_datetime which I have blogged earlier a few years ago.

Let us see the T-SQL Script:

1
2
3
4
5
6
7
SELECT jobs.name AS 'JobName',
msdb.dbo.agent_datetime(run_date, run_time) AS 'Run Date Time',
history.run_duration AS 'Duration in Second'
FROM msdb.dbo.sysjobs jobs
INNER JOIN msdb.dbo.sysjobhistory history
ON jobs.job_id = history.job_id
WHERE jobs.enabled = 1

'...

https://blog.sqlauthority.com/2018/12/22/sql-server-t-sql-script-to-check-sql-server-job-history/

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160}...

'The Error

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Background

It would appear that an Apple application was installed on these machines at some point and that it did not do a proper install.  The W10 upgrade exacerbated the issue due to missing security accounts after a W10 upgrade.  The fix is to give local administrators and System rights to the DCOM.  To do this you have to modify premissions on two registry keys and then change the DCOM premissions.  Pretty easy to do.

FIX...'...

https://shauncassells.wordpress.com/2015/09/28/windows-10-event-10016-fix-the-application-specific-permission-settings-do-not-grant-local-activation-permission-for-the-com-server-application-with-clsid-d63b10c5-bb46-4990-a94f-e40b9d520160-and-a/

Performance Monitoring and Tuning Tools

'Microsoft SQL Server provides a comprehensive set of tools for monitoring events in SQL Server and for tuning the physical database design. The choice of tool depends on the type of monitoring or tuning to be done and the particular events to be monitored.

Following are the SQL Server monitoring and tuning tools...'...

https://docs.microsoft.com/en-us/sql/relational-databases/performance/performance-monitoring-and-tuning-tools?view=sql-server-2017