Windows Server 2016 - 'MSOLEDBSQL' provider is not registered on the local machine.

Yankee30 206 Reputation points

Windows Server 2016 - We've an application running on the server which relies on MSOLEDBSQL drivers for connection but out of nowhere intermittently we keep getting errors :-

DB Error.The 'MSOLEDBSQL' provider is not registered on the local machine.

failing the application to not work.
Re-installing the MSOLEDBSQL driver fixes the problem. We're under the impression that the drivers are getting corrupted as re-installing fixes the issue or it might be something else.

Can anyone provide a way forward on how to figure out this issue ?
There's no standard time at which the issue appears & there's nothing in the system/application logs which points to what's causing the issue.

Any help will be good. Thanks in advance

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,314 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. PandaPan-MSFT 1,901 Reputation points

    Hi @Yankee30 ,
    You may put the following order into powershell and see the current situation of your driver:

    (New-Object System.Data.OleDb.OleDbEnumerator).GetElements() | select SOURCES_NAME, SOURCES_DESCRIPTION

    We may can't locate the specify reason what causes the problem but you can prevent it from happening again, checking if you have missed something.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment"

    1 person found this answer helpful.

  2. Dave Patrick 426.2K Reputation points MVP

    The application developer will be your best resource to troubleshoot this issue.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

  3. Erland Sommarskog 102.4K Reputation points

    If the driver is getting corrupted, you have green men in the machine that is corrupting the disk in general.

    I would look at the antivirus and see if may have quarantined something it should not have messed with.