Strange Behavior with MSOLEDB19 driver

  • We have recently changed many of our SSIS packages from using the depreciated SQL Native 11 driver to the now recommended Microsoft OLEDB 19 driver.  Primarily because it support the MULTISUBNETFAILOVER attribute required when pointing a data connection at an availability group listener.

    Everything appeared to be working but then some packages randomly stopped working. The packages are called by a SQL Agent Job.

    First we got this message

    The requested OLE DB provider MSOLEDBSQL19.1 is not registered. If the 64-bit driver is not installed, run the package in 32-bit mode. Error code: 0x00000000.

    Despite nothing changing, the job just starting failing.

    We changed the job step to "32 bit execution", and the job/package worked again.

    Until the next day, it failed again, but this time with

    The requested OLE DB provider MSOLEDBSQL19.1 is not registered. If the 32-bit driver is not installed, run the package in 64-bit mode. Error code: 0x00000000.

    Again, switching 32bit off in the job step fixed it but I can't understand what's causing this behavior or why it's randomly not seeing the installed version of each driver.   There should be no reason it ever needs to run in 32bit mode or why it sometimes only works in either mode.

  • this looks like a failover issue where the servers installed version isn't the same - one has a 32 bit version and the other a 64bit version.

    I would check this.

  • No, it's not a failover issue.  The AG is set to manual failover and has not been failed over between the job fail events.  The job/package is running consistently from one server.

  • regardless - check every server that is part of that AG and ensure that only the 64 bit version of the driver is installed.

    use script from https://www.powershellgallery.com/packages/LegacyData/3.2.0/Content/Public%5CGet-InstalledDatabaseDriverList.ps1

    can be called as

    Get-InstalledDatabaseDriverList -name ole|ft

    which will give you all OLEDB drivers installed.

     

  • This was removed by the editor as SPAM

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply