Hello,
I have successfully created an Exchange 2000 linked server in Microsoft SQL server 2k. When I use my NT login, I can query it.
I'm now developping a website (ASP.NET in IIS 5). I have successfully created a web page querying my database. But now, I would like to query my linked server via my SQL server. I have try various authentification settings but I always got this error : OLE DB provider 'Exoledb.DataSource.1' reported an error. Authentication failed.
I know it is because the IIS process don't have any rights on the Exchange server but I would like to know what is the way to get around this without given rights to the IIS process (and creating huge security holes).
Thank a lot
Felix Pageau
fpageau@.str.cadid you try distributed queries ?
for example :
INSERT INTO [Database1name].[Owner].[Table]
SELECT *
FROM OPENQUERY ([LinkedServerName], SELECT Database2name.Table.* FROM Database2Name.Table)|||Hello,
this is exactly what I'm trying to do... I would like to know if it is possible to "impersonate" an Exchange Linked Server (with a user defined in the domain...) ?
Thank|||Review information from this KBA (http://support.microsoft.com/default.aspx?scid=kb;EN-US;285833) to go with Linked server authentication.|||Hello,
this is working fine with access but Exchange is using Active Directory login... Those example use plain text login & password. I have already try this way.
Thank a lot
Felix Pageau
Showing posts with label linked. Show all posts
Showing posts with label linked. Show all posts
Sunday, March 25, 2012
Friday, February 24, 2012
attempting to create a linked server to MySQL
We attempted to create a link server between an MSDE database and MySQL 4.1
database using ODBC. However, whenever we attempt to look at the tables
associated with the link we are greeted with the message: Could not create
an instance of OLE DB provider 'MSDASQL'. OLD DB error trace [Non-interface
error: Cocreate of DSO for MSDASQL returned 0x800700005].
When I searched the web for this message, I learned that it is not unusual
to encounter it, but have not been able to find a way to get past it. The
version of MDAC appears to be consistent with the Microsoft table relating
version and Windows version (2000).
Any direction or source of specific aids would be appreciated.
We have had some success, but different problem which may be essentially the
same.
On a different machine which has MSDE , loaded a MySQL 4.1 database. When
adding the ODBC/Connector used the FTP address of this machine in the block
for Server. tested the connection succesfully.
Then used query analyzer to EXEC sp_addlinkedserver with
New LinkedServer Name,
string MYSQL 4.1,
string MSDASQL,
the name of the ODBC/Connector from first step,
Null,
string Driver={MySQL ODBC 3.51 Driver}
After execution of this I started up Enterprise Mgr and could click of the
Linked Server name, and then the tables Icon and a list of all the tables in
the MySql database was visible.
I went back to the query analyzer and executed a select statement and saw
data from field1 in tbl1 of the Mysql databas3e when I executed the
statemnet:
Select * from OPENQUERY( new linked servername, 'Select field1 from tbl1')
End of success.
i started up an Access ADP program and attempted to add external data using
the Linked Table wizard. After selecting tbl1 it created an odc file, which
when I attempted to open it was greeted with the error message: This
DataSource contains no visible tables. ...AAAH ...the next problem
Thanks to those who sent on comments. Comments and
"Sean Moore" <smoore@.123progeny.net> wrote in message
news:OOMAQUq7FHA.2152@.TK2MSFTNGP10.phx.gbl...
> We attempted to create a link server between an MSDE database and MySQL
4.1
> database using ODBC. However, whenever we attempt to look at the tables
> associated with the link we are greeted with the message: Could not
create
> an instance of OLE DB provider 'MSDASQL'. OLD DB error trace
[Non-interface
> error: Cocreate of DSO for MSDASQL returned 0x800700005].
> When I searched the web for this message, I learned that it is not unusual
> to encounter it, but have not been able to find a way to get past it. The
> version of MDAC appears to be consistent with the Microsoft table relating
> version and Windows version (2000).
> Any direction or source of specific aids would be appreciated.
>
|||Not an expert on this but I believe that linking servers requires OLEDB.
Can't be done with an ODBC driver. You should be able to fine an OLEDB
driver out there to make this work.
Andrew Robinson
www.binaryocean.com
www.bellinghamdotnet.org
"Sean Moore" <smoore@.123progeny.net> wrote in message
news:OOMAQUq7FHA.2152@.TK2MSFTNGP10.phx.gbl...
> We attempted to create a link server between an MSDE database and MySQL
> 4.1
> database using ODBC. However, whenever we attempt to look at the tables
> associated with the link we are greeted with the message: Could not
> create
> an instance of OLE DB provider 'MSDASQL'. OLD DB error trace
> [Non-interface
> error: Cocreate of DSO for MSDASQL returned 0x800700005].
> When I searched the web for this message, I learned that it is not unusual
> to encounter it, but have not been able to find a way to get past it. The
> version of MDAC appears to be consistent with the Microsoft table relating
> version and Windows version (2000).
> Any direction or source of specific aids would be appreciated.
>
database using ODBC. However, whenever we attempt to look at the tables
associated with the link we are greeted with the message: Could not create
an instance of OLE DB provider 'MSDASQL'. OLD DB error trace [Non-interface
error: Cocreate of DSO for MSDASQL returned 0x800700005].
When I searched the web for this message, I learned that it is not unusual
to encounter it, but have not been able to find a way to get past it. The
version of MDAC appears to be consistent with the Microsoft table relating
version and Windows version (2000).
Any direction or source of specific aids would be appreciated.
We have had some success, but different problem which may be essentially the
same.
On a different machine which has MSDE , loaded a MySQL 4.1 database. When
adding the ODBC/Connector used the FTP address of this machine in the block
for Server. tested the connection succesfully.
Then used query analyzer to EXEC sp_addlinkedserver with
New LinkedServer Name,
string MYSQL 4.1,
string MSDASQL,
the name of the ODBC/Connector from first step,
Null,
string Driver={MySQL ODBC 3.51 Driver}
After execution of this I started up Enterprise Mgr and could click of the
Linked Server name, and then the tables Icon and a list of all the tables in
the MySql database was visible.
I went back to the query analyzer and executed a select statement and saw
data from field1 in tbl1 of the Mysql databas3e when I executed the
statemnet:
Select * from OPENQUERY( new linked servername, 'Select field1 from tbl1')
End of success.
i started up an Access ADP program and attempted to add external data using
the Linked Table wizard. After selecting tbl1 it created an odc file, which
when I attempted to open it was greeted with the error message: This
DataSource contains no visible tables. ...AAAH ...the next problem
Thanks to those who sent on comments. Comments and
"Sean Moore" <smoore@.123progeny.net> wrote in message
news:OOMAQUq7FHA.2152@.TK2MSFTNGP10.phx.gbl...
> We attempted to create a link server between an MSDE database and MySQL
4.1
> database using ODBC. However, whenever we attempt to look at the tables
> associated with the link we are greeted with the message: Could not
create
> an instance of OLE DB provider 'MSDASQL'. OLD DB error trace
[Non-interface
> error: Cocreate of DSO for MSDASQL returned 0x800700005].
> When I searched the web for this message, I learned that it is not unusual
> to encounter it, but have not been able to find a way to get past it. The
> version of MDAC appears to be consistent with the Microsoft table relating
> version and Windows version (2000).
> Any direction or source of specific aids would be appreciated.
>
|||Not an expert on this but I believe that linking servers requires OLEDB.
Can't be done with an ODBC driver. You should be able to fine an OLEDB
driver out there to make this work.
Andrew Robinson
www.binaryocean.com
www.bellinghamdotnet.org
"Sean Moore" <smoore@.123progeny.net> wrote in message
news:OOMAQUq7FHA.2152@.TK2MSFTNGP10.phx.gbl...
> We attempted to create a link server between an MSDE database and MySQL
> 4.1
> database using ODBC. However, whenever we attempt to look at the tables
> associated with the link we are greeted with the message: Could not
> create
> an instance of OLE DB provider 'MSDASQL'. OLD DB error trace
> [Non-interface
> error: Cocreate of DSO for MSDASQL returned 0x800700005].
> When I searched the web for this message, I learned that it is not unusual
> to encounter it, but have not been able to find a way to get past it. The
> version of MDAC appears to be consistent with the Microsoft table relating
> version and Windows version (2000).
> Any direction or source of specific aids would be appreciated.
>
attempting to create a linked server to MySQL
We attempted to create a link server between an MSDE database and MySQL 4.1
database using ODBC. However, whenever we attempt to look at the tables
associated with the link we are greeted with the message: Could not create
an instance of OLE DB provider 'MSDASQL'. OLD DB error trace [Non-interface
error: Cocreate of DSO for MSDASQL returned 0x800700005].
When I searched the web for this message, I learned that it is not unusual
to encounter it, but have not been able to find a way to get past it. The
version of MDAC appears to be consistent with the Microsoft table relating
version and Windows version (2000).
Any direction or source of specific aids would be appreciated.
We have had some success, but different problem which may be essentially the
same.
On a different machine which has MSDE , loaded a MySQL 4.1 database. When
adding the ODBC/Connector used the FTP address of this machine in the block
for Server. tested the connection succesfully.
Then used query analyzer to EXEC sp_addlinkedserver with
New LinkedServer Name,
string MYSQL 4.1,
string MSDASQL,
the name of the ODBC/Connector from first step,
Null,
string Driver={MySQL ODBC 3.51 Driver}
After execution of this I started up Enterprise Mgr and could click of the
Linked Server name, and then the tables Icon and a list of all the tables in
the MySql database was visible.
I went back to the query analyzer and executed a select statement and saw
data from field1 in tbl1 of the Mysql databas3e when I executed the
statemnet:
Select * from OPENQUERY( new linked servername, 'Select field1 from tbl1')
End of success.
i started up an Access ADP program and attempted to add external data using
the Linked Table wizard. After selecting tbl1 it created an odc file, which
when I attempted to open it was greeted with the error message: This
DataSource contains no visible tables. ...AAAH ...the next problem
Thanks to those who sent on comments. Comments and
"Sean Moore" <smoore@.123progeny.net> wrote in message
news:OOMAQUq7FHA.2152@.TK2MSFTNGP10.phx.gbl...
> We attempted to create a link server between an MSDE database and MySQL
4.1
> database using ODBC. However, whenever we attempt to look at the tables
> associated with the link we are greeted with the message: Could not
create
> an instance of OLE DB provider 'MSDASQL'. OLD DB error trace
[Non-interface
> error: Cocreate of DSO for MSDASQL returned 0x800700005].
> When I searched the web for this message, I learned that it is not unusual
> to encounter it, but have not been able to find a way to get past it. The
> version of MDAC appears to be consistent with the Microsoft table relating
> version and Windows version (2000).
> Any direction or source of specific aids would be appreciated.
>
|||Not an expert on this but I believe that linking servers requires OLEDB.
Can't be done with an ODBC driver. You should be able to fine an OLEDB
driver out there to make this work.
Andrew Robinson
www.binaryocean.com
www.bellinghamdotnet.org
"Sean Moore" <smoore@.123progeny.net> wrote in message
news:OOMAQUq7FHA.2152@.TK2MSFTNGP10.phx.gbl...
> We attempted to create a link server between an MSDE database and MySQL
> 4.1
> database using ODBC. However, whenever we attempt to look at the tables
> associated with the link we are greeted with the message: Could not
> create
> an instance of OLE DB provider 'MSDASQL'. OLD DB error trace
> [Non-interface
> error: Cocreate of DSO for MSDASQL returned 0x800700005].
> When I searched the web for this message, I learned that it is not unusual
> to encounter it, but have not been able to find a way to get past it. The
> version of MDAC appears to be consistent with the Microsoft table relating
> version and Windows version (2000).
> Any direction or source of specific aids would be appreciated.
>
database using ODBC. However, whenever we attempt to look at the tables
associated with the link we are greeted with the message: Could not create
an instance of OLE DB provider 'MSDASQL'. OLD DB error trace [Non-interface
error: Cocreate of DSO for MSDASQL returned 0x800700005].
When I searched the web for this message, I learned that it is not unusual
to encounter it, but have not been able to find a way to get past it. The
version of MDAC appears to be consistent with the Microsoft table relating
version and Windows version (2000).
Any direction or source of specific aids would be appreciated.
We have had some success, but different problem which may be essentially the
same.
On a different machine which has MSDE , loaded a MySQL 4.1 database. When
adding the ODBC/Connector used the FTP address of this machine in the block
for Server. tested the connection succesfully.
Then used query analyzer to EXEC sp_addlinkedserver with
New LinkedServer Name,
string MYSQL 4.1,
string MSDASQL,
the name of the ODBC/Connector from first step,
Null,
string Driver={MySQL ODBC 3.51 Driver}
After execution of this I started up Enterprise Mgr and could click of the
Linked Server name, and then the tables Icon and a list of all the tables in
the MySql database was visible.
I went back to the query analyzer and executed a select statement and saw
data from field1 in tbl1 of the Mysql databas3e when I executed the
statemnet:
Select * from OPENQUERY( new linked servername, 'Select field1 from tbl1')
End of success.
i started up an Access ADP program and attempted to add external data using
the Linked Table wizard. After selecting tbl1 it created an odc file, which
when I attempted to open it was greeted with the error message: This
DataSource contains no visible tables. ...AAAH ...the next problem
Thanks to those who sent on comments. Comments and
"Sean Moore" <smoore@.123progeny.net> wrote in message
news:OOMAQUq7FHA.2152@.TK2MSFTNGP10.phx.gbl...
> We attempted to create a link server between an MSDE database and MySQL
4.1
> database using ODBC. However, whenever we attempt to look at the tables
> associated with the link we are greeted with the message: Could not
create
> an instance of OLE DB provider 'MSDASQL'. OLD DB error trace
[Non-interface
> error: Cocreate of DSO for MSDASQL returned 0x800700005].
> When I searched the web for this message, I learned that it is not unusual
> to encounter it, but have not been able to find a way to get past it. The
> version of MDAC appears to be consistent with the Microsoft table relating
> version and Windows version (2000).
> Any direction or source of specific aids would be appreciated.
>
|||Not an expert on this but I believe that linking servers requires OLEDB.
Can't be done with an ODBC driver. You should be able to fine an OLEDB
driver out there to make this work.
Andrew Robinson
www.binaryocean.com
www.bellinghamdotnet.org
"Sean Moore" <smoore@.123progeny.net> wrote in message
news:OOMAQUq7FHA.2152@.TK2MSFTNGP10.phx.gbl...
> We attempted to create a link server between an MSDE database and MySQL
> 4.1
> database using ODBC. However, whenever we attempt to look at the tables
> associated with the link we are greeted with the message: Could not
> create
> an instance of OLE DB provider 'MSDASQL'. OLD DB error trace
> [Non-interface
> error: Cocreate of DSO for MSDASQL returned 0x800700005].
> When I searched the web for this message, I learned that it is not unusual
> to encounter it, but have not been able to find a way to get past it. The
> version of MDAC appears to be consistent with the Microsoft table relating
> version and Windows version (2000).
> Any direction or source of specific aids would be appreciated.
>
attempting to create a linked server to MySQL
We attempted to create a link server between an MSDE database and MySQL 4.1
database using ODBC. However, whenever we attempt to look at the tables
associated with the link we are greeted with the message: Could not create
an instance of OLE DB provider 'MSDASQL'. OLD DB error trace [Non-interface
error: Cocreate of DSO for MSDASQL returned 0x800700005].
When I searched the web for this message, I learned that it is not unusual
to encounter it, but have not been able to find a way to get past it. The
version of MDAC appears to be consistent with the Microsoft table relating
version and Windows version (2000).
Any direction or source of specific aids would be appreciated.
We have had some success, but different problem which may be essentially the
same.
On a different machine which has MSDE , loaded a MySQL 4.1 database. When
adding the ODBC/Connector used the FTP address of this machine in the block
for Server. tested the connection succesfully.
Then used query analyzer to EXEC sp_addlinkedserver with
New LinkedServer Name,
string MYSQL 4.1,
string MSDASQL,
the name of the ODBC/Connector from first step,
Null,
string Driver={MySQL ODBC 3.51 Driver}
After execution of this I started up Enterprise Mgr and could click of the
Linked Server name, and then the tables Icon and a list of all the tables in
the MySql database was visible.
I went back to the query analyzer and executed a select statement and saw
data from field1 in tbl1 of the Mysql databas3e when I executed the
statemnet:
Select * from OPENQUERY( new linked servername, 'Select field1 from tbl1')
End of success.
i started up an Access ADP program and attempted to add external data using
the Linked Table wizard. After selecting tbl1 it created an odc file, which
when I attempted to open it was greeted with the error message: This
DataSource contains no visible tables. ...AAAH ...the next problem
Thanks to those who sent on comments. Comments and
"Sean Moore" <smoore@.123progeny.net> wrote in message
news:OOMAQUq7FHA.2152@.TK2MSFTNGP10.phx.gbl...
> We attempted to create a link server between an MSDE database and MySQL
4.1
> database using ODBC. However, whenever we attempt to look at the tables
> associated with the link we are greeted with the message: Could not
create
> an instance of OLE DB provider 'MSDASQL'. OLD DB error trace
[Non-interface
> error: Cocreate of DSO for MSDASQL returned 0x800700005].
> When I searched the web for this message, I learned that it is not unusual
> to encounter it, but have not been able to find a way to get past it. The
> version of MDAC appears to be consistent with the Microsoft table relating
> version and Windows version (2000).
> Any direction or source of specific aids would be appreciated.
>
|||Not an expert on this but I believe that linking servers requires OLEDB.
Can't be done with an ODBC driver. You should be able to fine an OLEDB
driver out there to make this work.
Andrew Robinson
www.binaryocean.com
www.bellinghamdotnet.org
"Sean Moore" <smoore@.123progeny.net> wrote in message
news:OOMAQUq7FHA.2152@.TK2MSFTNGP10.phx.gbl...
> We attempted to create a link server between an MSDE database and MySQL
> 4.1
> database using ODBC. However, whenever we attempt to look at the tables
> associated with the link we are greeted with the message: Could not
> create
> an instance of OLE DB provider 'MSDASQL'. OLD DB error trace
> [Non-interface
> error: Cocreate of DSO for MSDASQL returned 0x800700005].
> When I searched the web for this message, I learned that it is not unusual
> to encounter it, but have not been able to find a way to get past it. The
> version of MDAC appears to be consistent with the Microsoft table relating
> version and Windows version (2000).
> Any direction or source of specific aids would be appreciated.
>
database using ODBC. However, whenever we attempt to look at the tables
associated with the link we are greeted with the message: Could not create
an instance of OLE DB provider 'MSDASQL'. OLD DB error trace [Non-interface
error: Cocreate of DSO for MSDASQL returned 0x800700005].
When I searched the web for this message, I learned that it is not unusual
to encounter it, but have not been able to find a way to get past it. The
version of MDAC appears to be consistent with the Microsoft table relating
version and Windows version (2000).
Any direction or source of specific aids would be appreciated.
We have had some success, but different problem which may be essentially the
same.
On a different machine which has MSDE , loaded a MySQL 4.1 database. When
adding the ODBC/Connector used the FTP address of this machine in the block
for Server. tested the connection succesfully.
Then used query analyzer to EXEC sp_addlinkedserver with
New LinkedServer Name,
string MYSQL 4.1,
string MSDASQL,
the name of the ODBC/Connector from first step,
Null,
string Driver={MySQL ODBC 3.51 Driver}
After execution of this I started up Enterprise Mgr and could click of the
Linked Server name, and then the tables Icon and a list of all the tables in
the MySql database was visible.
I went back to the query analyzer and executed a select statement and saw
data from field1 in tbl1 of the Mysql databas3e when I executed the
statemnet:
Select * from OPENQUERY( new linked servername, 'Select field1 from tbl1')
End of success.
i started up an Access ADP program and attempted to add external data using
the Linked Table wizard. After selecting tbl1 it created an odc file, which
when I attempted to open it was greeted with the error message: This
DataSource contains no visible tables. ...AAAH ...the next problem
Thanks to those who sent on comments. Comments and
"Sean Moore" <smoore@.123progeny.net> wrote in message
news:OOMAQUq7FHA.2152@.TK2MSFTNGP10.phx.gbl...
> We attempted to create a link server between an MSDE database and MySQL
4.1
> database using ODBC. However, whenever we attempt to look at the tables
> associated with the link we are greeted with the message: Could not
create
> an instance of OLE DB provider 'MSDASQL'. OLD DB error trace
[Non-interface
> error: Cocreate of DSO for MSDASQL returned 0x800700005].
> When I searched the web for this message, I learned that it is not unusual
> to encounter it, but have not been able to find a way to get past it. The
> version of MDAC appears to be consistent with the Microsoft table relating
> version and Windows version (2000).
> Any direction or source of specific aids would be appreciated.
>
|||Not an expert on this but I believe that linking servers requires OLEDB.
Can't be done with an ODBC driver. You should be able to fine an OLEDB
driver out there to make this work.
Andrew Robinson
www.binaryocean.com
www.bellinghamdotnet.org
"Sean Moore" <smoore@.123progeny.net> wrote in message
news:OOMAQUq7FHA.2152@.TK2MSFTNGP10.phx.gbl...
> We attempted to create a link server between an MSDE database and MySQL
> 4.1
> database using ODBC. However, whenever we attempt to look at the tables
> associated with the link we are greeted with the message: Could not
> create
> an instance of OLE DB provider 'MSDASQL'. OLD DB error trace
> [Non-interface
> error: Cocreate of DSO for MSDASQL returned 0x800700005].
> When I searched the web for this message, I learned that it is not unusual
> to encounter it, but have not been able to find a way to get past it. The
> version of MDAC appears to be consistent with the Microsoft table relating
> version and Windows version (2000).
> Any direction or source of specific aids would be appreciated.
>
attempting to create a linked server to MySQL
We attempted to create a link server between an MSDE database and mysql 4.1
database using ODBC. However, whenever we attempt to look at the tables
associated with the link we are greeted with the message: Could not create
an instance of OLE DB provider 'MSDASQL'. OLD DB error trace [Non-interf
ace
error: Cocreate of DSO for MSDASQL returned 0x800700005].
When I searched the web for this message, I learned that it is not unusual
to encounter it, but have not been able to find a way to get past it. The
version of MDAC appears to be consistent with the Microsoft table relating
version and Windows version (2000).
Any direction or source of specific aids would be appreciated.We have had some success, but different problem which may be essentially the
same.
On a different machine which has MSDE , loaded a mysql 4.1 database. When
adding the ODBC/Connector used the FTP address of this machine in the block
for Server. tested the connection succesfully.
Then used query analyzer to EXEC sp_addlinkedserver with
New LinkedServer Name,
string mysql 4.1,
string MSDASQL,
the name of the ODBC/Connector from first step,
Null,
string Driver={MySQL ODBC 3.51 Driver}
After execution of this I started up Enterprise Mgr and could click of the
Linked Server name, and then the tables Icon and a list of all the tables in
the mysql database was visible.
I went back to the query analyzer and executed a select statement and saw
data from field1 in tbl1 of the mysql databas3e when I executed the
statemnet:
Select * from OPENQUERY( new linked servername, 'Select field1 from tbl1')
End of success.
i started up an Access ADP program and attempted to add external data using
the Linked Table wizard. After selecting tbl1 it created an odc file, which
when I attempted to open it was greeted with the error message: This
DataSource contains no visible tables. ...AAAH ...the next problem
Thanks to those who sent on comments. Comments and
"Sean Moore" <smoore@.123progeny.net> wrote in message
news:OOMAQUq7FHA.2152@.TK2MSFTNGP10.phx.gbl...
> We attempted to create a link server between an MSDE database and MySQL
4.1
> database using ODBC. However, whenever we attempt to look at the tables
> associated with the link we are greeted with the message: Could not
create
> an instance of OLE DB provider 'MSDASQL'. OLD DB error trace
[Non-interface
> error: Cocreate of DSO for MSDASQL returned 0x800700005].
> When I searched the web for this message, I learned that it is not unusual
> to encounter it, but have not been able to find a way to get past it. The
> version of MDAC appears to be consistent with the Microsoft table relating
> version and Windows version (2000).
> Any direction or source of specific aids would be appreciated.
>|||Not an expert on this but I believe that linking servers requires OLEDB.
Can't be done with an ODBC driver. You should be able to fine an OLEDB
driver out there to make this work.
Andrew Robinson
www.binaryocean.com
www.bellinghamdotnet.org
"Sean Moore" <smoore@.123progeny.net> wrote in message
news:OOMAQUq7FHA.2152@.TK2MSFTNGP10.phx.gbl...
> We attempted to create a link server between an MSDE database and MySQL
> 4.1
> database using ODBC. However, whenever we attempt to look at the tables
> associated with the link we are greeted with the message: Could not
> create
> an instance of OLE DB provider 'MSDASQL'. OLD DB error trace
> [Non-interface
> error: Cocreate of DSO for MSDASQL returned 0x800700005].
> When I searched the web for this message, I learned that it is not unusual
> to encounter it, but have not been able to find a way to get past it. The
> version of MDAC appears to be consistent with the Microsoft table relating
> version and Windows version (2000).
> Any direction or source of specific aids would be appreciated.
>
database using ODBC. However, whenever we attempt to look at the tables
associated with the link we are greeted with the message: Could not create
an instance of OLE DB provider 'MSDASQL'. OLD DB error trace [Non-interf
ace
error: Cocreate of DSO for MSDASQL returned 0x800700005].
When I searched the web for this message, I learned that it is not unusual
to encounter it, but have not been able to find a way to get past it. The
version of MDAC appears to be consistent with the Microsoft table relating
version and Windows version (2000).
Any direction or source of specific aids would be appreciated.We have had some success, but different problem which may be essentially the
same.
On a different machine which has MSDE , loaded a mysql 4.1 database. When
adding the ODBC/Connector used the FTP address of this machine in the block
for Server. tested the connection succesfully.
Then used query analyzer to EXEC sp_addlinkedserver with
New LinkedServer Name,
string mysql 4.1,
string MSDASQL,
the name of the ODBC/Connector from first step,
Null,
string Driver={MySQL ODBC 3.51 Driver}
After execution of this I started up Enterprise Mgr and could click of the
Linked Server name, and then the tables Icon and a list of all the tables in
the mysql database was visible.
I went back to the query analyzer and executed a select statement and saw
data from field1 in tbl1 of the mysql databas3e when I executed the
statemnet:
Select * from OPENQUERY( new linked servername, 'Select field1 from tbl1')
End of success.
i started up an Access ADP program and attempted to add external data using
the Linked Table wizard. After selecting tbl1 it created an odc file, which
when I attempted to open it was greeted with the error message: This
DataSource contains no visible tables. ...AAAH ...the next problem
Thanks to those who sent on comments. Comments and
"Sean Moore" <smoore@.123progeny.net> wrote in message
news:OOMAQUq7FHA.2152@.TK2MSFTNGP10.phx.gbl...
> We attempted to create a link server between an MSDE database and MySQL
4.1
> database using ODBC. However, whenever we attempt to look at the tables
> associated with the link we are greeted with the message: Could not
create
> an instance of OLE DB provider 'MSDASQL'. OLD DB error trace
[Non-interface
> error: Cocreate of DSO for MSDASQL returned 0x800700005].
> When I searched the web for this message, I learned that it is not unusual
> to encounter it, but have not been able to find a way to get past it. The
> version of MDAC appears to be consistent with the Microsoft table relating
> version and Windows version (2000).
> Any direction or source of specific aids would be appreciated.
>|||Not an expert on this but I believe that linking servers requires OLEDB.
Can't be done with an ODBC driver. You should be able to fine an OLEDB
driver out there to make this work.
Andrew Robinson
www.binaryocean.com
www.bellinghamdotnet.org
"Sean Moore" <smoore@.123progeny.net> wrote in message
news:OOMAQUq7FHA.2152@.TK2MSFTNGP10.phx.gbl...
> We attempted to create a link server between an MSDE database and MySQL
> 4.1
> database using ODBC. However, whenever we attempt to look at the tables
> associated with the link we are greeted with the message: Could not
> create
> an instance of OLE DB provider 'MSDASQL'. OLD DB error trace
> [Non-interface
> error: Cocreate of DSO for MSDASQL returned 0x800700005].
> When I searched the web for this message, I learned that it is not unusual
> to encounter it, but have not been able to find a way to get past it. The
> version of MDAC appears to be consistent with the Microsoft table relating
> version and Windows version (2000).
> Any direction or source of specific aids would be appreciated.
>
Subscribe to:
Posts (Atom)