Page 1 of 1

prAuto not finding Native Client

Posted: Wed 17 Jul 2013 13:09
by MartyN
I'm using version unidac41d16pro.
I have a client who has been using our app for almost a year and now it won't connect. Of course they deny changing anything. But in my research the app would not even find the server. We used his SSMS 2012 to see the server and query tables. I reinstalled his sqlncli version 11 but it still would not connect. The work station is win7 x64. I wrote a little test app and just happened to change the OLEDBPRovider to prSQL and it connected. So my question is why didn't the prAuto locate either sqlncli or the OleDB driver? Also on x64 machines does the TUniConnection component search both the WOW64 and SYSTEM32 directories?

Re: prAuto not finding Native Client

Posted: Thu 18 Jul 2013 12:31
by AndreyZ
UniDAC supports SQL Native Client 11 since version 4.2.7. Therefore, to work with SQL Native Client 11, you should upgrade UniDAC at least to this version.
When the OLEDBProvider SQL Server specific option is set to prAuto, UniDAC looks for an available provider in the following sequence: SQL Native Client 11, SQL Native Client 10, SQL Native Client 9, OLEDB. The first found provider from the sequence is used. If there is no SQL Native Client version installed, UniDAC uses the OLEDB provider. In such case, there is no difference between prSQL and prAuto.
If you can connect to the server with OLEDBProvider set to prSQL but cannot connect to it with OLEDBProvider set to prAuto, please specify the exact error message that occurs. Also, make sure that there are no SQL Native Client 10 and SQL Native Client 9 installed. Maybe, the problem is caused by their incorrect settings.