Friday, March 23, 2012

Linked Server Issue

I am trying to set up a link between 2 SQLServer databases. One is on
server named ACT-S91 and the other is on server named ACT-S92. I ran the
following statement on ACT-S91 - which said it worked.
sp_addlinkedserver N'ACT-S92', ' ', N'SQLOLEDB', N'ACT-S92'
So, at this point I should have ACT-S91 and ACT-S92 linked. But when I run
a query from ACT-S91 trying to access the data on ACT-S92 I get the
following error:
Server: Msg 7302, Level 16, State 1, Line 1
Could not create an instance of OLE DB provider 'SQLOLEDB'.
OLE DB error trace [Non-interface error: CoCreate of DSO for SQLOLEDB
returned 0x8007007f].
I assume I am missing something in setting up the link. But from the
documentation I can't determine what that something might be. Any help?
--
Edward Fultz
Sr. Software Engineer
Pamet Systems
Acton, Ma
www.pametsystems.comIf you look at the properties of the linked Server in Enterprise Manager,
under Security, what context is the connection to the linked server being
made.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||I used the one that says Be made using the login's current security context.
Since I can get into both servers I assumed I would have no problems. I
have no specific local logins defined. We use windows authentication on
both machines. So, if I can get into both machines shouldn't this have been
right?
--
Edward Fultz
Sr. Software Engineer
Pamet Systems
Acton, Ma
www.pametsystems.com
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
news:hXKEeD%23UEHA.2616@.cpmsftngxa10.phx.gbl...
> If you look at the properties of the linked Server in Enterprise Manager,
> under Security, what context is the connection to the linked server being
> made.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>|||I tried setting a specific security user id and password and that, also,
provided the same error.
--
Edward Fultz
Sr. Software Engineer
Pamet Systems
Acton, Ma
www.pametsystems.com
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
news:hXKEeD%23UEHA.2616@.cpmsftngxa10.phx.gbl...
> If you look at the properties of the linked Server in Enterprise Manager,
> under Security, what context is the connection to the linked server being
> made.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>|||Figured out the problem appears to be that you can't use the SQLServer
option. But on our server there are no providers loaded so we are
researching why this is and how to fix it. Anyone have any ideas how to get
providers loaded? We have 2 other servers and the providers show up there
fine. The server on which they don't show up is a Server2003 server running
SQLServer2000 (was recently upgraded to Server2003).
--
Edward Fultz
Sr. Software Engineer
Pamet Systems
Acton, Ma
www.pametsystems.com
"Ed Fultz" <efultz@.yahoo.com> wrote in message
news:%235FnB88UEHA.4092@.TK2MSFTNGP11.phx.gbl...
> I am trying to set up a link between 2 SQLServer databases. One is on
> server named ACT-S91 and the other is on server named ACT-S92. I ran the
> following statement on ACT-S91 - which said it worked.
> sp_addlinkedserver N'ACT-S92', ' ', N'SQLOLEDB', N'ACT-S92'
> So, at this point I should have ACT-S91 and ACT-S92 linked. But when I
run
> a query from ACT-S91 trying to access the data on ACT-S92 I get the
> following error:
> Server: Msg 7302, Level 16, State 1, Line 1
> Could not create an instance of OLE DB provider 'SQLOLEDB'.
> OLE DB error trace [Non-interface error: CoCreate of DSO for SQLOLEDB
> returned 0x8007007f].
>
> I assume I am missing something in setting up the link. But from the
> documentation I can't determine what that something might be. Any help?
>
> --
> Edward Fultz
> Sr. Software Engineer
> Pamet Systems
> Acton, Ma
> www.pametsystems.com
>

No comments:

Post a Comment