Hi,
When ever I start the Enterprise manger client from my laptop(Client), I see
the Failure Audit in the Security Eventlog. I registered all the servers
using sql authentication. I am running SQL Enterprisemanger on Windows Xp.
Here is one of the error:
Unprotection of auditable protected data.
Data Description: SQL Server Registration
Key Identifier: 1f3ba71a-6f52-4e58-8007-43ced74242b4
Protected Data Flags: 0x0
Protection Algorithms: 3DES-168 , SHA1-160
Failure Reason: 0x8009000B
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Can anybody having the fix for this, because my securtiy Auditing team
questioning these failures.
Thanks
rb
1. Do you have encryption enabled on the client or server?
2. When this happens is the laptop connected to the network?
3. Do you have any IPSec rules setup for the SQL Server?
"rb" <srbssr@.yahoo.com> wrote in message
news:efxp4cN9EHA.2600@.TK2MSFTNGP09.phx.gbl...
> Hi,
> When ever I start the Enterprise manger client from my laptop(Client), I
see
> the Failure Audit in the Security Eventlog. I registered all the servers
> using sql authentication. I am running SQL Enterprisemanger on Windows Xp.
> Here is one of the error:
> Unprotection of auditable protected data.
> Data Description: SQL Server Registration
> Key Identifier: 1f3ba71a-6f52-4e58-8007-43ced74242b4
> Protected Data Flags: 0x0
> Protection Algorithms: 3DES-168 , SHA1-160
> Failure Reason: 0x8009000B
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Can anybody having the fix for this, because my securtiy Auditing team
> questioning these failures.
> Thanks
> rb
>
Showing posts with label whenever. Show all posts
Showing posts with label whenever. Show all posts
Saturday, February 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)