Microsoft SQL Server Spatial Reader now fails to connect post upgrade to 2020.1. It worked with 2020.0. We are getting this error: Microsoft SQL Server Spatial Reader: Failed to connect using Microsoft OLE DB Driver for SQL Server. Provider error '(-2146824582) Provider cannot be found. It may not be properly installed.'. - is there something we need to install?
Question
Microsoft SQL server Spatial reader failing
+2This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+22- Contributor
Just a thought:
Are both 32 or 64 bits?
The bits of the FME install have to match the SQL Server client components.
+11- Enthusiast
Same problem here. Worked this morning, broken this afternoon after upgrading to 2020.1.2. Haven't dug in yet to find out about bitness. Later: actually this isn't a problem for our script. Yes the warning is there, but the next line is "Microsoft SQL Server Non-Spatial Reader: Trying to connect using SQL Server 2012 Native Client...", and that succeeds.
Now to see if we can reverse the try order, or just tell it to not try OLE DB at all.
+8Same here upgrading from FME Server 2017 to FME Server 2020.2.0.0
Did anyone ever find a resolution for this?
I installed this and now the workspace is working.
I installed this and now the workspace is working.
Did you have to install both 64 and 32-bit versions?
+7- Supporter
For the record I had this problem recently with FME 2022 and the client libary that actually worked was:
sqlncli.msi (64 bit for 64 bit FME)
At time of writing found here:
https://www.microsoft.com/en-us/download/details.aspx?id=50402
But with microsoft these links don’t seem to last forever.