July 9, 2008 at 1:24 pm
We just ran into a problem when a vendor tried to install an application on our production instance of SQL Server 2005 (EE 64 bit). The vendor says that the deploy is failing because the instance does not have SQLOLEDB as a Provider in the Server Object/Linked Servers node.
Sure enough, on our standby and dev servers, SQLOLEDB is included in the list of Providers. And the vendor is able to deploy the app to the backup server. I can't explain the difference between servers, because I followed the same procedure (as far as I know) when installing SQL 2005 on our different boxes.
Before this, we haven't had any issues with our linked servers, distributed queries, etc. Everything runs fine, using SQLNCLI I believe. But apparently the vendor's Install program requires the other provider.
I haven't found anything in the forums or Google about how to load/install/register SQLOLEDB when it is missing.
Does anyone have any ideas?
Thanks,
Elliott
BTW--There is a copy of SQLOLEDB.dll and rll on the production server C drive; just nothing showing up in the list of Providers.
July 9, 2008 at 9:00 pm
SQLNCLI.msi is available in the SQL Server\Setup BootStrap\ Folder. Try to Run that and see if this installs the required Providers.
Maninder
www.dbanation.com
July 9, 2008 at 11:24 pm
Thanks for the suggestion. And it may be a solution, although we do have SQLNCLI already present and it works fine for our distributed queries, just not for the vendor's new application.
Today we are trying a re-registration of SQLOLEDB.dll. The object was already in the Program Files(x86) folder, but didn't appear in the Provider list of Server Objects. SQLOLEDB is now shown as a Provider, so we'll have the vendor try the install again tomorrow to see if this fixes the problem.
If it doesn't, I'll look at running the msi file you suggested.
Cheers,
Elliott
July 11, 2008 at 1:43 pm
Update on the SQLOLEDB missing provider problem.
The dll existed in the Program Files, so I used RegEdit to unregister and re-register it. That caused it to show up as expected in the Provider List of the Linked Server node in Enterprise Manager.
Haven't had a chance to have the vendor re-try the deployment of his app, but this should do the trick.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply