It seems that out-of-the-box, Windows 2008 r2 locks down all the security configuration of the components needed to be modified, which isn't mentioned in the article above resulting in a brick wall. I found this great article outlining all the steps in detail.īut low and behold, another hurdle I ran into while walking through this. So apparently, MSDAINITIALIZE and some other components need some security tweaking in order to run the OLE DB ODBC MySQL driver out of process. Found another bloody workaround for this issue in this other workaround, but this is getting ridiculous. Not sure why allow in process would have to be enabled. Is this true? I tried re-enabling and then I got the same hang errors I was seeing previously.ĮDIT: I noticed that everytime I execute the OPENQUERY from the MSSQL server, a connection is getting spawned on the MySQL server. Seems to suggest that I have to have Allow In Process enabled.
I even went ahead and granted dba for % host on the mysql account. Access denied.Ĭannot get the column information from OLE DB provider "MSDASQL" for linked server "SHORETEL_CDR". The OLE DB provider "MSDASQL" for linked server "SHORETEL_CDR" reported an error.
Then I receive this error even though permissions on the security account are all setup correctly SELECT * FROM OPENQUERY(MYLINKEDSERVER, 'SELECT * FROM SomeTable') When Allow In Process disabled, Testing the connection works now and returns no error. Still facing pretty much the same problem. Ugh, so I'm not out of the woods yet actually.