Linked Server Problems with all providers

Im having problems with linked servers on one particular computer and am out
of ideas. The box is an XP SP2, SQL server 2000 SP3. When i create a linke
d
server of any type, clicking on "tables" or "views" in the enterprise manage
r
list, gives the following error:
Error 7399: OLE DB provider 'SQLOLEDB' reported an error.
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBinitialize::Initialize
returned 0x80004005: ].
This particular LSN is pointing to another SQL server machine. Regardless
of what provider i choose, i get the same error (the error message changes
the provider based on the provider of the LSN).
I am an administrator on both boxes, have disabled virus protection, the
windows firewall on the XP box is disabled (by a group policy on the domain)
,
and i have enabled inbound and outbound traffic in the dcomcnfg.exe.
LSN's created on other computers work fine. Any ideas?You can get this error with timeout issues. Refer to the
following:
Error message when you execute a linked server query in SQL
Server: "Timeout Expired"
http://support.microsoft.com/?id=314530
You can also double check the security mappings for the
linked servers.
You will also want to check the connectivity - try pinging
the other servers from the box you are having problems with.
Ping by server name and IP.
-Sue
On Wed, 15 Mar 2006 06:56:28 -0800, John Kurtis <John
Kurtis@.discussions.microsoft.com> wrote:

>Im having problems with linked servers on one particular computer and am ou
t
>of ideas. The box is an XP SP2, SQL server 2000 SP3. When i create a link
ed
>server of any type, clicking on "tables" or "views" in the enterprise manag
er
>list, gives the following error:
>Error 7399: OLE DB provider 'SQLOLEDB' reported an error.
>OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBinitialize::Initializ
e
>returned 0x80004005: ].
>This particular LSN is pointing to another SQL server machine. Regardless
>of what provider i choose, i get the same error (the error message changes
>the provider based on the provider of the LSN).
>I am an administrator on both boxes, have disabled virus protection, the
>windows firewall on the XP box is disabled (by a group policy on the domain
),
>and i have enabled inbound and outbound traffic in the dcomcnfg.exe.
>LSN's created on other computers work fine. Any ideas?|||Thanks for the reply. However im 99% sure that its not a timeout issue. I
get the error immediately after i click on "tables" or "views" in enterprise
manager.
Pings from the box that is having problems come back fine, both with IP as
well as name.

Linked Server PROBLEM For MySQL Database

I created a ODBC DSN on my Windows Server for a remote UNIX box MySQL database. The TEST button returns the 'successful' message for the MySQL databaser. Also, when I use an ODBC DSNless string I found, that also successfully connects when I use it in some ASP pages.

However, I can not get a successful connection in the Enterprise Manager trying to use the DSN I created nor the DSNless string I used in the ASP pages. Can anyone tell me how to config the Enterprise Manager Linked Server settings listed below to connect to the MySQL database(s).

I added a new linked server, and selected the Microsoft OLEDB Provider for ODBC Drivers as the Provider name.

Does anyone know how do I configure the items below:

On the General tab:" option.
Product Name: xxxxxxxxxxxxxxxxxx
Data Source: xxxxxxx
Provider String: xxxxxxxx
Location: xxxxxxx
Catalog: xxxxx

On the Security tab:" option.
Remote Login: xxxxxx
With password: xxxxxx

Thanks.I found a wonderful solution to this problem...

http://bside.typepad.com/lifebsideben/2003/08/mysql_mssql_lin.html

In case the link is gone, here is the way to create a Linked Server to a MySQL database, in a nutshell...

1) Create a System DSN on the server running MSSQL, connecting to the MySQL database. Let's call it <the_new_mysql_dsn>.

2) Run the following stored procedure, with appropriate arguments...

EXEC sp_addlinkedserver @.server='<linked_server_label>', @.srvproduct='MySQL', @.provider='MSDASQL', @.datasrc='<the_new_mysql_dsn>'

-------

You can then open up ol' Enterprise Manager and see the new linked server added in. Right click on it to see the Properties. On mine, the settings showed up as...

Linked server: <linked_server_label>
Provider name: Microsoft OLE DB Provider for ODBC Drivers
Product name: MySQL
Data source: <the_new_mysql_dsn>

Everything else is blank.

-------

Incidentally, just to try it out, I deleted my new linked server, and then added a new one, using the following settings...

Linked server: <linked_server_label>
Provider name: Microsoft OLE DB Provider for ODBC Drivers
Provider string: DRIVER={MySQL ODBC 3.51 Driver};DESC=;DATABASE=<mysql_database>;SERVER=<mysql_server>;UID=;PORT=;OPTION=0;STMT=;

And it works as well (the connection string was generated within Visual Interdev). I am using no passwords yet, I'm still in the early development phases, but this should handle the basics of connecting to a MySQL database from SQL Server.

Linked server problem

I linked two sql servers (one an x64 sql 2005 server the other a sql 2000 x86 server). The link is from the x64 box to the x86 box and I used Windows authentication to forge the links.

When the developer (who has Windows accounts on both boxes) logs in locally to the x64 box and runs a query, data is returned from the linked server. But when the same developer logs into his own client box and uses Management Studio to access the x64 box (via Windows authentication) and run the same query, he gets this error message"

"Login failed for user '(null)'. Reason: not associated with a trusted SQL Server Connection"

I presume that the developer should be able to access this data from his own box or can the linked data only be gotten from an account logged into the x64 box?

TIA,

barkingdog

I'm a little confused about what you mean by 'windows authentication' to forge the links.

when you create a linked server, you have the following options:

map a local login to a login on the remote server

connect using the user login's security context

connect using a specific (provided) login's security context

Whenever I've seen the above error, it has been because a developer had the server registered incorrectly in EM.

:

|||

Under SSMS, I thought that those options only applied when the connection trying to access the linked server was not listed in the top box ("Local server login to remote server login mappings".). So I ignored those options. Maybe I dun wrong!

The developer who is trying to access data on the linked server from SSMS from his own box is listed (using Windows authentication) in the Local Login section of the Linked server properties box of the x64 server. "Impersonate" is selected for that developer. No names are supplied for the Remote User\Remote password box as his Windows authentication will be used on the linked box. (Or so I think...)

TIA,

barkingdog

|||

I woul dfill in the other two boxes and see if that works.

I am struggling with my own linked server issues right now, related to windows authentication accross linked servers, but we would be using the

'connect using the user's login'.

You might try that and tell me if it works. ;)

|||

Here's what I have so far:

Suppose Server B is linked to Server A via a "Link Account". When I log on to Server B (using Remote Desktop) as "Link Account" I can successfully pull data from Server A, so the link is working. The problem: I logged into my own local workstation (not Server A or Server B) as "LinkAccount" fired up SSMS, connected to Server B as that account, and tried to pull the same data that I did earlier. The attempt fails saying that I am using a "null" account and no sql account exists.....blah, blah, blah.

I found this SQL 2005 BOL link that describes the situation:

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/9e302c29-639d-4509-ba1e-cf452582c5c3.htm

Apparently, what I wanted to do was not as simple as I thought it should be. I am creating a "double hop" and the servers need to be prepared as described in the help article. Otherwise, the error message is to be expected!

linked server login problem... with a particular login... on a particular box

Im having a problem with one particular Linked Server Login. I've created
two of them. Neither of which has an existing Login on the Linked Server and
both of which are mapped to a member of SA. In the below examply, Login1
will work, but Login2 will fail with:
Server: Msg 18456, Level 14, State 1, Line 1
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
sp_addlinkedsrvlogin @.rmtsrvname = 'server2'
, @.useself = 'false'
, @.locallogin = 'domain\Login1'
, @.rmtuser = 'RmtLogin1'
, @.rmtpassword = 'password'
sp_addlinkedsrvlogin @.rmtsrvname = 'server2'
, @.useself = 'false'
, @.locallogin = 'domain\Login2'
, @.rmtuser = 'RmtLogin1'
, @.rmtpassword = 'password'
Again, please keep in mind that the Login on the Linked Server is in the SA
role, and that the top Login works. Another important tip, both of these
work successfully on another box, just not the one that counts.
All ideas are greatly appreciated as Im quite desperate.
--
SQL2K SP3
TIA, ChrisRI think its related to this issue but Im not sure.
http://support.microsoft.com/default.aspx?scid=kb;en-us;238477
I don't really need a fix for this anyomore as I've found a workaround and
only needed this temporarily. More info: I had opened Query Analyzer under
the failing account on my local box... RClick/ Run as. But if I log directly
onto the box I was trying to run the query from it works fine. Which is why
Im thinking its related to the above article.
"ChrisR" <bla@.noemail.com> wrote in message
news:#uUSqB4EFHA.2608@.TK2MSFTNGP10.phx.gbl...
> Im having a problem with one particular Linked Server Login. I've created
> two of them. Neither of which has an existing Login on the Linked Server
and
> both of which are mapped to a member of SA. In the below examply, Login1
> will work, but Login2 will fail with:
> Server: Msg 18456, Level 14, State 1, Line 1
> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
> sp_addlinkedsrvlogin @.rmtsrvname = 'server2'
> , @.useself = 'false'
> , @.locallogin = 'domain\Login1'
> , @.rmtuser = 'RmtLogin1'
> , @.rmtpassword = 'password'
> sp_addlinkedsrvlogin @.rmtsrvname = 'server2'
> , @.useself = 'false'
> , @.locallogin = 'domain\Login2'
> , @.rmtuser = 'RmtLogin1'
> , @.rmtpassword = 'password'
> Again, please keep in mind that the Login on the Linked Server is in the
SA
> role, and that the top Login works. Another important tip, both of these
> work successfully on another box, just not the one that counts.
> All ideas are greatly appreciated as Im quite desperate.
> --
> SQL2K SP3
> TIA, ChrisR
>

linked server login problem... with a particular login... on a particular box

Im having a problem with one particular Linked Server Login. I've created
two of them. Neither of which has an existing Login on the Linked Server and
both of which are mapped to a member of SA. In the below examply, Login1
will work, but Login2 will fail with:
Server: Msg 18456, Level 14, State 1, Line 1
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
sp_addlinkedsrvlogin @.rmtsrvname = 'server2'
, @.useself = 'false'
, @.locallogin = 'domain\Login1'
, @.rmtuser = 'RmtLogin1'
, @.rmtpassword = 'password'
sp_addlinkedsrvlogin @.rmtsrvname = 'server2'
, @.useself = 'false'
, @.locallogin = 'domain\Login2'
, @.rmtuser = 'RmtLogin1'
, @.rmtpassword = 'password'
Again, please keep in mind that the Login on the Linked Server is in the SA
role, and that the top Login works. Another important tip, both of these
work successfully on another box, just not the one that counts.
All ideas are greatly appreciated as Im quite desperate.
SQL2K SP3
TIA, ChrisRI think its related to this issue but Im not sure.
http://support.microsoft.com/defaul...kb;en-us;238477
I don't really need a fix for this anyomore as I've found a workaround and
only needed this temporarily. More info: I had opened Query Analyzer under
the failing account on my local box... RClick/ Run as. But if I log directly
onto the box I was trying to run the query from it works fine. Which is why
Im thinking its related to the above article.
"ChrisR" <bla@.noemail.com> wrote in message
news:#uUSqB4EFHA.2608@.TK2MSFTNGP10.phx.gbl...
> Im having a problem with one particular Linked Server Login. I've created
> two of them. Neither of which has an existing Login on the Linked Server
and
> both of which are mapped to a member of SA. In the below examply, Login1
> will work, but Login2 will fail with:
> Server: Msg 18456, Level 14, State 1, Line 1
> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
> sp_addlinkedsrvlogin @.rmtsrvname = 'server2'
> , @.useself = 'false'
> , @.locallogin = 'domain\Login1'
> , @.rmtuser = 'RmtLogin1'
> , @.rmtpassword = 'password'
> sp_addlinkedsrvlogin @.rmtsrvname = 'server2'
> , @.useself = 'false'
> , @.locallogin = 'domain\Login2'
> , @.rmtuser = 'RmtLogin1'
> , @.rmtpassword = 'password'
> Again, please keep in mind that the Login on the Linked Server is in the
SA
> role, and that the top Login works. Another important tip, both of these
> work successfully on another box, just not the one that counts.
> All ideas are greatly appreciated as Im quite desperate.
> --
> SQL2K SP3
> TIA, ChrisR
>

linked server login problem... with a particular login... on a particular box

Im having a problem with one particular Linked Server Login. I've created
two of them. Neither of which has an existing Login on the Linked Server and
both of which are mapped to a member of SA. In the below examply, Login1
will work, but Login2 will fail with:
Server: Msg 18456, Level 14, State 1, Line 1
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
sp_addlinkedsrvlogin @.rmtsrvname = 'server2'
, @.useself = 'false'
, @.locallogin = 'domain\Login1'
, @.rmtuser = 'RmtLogin1'
, @.rmtpassword = 'password'
sp_addlinkedsrvlogin @.rmtsrvname = 'server2'
, @.useself = 'false'
, @.locallogin = 'domain\Login2'
, @.rmtuser = 'RmtLogin1'
, @.rmtpassword = 'password'
Again, please keep in mind that the Login on the Linked Server is in the SA
role, and that the top Login works. Another important tip, both of these
work successfully on another box, just not the one that counts.
All ideas are greatly appreciated as Im quite desperate.
SQL2K SP3
TIA, ChrisR
I think its related to this issue but Im not sure.
http://support.microsoft.com/default...b;en-us;238477
I don't really need a fix for this anyomore as I've found a workaround and
only needed this temporarily. More info: I had opened Query Analyzer under
the failing account on my local box... RClick/ Run as. But if I log directly
onto the box I was trying to run the query from it works fine. Which is why
Im thinking its related to the above article.
"ChrisR" <bla@.noemail.com> wrote in message
news:#uUSqB4EFHA.2608@.TK2MSFTNGP10.phx.gbl...
> Im having a problem with one particular Linked Server Login. I've created
> two of them. Neither of which has an existing Login on the Linked Server
and
> both of which are mapped to a member of SA. In the below examply, Login1
> will work, but Login2 will fail with:
> Server: Msg 18456, Level 14, State 1, Line 1
> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
> sp_addlinkedsrvlogin @.rmtsrvname = 'server2'
> , @.useself = 'false'
> , @.locallogin = 'domain\Login1'
> , @.rmtuser = 'RmtLogin1'
> , @.rmtpassword = 'password'
> sp_addlinkedsrvlogin @.rmtsrvname = 'server2'
> , @.useself = 'false'
> , @.locallogin = 'domain\Login2'
> , @.rmtuser = 'RmtLogin1'
> , @.rmtpassword = 'password'
> Again, please keep in mind that the Login on the Linked Server is in the
SA
> role, and that the top Login works. Another important tip, both of these
> work successfully on another box, just not the one that counts.
> All ideas are greatly appreciated as Im quite desperate.
> --
> SQL2K SP3
> TIA, ChrisR
>

Linked server for ODBC data source

Hope someone can help with this:
I have an Alpha box running open VMS which has an ODBC client from easysoft
set up as a system dsn in ODBC data sources. I can select the data source
from Excel/Access/VB asp etc with a connection string of "dsn=dsnname"
How can I set this up as a linked server in SQL 2k ?
I have tried using enterprise manager & creating a linked server for
"Microsoft OLE DB Provider for ODBC Drivers" with the data source as
"dsnname" and the provider string as "dsn=dsnname". Is the the correct way
to use a system dsn as a linked server? If so, are there any other
parameters to set up as I can't see any tables, and get an error : 7399,
OLEDB provider 'MSDASQL' reported an error, provider did not give any
information...IDBinitialize returned 0x80004005
Is this a login or security problem? I just want the login to use my current
credentials.
Did you install the ODBC client on the SQL Server box?
You can use a DSN but you need to create the DSN on the
server. You don't need to use a DSN though - you can also
provide the information used by the DSN in the provider
string and data source parameters of sp_addlinkedserver.
In terms of the 7399 error, that's somewhat of a generic
error. Try turning on trace flag 7300 or use SQL Profiler
to capture the OLEDB Errors event. This should give you to
get more information about the error.
-Sue
On Mon, 7 Jun 2004 12:12:03 +0100, "CCA Dave"
<david@.notreally.co.uk> wrote:

>Hope someone can help with this:
>I have an Alpha box running open VMS which has an ODBC client from easysoft
>set up as a system dsn in ODBC data sources. I can select the data source
>from Excel/Access/VB asp etc with a connection string of "dsn=dsnname"
>How can I set this up as a linked server in SQL 2k ?
>I have tried using enterprise manager & creating a linked server for
>"Microsoft OLE DB Provider for ODBC Drivers" with the data source as
>"dsnname" and the provider string as "dsn=dsnname". Is the the correct way
>to use a system dsn as a linked server? If so, are there any other
>parameters to set up as I can't see any tables, and get an error : 7399,
>OLEDB provider 'MSDASQL' reported an error, provider did not give any
>information...IDBinitialize returned 0x80004005
>Is this a login or security problem? I just want the login to use my current
>credentials.
>

Linked server for ODBC data source

Hope someone can help with this:
I have an Alpha box running open VMS which has an ODBC client from easysoft
set up as a system dsn in ODBC data sources. I can select the data source
from Excel/Access/VB asp etc with a connection string of "dsn=dsnname"
How can I set this up as a linked server in SQL 2k ?
I have tried using enterprise manager & creating a linked server for
"Microsoft OLE DB Provider for ODBC Drivers" with the data source as
"dsnname" and the provider string as "dsn=dsnname". Is the the correct way
to use a system dsn as a linked server? If so, are there any other
parameters to set up as I can't see any tables, and get an error : 7399,
OLEDB provider 'MSDASQL' reported an error, provider did not give any
information...IDBinitialize returned 0x80004005
Is this a login or security problem? I just want the login to use my current
credentials.Did you install the ODBC client on the SQL Server box?
You can use a DSN but you need to create the DSN on the
server. You don't need to use a DSN though - you can also
provide the information used by the DSN in the provider
string and data source parameters of sp_addlinkedserver.
In terms of the 7399 error, that's somewhat of a generic
error. Try turning on trace flag 7300 or use SQL Profiler
to capture the OLEDB Errors event. This should give you to
get more information about the error.
-Sue
On Mon, 7 Jun 2004 12:12:03 +0100, "CCA Dave"
<david@.notreally.co.uk> wrote:

>Hope someone can help with this:
>I have an Alpha box running open VMS which has an ODBC client from easysoft
>set up as a system dsn in ODBC data sources. I can select the data source
>from Excel/Access/VB asp etc with a connection string of "dsn=dsnname"
>How can I set this up as a linked server in SQL 2k ?
>I have tried using enterprise manager & creating a linked server for
>"Microsoft OLE DB Provider for ODBC Drivers" with the data source as
>"dsnname" and the provider string as "dsn=dsnname". Is the the correct way
>to use a system dsn as a linked server? If so, are there any other
>parameters to set up as I can't see any tables, and get an error : 7399,
>OLEDB provider 'MSDASQL' reported an error, provider did not give any
>information...IDBinitialize returned 0x80004005
>Is this a login or security problem? I just want the login to use my curren
t
>credentials.
>sql

Linked Server error 7399

I have setup a linked server to a Sybase database using the ODBC driver (which in turn uses the Sybase OLE DB provider). Logged onto the box as the SQL Service account everything is good. Using Enterprise Manager from any machine to the SQL Server box using an account that is a local administrator on the SQL Server box everything is good. However, if I attempt to make a connection via Enterprise Manager with an account that does not have local administrator rights on the server I get an error. I get the same error if I attempt an OPENQUERY against a table in the Linked server database. The error I receive is as follows:

Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'MSDASQL' reported an error.
[OLE/DB provider returned message: [SYBASE][ODBC Sybase driver]Allocation of a Sybase Open Client Context failed. Sybase normally generates a SYBINIT.ERR file contianing more specific reasons for failing.]
OLE DB error trace [OLE/DB Provider 'MSDASQL' IDBInitialize::Initialize returned 0x80004005: ].

The drives are secured so that only local administrators have rights to them.

I found in the Microsoft KB the follownig article:
http://support.microsoft.com/?kbid=814398

In this article it is suggesting that I need to open up the server from this lockdown. So, just to test this out without having to restart SQL Server I first allowed for full access to the C drive to "Everyone" and everything was good.

My question then is, has anybody else ran into this sort of thing? It doesn't seem right that I have to open up some folder on the database server to everyone in order to get a linked server going.

ThanksI figured it out. Here is what I found out:
Using the FileMon.exe tool from sysinternals.com I noticed that the file referred to in the error called "SYBINIT.ERR" could not be written since regular users did not have write access to the directory that it was trying to be written to. This was C:\WINNT\System32. So, I temporarily gave "Everyone" rights to modify the files within this directory. After doing so I ended up getting a "SYBINIT.ERR" file created which in turn told me that it "Cannot access file c:\sybase\ini\objectid.dat". I then gave Everyone read rights to the C:\sybase\ini folder. I then attempted again and got the following error: "Cannot access file c:\sybase\locales\locales.dat". Again, I gave read rights to this folder and tried again... this time getting the following errors: "Cannot access c:\sybase\charsets\iso_1\binary.srt file
Cannot access c:\sybase\charsets\iso_1\charset.loc file
Cannot access c:\sybase\charsets\iso_1\iso_1.cfg file"

Not wanting to keep this up, I then gave read rights to the C:\sybase folder and tried again. Everything worked. Then, I removed modify rights from "C:\WINNT\System32" and tried again. EVERYTHING WORKED!!! Yeah, this means that I just had to give read rights without opening up the SQL Server too much.|||Appreciate your interest in posting solution too, keep it up.

linked server , Oledb error....Urgent.

HI,
I am getting below error when creating linked server,infact in provider
options list box none of the provider is getting displayed.
in case if i select sql server then linked server is created but clicking on
tables below error message is displayed.
SQL Server Enterprise Manager
Error 7302: Could not create an instance of OLE DB provider 'SQLOLEDB'.
OLE DB error trace [Non-interface error: CoCreate of DSO for SQLOLEDB
returned 0x8007007f].
appreciating everyone help.
Sanjay
You'd probably want to check your MDAC installation on that server.
You can use the component checker to do this. You can download the
component checker as well as MDAC versions from:
http://msdn.microsoft.com/data/mdac/default.aspx
-Sue
On Tue, 26 Oct 2004 03:15:03 -0700, Sanjay
<Sanjay@.discussions.microsoft.com> wrote:

>HI,
> I am getting below error when creating linked server,infact in provider
>options list box none of the provider is getting displayed.
>in case if i select sql server then linked server is created but clicking on
>tables below error message is displayed.
>
>SQL Server Enterprise Manager
>--
>Error 7302: Could not create an instance of OLE DB provider 'SQLOLEDB'.
>OLE DB error trace [Non-interface error: CoCreate of DSO for SQLOLEDB
>returned 0x8007007f].

linked server , Oledb error....Urgent.

HI,
I am getting below error when creating linked server,infact in provider
options list box none of the provider is getting displayed.
in case if i select sql server then linked server is created but clicking on
tables below error message is displayed.
SQL Server Enterprise Manager
--
Error 7302: Could not create an instance of OLE DB provider 'SQLOLEDB'.
OLE DB error trace [Non-interface error: CoCreate of DSO for SQLOLEDB
returned 0x8007007f].
--
appreciating everyone help.
SanjayYou'd probably want to check your MDAC installation on that server.
You can use the component checker to do this. You can download the
component checker as well as MDAC versions from:
http://msdn.microsoft.com/data/mdac/default.aspx
-Sue
On Tue, 26 Oct 2004 03:15:03 -0700, Sanjay
<Sanjay@.discussions.microsoft.com> wrote:

>HI,
> I am getting below error when creating linked server,infact in provider
>options list box none of the provider is getting displayed.
>in case if i select sql server then linked server is created but clicking o
n
>tables below error message is displayed.
>
>SQL Server Enterprise Manager
>--
>Error 7302: Could not create an instance of OLE DB provider 'SQLOLEDB'.
>OLE DB error trace [Non-interface error: CoCreate of DSO for SQLOLEDB
>returned 0x8007007f].

linked server , Oledb error....Urgent.

HI,
I am getting below error when creating linked server,infact in provider
options list box none of the provider is getting displayed.
in case if i select sql server then linked server is created but clicking on
tables below error message is displayed.
SQL Server Enterprise Manager
--
Error 7302: Could not create an instance of OLE DB provider 'SQLOLEDB'.
OLE DB error trace [Non-interface error: CoCreate of DSO for SQLOLEDB
returned 0x8007007f].
--
appreciating everyone help.
SanjayYou'd probably want to check your MDAC installation on that server.
You can use the component checker to do this. You can download the
component checker as well as MDAC versions from:
http://msdn.microsoft.com/data/mdac/default.aspx
-Sue
On Tue, 26 Oct 2004 03:15:03 -0700, Sanjay
<Sanjay@.discussions.microsoft.com> wrote:
>HI,
> I am getting below error when creating linked server,infact in provider
>options list box none of the provider is getting displayed.
>in case if i select sql server then linked server is created but clicking on
>tables below error message is displayed.
>
>SQL Server Enterprise Manager
>--
>Error 7302: Could not create an instance of OLE DB provider 'SQLOLEDB'.
>OLE DB error trace [Non-interface error: CoCreate of DSO for SQLOLEDB
>returned 0x8007007f].

Linked server

I'm trying to connect to a DB2/400 v4r creating a linked server on the
Enterprise Manager of my MSSQL 2000 box, but i receive the following message
when i try to expand the TABLES node on the tree:
Error 7302: Could not create an instance of OLE DB Provide 'IBMDA400'.
OLE DB error trace [non-interface error: CoCreate of DSO for IBMDA400
returned 0x80040154]
The version of CA400 installed on the MSSQL box is V4R5M0.
ThanksGenerally the error is caused by the provider not being
registered on the machine or from not having the in process
option set for the provider.
For the provider options, if you go to the linked server in
enterprise manager, view the properties and select Provider
Options. Then make sure the Allow InProcess option is
selected.
-Sue
On Mon, 15 Mar 2004 10:55:36 GMT, "Fabio Benedini"
<f.benedini@.magconsulting.it> wrote:

>I'm trying to connect to a DB2/400 v4r creating a linked server on the
>Enterprise Manager of my MSSQL 2000 box, but i receive the following messag
e
>when i try to expand the TABLES node on the tree:
>
>Error 7302: Could not create an instance of OLE DB Provide 'IBMDA400'.
>OLE DB error trace [non-interface error: CoCreate of DSO for IBMDA400
>returned 0x80040154]
>The version of CA400 installed on the MSSQL box is V4R5M0.
>Thanks
>|||Thank you Sue,
I've applied your tip and now I don't get that message, but now when I try
to expand the Tables node, my Enterprise Manager seems to hang. I tried to
wait for over 20 mins but i had to close it from the Task Manager.
Could you give me an example of a working configuration of a linked server
to DB2/400?
Thanks
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:l8eb50dfufaqvf68ugecj8aagokm5pop0h@.
4ax.com...
> Generally the error is caused by the provider not being
> registered on the machine or from not having the in process
> option set for the provider.
> For the provider options, if you go to the linked server in
> enterprise manager, view the properties and select Provider
> Options. Then make sure the Allow InProcess option is
> selected.
> -Sue
> On Mon, 15 Mar 2004 10:55:36 GMT, "Fabio Benedini"
> <f.benedini@.magconsulting.it> wrote:
>
message
>|||If you install Client Access on the server, it will install
and configure the drivers and providers for the AS400 on the
SQL Server box so that you can use linked servers. You
should also make sure you have the client updated with what
whatever service pack level based on updates to the AS400.
There is a link to update this in the Client Access program
group - I think that's where it is, can't remember off the
top of my head. For data source, use the IP address of the
AS400. For provider string, you need to include the library
you are using, connect timeout setting and code page. There
is some documentation for the settings in the Client Access
help files. You'd set the provider string somewhat like:
InitCat=YourLibrary;CCSID=37;PCCodePage=
1252;
Data Source=xxx.xxx.xxx.xxx
Settings will depend on how your AS400 is configured. Again,
the Client Access help files have information on the
necessary connection string settings.
-Sue
On Mon, 15 Mar 2004 15:22:36 GMT, "Fabio Benedini"
<f.benedini@.magconsulting.it> wrote:

>Thank you Sue,
>I've applied your tip and now I don't get that message, but now when I try
>to expand the Tables node, my Enterprise Manager seems to hang. I tried to
>wait for over 20 mins but i had to close it from the Task Manager.
>Could you give me an example of a working configuration of a linked server
>to DB2/400?
>Thanks
>
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> news:l8eb50dfufaqvf68ugecj8aagokm5pop0h@.
4ax.com...
>message
>