Re: 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine
- From: "TompIfe" <tpskonto@xxxxxxxxxxxxxxxx>
- Date: Mon, 18 May 2009 15:46:23 +0200
Hi Steven Cheng,
I cannot see the %systemdrive%\Inetpub\AdminScripts directory?
The machine runs Windows Web Server 2008.
Kind regards,
Tom Pedersen
""Steven Cheng"" <stcheng@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:JbR6UQ30JHA.2060@xxxxxxxxxxxxxxxxxxxxxxxxx
Hi Tomplfe,
Also, you can try temporarily switch the ASP.NET web app to 32 bit mode(in
IIS) so verify whether it is the 64-bit problem.
#Configuring IIS to Run 32-bit ASP.NET Applications on 64-bit Windows
http://technet.microsoft.com/en-us/library/cc737351(WS.10).aspx
http://support.microsoft.com/kb/894435
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx
--------------------
From: "TompIfe" <tpskonto@xxxxxxxxxxxxxxxx>
References: <OO5zPwnyJHA.3968@xxxxxxxxxxxxxxxxxxxx>
<wTOWCWGzJHA.4632@xxxxxxxxxxxxxxxxxxxxxx>
<eMJXDAkzJHA.1492@xxxxxxxxxxxxxxxxxxxx>
<6gwWBcvzJHA.4632@xxxxxxxxxxxxxxxxxxxxxx>
<OiG6bR8zJHA.1416@xxxxxxxxxxxxxxxxxxxx>
<Ou#1L6O0JHA.5036@xxxxxxxxxxxxxxxxxxxx>
<u7TFaRi0JHA.2584@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the
local machine
Date: Mon, 11 May 2009 16:28:55 +0200
Hi again,
I believed that a winform application on the 64 bit machine worked fine
because when I added the Access data base to it,
a klicked on "test connection" it said OK, and when I pressed 'preview' on
a
DataGridView of a table in the data base, it was filled with data.
However,
when I run the winform application, the DataGridView is empty. So the
"test
connection" and "preview" works despite there is no Jet provider. This
seems
a bit odd, do not you think? Which mechanisms are used for "test
connection"
and "preview", and should not an error message been given since the Jet
provider is defined in the connection string on the 64 bit machine?:
connectionString="Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=|DataDirectory|\Test.mdb"
Kind regards,
TomIfe
.
- Follow-Ups:
- References:
- 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine
- From: TompIfe
- RE: 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine
- From: "Steven Cheng"
- Re: 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine
- From: TompIfe
- Re: 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine
- From: "Steven Cheng"
- Re: 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine
- From: TompIfe
- Re: 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine
- From: Joel Lucsy
- Re: 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine
- From: TompIfe
- Re: 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine
- From: TompIfe
- Re: 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine
- From: "Steven Cheng"
- 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine
- Prev by Date: RE: How to return a public List<> from a DataContext object via WCF
- Next by Date: Re: How to return a public List<> from a DataContext object via WCF
- Previous by thread: Re: 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine
- Next by thread: Re: 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine
- Index(es):
Relevant Pages
|