Home All Groups Group Topic Archive Search About

Problem with .Net Framework 2 on certain machines

Author
23 Dec 2005 7:14 AM
Programatix
Hi,

I'm trying to distribute my application written using .NET Framework 2.0. It
uses a MDB file for it's database.

On certain machines with Windows XP (I have also tried updating them to
SP2), I received this exception when the application tries to connect to the
MDB

"The .Net Framework Data Providers require Microsoft Data Access Components
(MDAC). Please install Microsoft Data Access Components (MDAC) version 2.6
or later."

I have checked the machines using Component Checker Version 2.0 and has
confirmed that the MDAC installed on the machine is already 2.8 SP1.

Any help would be greatly appreciated.

Author
23 Dec 2005 8:38 AM
Miha Markic [MVP C#]
Hi,

Jet engine is a separate download (starting from MDAC 2.6 if I remember
properly) thus you have to install it (just search ms website for it)
separately.

--
Miha Markic [MVP C#]
RightHand .NET consulting & development www.rthand.com
Blog: http://cs.rthand.com/blogs/blog_with_righthand/

Show quote
"Programatix" <N$SPAMprogramatixN0000@msn.com> wrote in message
news:%23bKnUC5BGHA.2664@TK2MSFTNGP15.phx.gbl...
> Hi,
>
> I'm trying to distribute my application written using .NET Framework 2.0.
> It uses a MDB file for it's database.
>
> On certain machines with Windows XP (I have also tried updating them to
> SP2), I received this exception when the application tries to connect to
> the MDB
>
> "The .Net Framework Data Providers require Microsoft Data Access
> Components (MDAC). Please install Microsoft Data Access Components (MDAC)
> version 2.6 or later."
>
> I have checked the machines using Component Checker Version 2.0 and has
> confirmed that the MDAC installed on the machine is already 2.8 SP1.
>
> Any help would be greatly appreciated.
>
Author
23 Dec 2005 8:44 AM
Wiktor Zychla [C# MVP]
> On certain machines with Windows XP (I have also tried updating them to
> SP2), I received this exception when the application tries to connect to
> the MDB
>
> "The .Net Framework Data Providers require Microsoft Data Access
> Components (MDAC). Please install Microsoft Data Access Components (MDAC)
> version 2.6 or later."
>
> I have checked the machines using Component Checker Version 2.0 and has
> confirmed that the MDAC installed on the machine is already 2.8 SP1.
>
> Any help would be greatly appreciated.

as stated on MDAC 2.8 SP1 download page
(http://www.microsoft.com/downloads/details.aspx?FamilyID=78cac895-efc2-4f8e-a9e0-3a1afbd5922e&displaylang=en):

"This release does not include Microsoft Jet, the Microsoft Jet OLE DB
Provider or ODBC driver, the Desktop Database ODBC Drivers, or the Visual
FoxPro ODBC Driver."

since MDB connection requires Ms Jet, you have to download (and install) it
separately:

http://msdn.microsoft.com/data/downloads/updates/default.aspx#jet

I think this should solve your problem.

Regards,
Wiktor Zychla
Author
23 Dec 2005 11:44 AM
Programatix
Sadly... it doesn't solve the problem.

By the way Microsoft Access XP is installed on those machines that have the
problem. If Microsoft Access XP is already installed, then MS JET is already
installed.

Show quote
"Wiktor Zychla [C# MVP]" <wzyc***@nospm.ii.uni.wroc.pl.nospm> wrote in
message news:ePLgb05BGHA.3584@TK2MSFTNGP11.phx.gbl...
>> On certain machines with Windows XP (I have also tried updating them to
>> SP2), I received this exception when the application tries to connect to
>> the MDB
>>
>> "The .Net Framework Data Providers require Microsoft Data Access
>> Components (MDAC). Please install Microsoft Data Access Components (MDAC)
>> version 2.6 or later."
>>
>> I have checked the machines using Component Checker Version 2.0 and has
>> confirmed that the MDAC installed on the machine is already 2.8 SP1.
>>
>> Any help would be greatly appreciated.
>
> as stated on MDAC 2.8 SP1 download page
> (http://www.microsoft.com/downloads/details.aspx?FamilyID=78cac895-efc2-4f8e-a9e0-3a1afbd5922e&displaylang=en):
>
> "This release does not include Microsoft Jet, the Microsoft Jet OLE DB
> Provider or ODBC driver, the Desktop Database ODBC Drivers, or the Visual
> FoxPro ODBC Driver."
>
> since MDB connection requires Ms Jet, you have to download (and install)
> it separately:
>
> http://msdn.microsoft.com/data/downloads/updates/default.aspx#jet
>
> I think this should solve your problem.
>
> Regards,
> Wiktor Zychla
>
Author
23 Dec 2005 6:22 PM
Amnon
Oh dear! Oh dear! Oh dear!

I am moving from VB6 to .NET and was hoping that all the installation
problems associated with the use of Access 97 data bases would be solved.
I was assuming that Framework 2 would include ALL NECESSARY components for
the Data Access.
I have a lot of existing problems with many installations including Windows
XP Home and all can be traced back to the JET engine. OLEDB.

I thought that all that was behind me.

Obviously not

Oh dear! Oh dear! Oh dear!

Garry




Show quote
"Programatix" <N$SPAMprogramatixN0000@msn.com> wrote in message
news:uVynQZ7BGHA.2704@TK2MSFTNGP15.phx.gbl...
> Sadly... it doesn't solve the problem.
>
> By the way Microsoft Access XP is installed on those machines that have
> the problem. If Microsoft Access XP is already installed, then MS JET is
> already installed.
>
> "Wiktor Zychla [C# MVP]" <wzyc***@nospm.ii.uni.wroc.pl.nospm> wrote in
> message news:ePLgb05BGHA.3584@TK2MSFTNGP11.phx.gbl...
>>> On certain machines with Windows XP (I have also tried updating them to
>>> SP2), I received this exception when the application tries to connect to
>>> the MDB
>>>
>>> "The .Net Framework Data Providers require Microsoft Data Access
>>> Components (MDAC). Please install Microsoft Data Access Components
>>> (MDAC) version 2.6 or later."
>>>
>>> I have checked the machines using Component Checker Version 2.0 and has
>>> confirmed that the MDAC installed on the machine is already 2.8 SP1.
>>>
>>> Any help would be greatly appreciated.
>>
>> as stated on MDAC 2.8 SP1 download page
>> (http://www.microsoft.com/downloads/details.aspx?FamilyID=78cac895-efc2-4f8e-a9e0-3a1afbd5922e&displaylang=en):
>>
>> "This release does not include Microsoft Jet, the Microsoft Jet OLE DB
>> Provider or ODBC driver, the Desktop Database ODBC Drivers, or the Visual
>> FoxPro ODBC Driver."
>>
>> since MDB connection requires Ms Jet, you have to download (and install)
>> it separately:
>>
>> http://msdn.microsoft.com/data/downloads/updates/default.aspx#jet
>>
>> I think this should solve your problem.
>>
>> Regards,
>> Wiktor Zychla
>>
>
>
Author
26 Dec 2005 7:07 AM
Programatix
Actually most of the data access components is already installed together
with the Service Packs for Windows XP. Eg, Windows XP SP2 comes with MDAC
2.8 SP1.

The problem now is, on certain machines with all required components
installed, .Net Framework 2.0 seems to be unable to detect them... or maybe
giving out the wrong report during exception?

Show quote
"Amnon" <am***@planium.com> wrote in message
news:uQ7f82%23BGHA.1032@TK2MSFTNGP11.phx.gbl...
> Oh dear! Oh dear! Oh dear!
>
> I am moving from VB6 to .NET and was hoping that all the installation
> problems associated with the use of Access 97 data bases would be solved.
> I was assuming that Framework 2 would include ALL NECESSARY components for
> the Data Access.
> I have a lot of existing problems with many installations including
> Windows XP Home and all can be traced back to the JET engine. OLEDB.
>
> I thought that all that was behind me.
>
> Obviously not
>
> Oh dear! Oh dear! Oh dear!
>
> Garry
>
>
>
>
> "Programatix" <N$SPAMprogramatixN0000@msn.com> wrote in message
> news:uVynQZ7BGHA.2704@TK2MSFTNGP15.phx.gbl...
>> Sadly... it doesn't solve the problem.
>>
>> By the way Microsoft Access XP is installed on those machines that have
>> the problem. If Microsoft Access XP is already installed, then MS JET is
>> already installed.
>>
>> "Wiktor Zychla [C# MVP]" <wzyc***@nospm.ii.uni.wroc.pl.nospm> wrote in
>> message news:ePLgb05BGHA.3584@TK2MSFTNGP11.phx.gbl...
>>>> On certain machines with Windows XP (I have also tried updating them to
>>>> SP2), I received this exception when the application tries to connect
>>>> to the MDB
>>>>
>>>> "The .Net Framework Data Providers require Microsoft Data Access
>>>> Components (MDAC). Please install Microsoft Data Access Components
>>>> (MDAC) version 2.6 or later."
>>>>
>>>> I have checked the machines using Component Checker Version 2.0 and has
>>>> confirmed that the MDAC installed on the machine is already 2.8 SP1.
>>>>
>>>> Any help would be greatly appreciated.
>>>
>>> as stated on MDAC 2.8 SP1 download page
>>> (http://www.microsoft.com/downloads/details.aspx?FamilyID=78cac895-efc2-4f8e-a9e0-3a1afbd5922e&displaylang=en):
>>>
>>> "This release does not include Microsoft Jet, the Microsoft Jet OLE DB
>>> Provider or ODBC driver, the Desktop Database ODBC Drivers, or the
>>> Visual FoxPro ODBC Driver."
>>>
>>> since MDB connection requires Ms Jet, you have to download (and install)
>>> it separately:
>>>
>>> http://msdn.microsoft.com/data/downloads/updates/default.aspx#jet
>>>
>>> I think this should solve your problem.
>>>
>>> Regards,
>>> Wiktor Zychla
>>>
>>
>>
>
>
Author
26 Dec 2005 12:38 PM
Skanda Subramanian
Hello:

The Jet provider is not part of the recent MDACs. You would have to
download a recent version of the provider which is not part of the MDAC
downloads. Also try registering the latest version of the msjet*0.dll
and see if that's the version the Framework picks. You can also use the
"Process Explorer" to determine the version of the dll being referenced
by your application.

HTH!
Skanda.
Author
27 Dec 2005 10:46 AM
Programatix
Well... Ms Jet 4.0 SP8 is already installed and the problem is still there.

Show quote
"Skanda Subramanian" <skandy.***@gmail.com> wrote in message
news:1135600736.410750.77900@g49g2000cwa.googlegroups.com...
> Hello:
>
> The Jet provider is not part of the recent MDACs. You would have to
> download a recent version of the provider which is not part of the MDAC
> downloads. Also try registering the latest version of the msjet*0.dll
> and see if that's the version the Framework picks. You can also use the
> "Process Explorer" to determine the version of the dll being referenced
> by your application.
>
> HTH!
> Skanda.
>

AddThis Social Bookmark Button