By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,863 Members | 838 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,863 IT Pros & Developers. It's quick & easy.

Sql Server 2000 linked server to Access 97/2000 incompatability

P: n/a
We are experiencing a problem with Sql Server 2000 linking to an
Access 97 file. We have two machines that link to this .mdb file, and
we recently upgraded one to newer hardware, SP3a, MDAC 2.8, etc. The
link on this upgraded machine no longer works, giving this message:

Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
[OLE/DB provider returned message: Cannot open a database created with
a previous version of your application.]
OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
IDBInitialize::Initialize returned 0x80004005: ].

The link on the older machine still works. We decided to try
converting a copy of the file to Access 2000 to see if the newer
patches/drivers/whatever no longer supported 97. We set up a link on
both machines to this file, and they both work. However, on the
upgraded machine, the following error is receieved

Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
[OLE/DB provider returned message: System resource exceeded.]
OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
ICommandText::Execute returned 0x80004005: ].
when making 1-3 connections to the the linked server, while the older
machine supports at least 7 simultaneous queries connecting to the
linked server and still hasn't produced that error.

Does anyone have any idea if there is a known issue with linking to
Access 97/2000 files under MDAC 2.8, Jet 4.0, etc? Any light anyone
can shine on this subject would be greatly appreciated.
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
SB
MDAC 2.6 onwards doesn't include Access ODBC Drivers

You need to install MDAC 2.5 over the top of MDAC 2.8, and all should be
fine.

"ErickR" <er****@innovat.com> wrote in message
news:1f**************************@posting.google.c om...
We are experiencing a problem with Sql Server 2000 linking to an
Access 97 file. We have two machines that link to this .mdb file, and
we recently upgraded one to newer hardware, SP3a, MDAC 2.8, etc. The
link on this upgraded machine no longer works, giving this message:

Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
[OLE/DB provider returned message: Cannot open a database created with
a previous version of your application.]
OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
IDBInitialize::Initialize returned 0x80004005: ].

The link on the older machine still works. We decided to try
converting a copy of the file to Access 2000 to see if the newer
patches/drivers/whatever no longer supported 97. We set up a link on
both machines to this file, and they both work. However, on the
upgraded machine, the following error is receieved

Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
[OLE/DB provider returned message: System resource exceeded.]
OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
ICommandText::Execute returned 0x80004005: ].
when making 1-3 connections to the the linked server, while the older
machine supports at least 7 simultaneous queries connecting to the
linked server and still hasn't produced that error.

Does anyone have any idea if there is a known issue with linking to
Access 97/2000 files under MDAC 2.8, Jet 4.0, etc? Any light anyone
can shine on this subject would be greatly appreciated.


Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.