aspnewbie09
asked on
The 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine
I follow this instruction: http://msdn.microsoft.com/en-us/library/tw738475(v=VS.80).aspx to get a connection to my MS Access 2000 database. It went through the wizard with no errors.
when i run the application in debug mode; got the following error:
The 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.InvalidOperationExc eption: The 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[InvalidOperationException : The 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine.]
System.Data.OleDb.OleDbSer vicesWrapp er.GetData Source(Ole DbConnecti onString constr, DataSourceWrapper& datasrcWrapper) +1709247
System.Data.OleDb.OleDbCon nectionInt ernal..cto r(OleDbCon nectionStr ing constr, OleDbConnection connection) +148
System.Data.OleDb.OleDbCon nectionFac tory.Creat eConnectio n(DbConnec tionOption s options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningObject) +100
System.Data.ProviderBase.D bConnectio nFactory.C reateNonPo oledConnec tion(DbCon nection owningConnection, DbConnectionPoolGroup poolGroup) +45
System.Data.ProviderBase.D bConnectio nFactory.G etConnecti on(DbConne ction owningConnection) +158
System.Data.ProviderBase.D bConnectio nClosed.Op enConnecti on(DbConne ction outerConnection, DbConnectionFactory connectionFactory) +1649271
System.Data.OleDb.OleDbCon nection.Op en() +47
System.Data.Common.DbDataA dapter.Qui etOpen(IDb Connection connection, ConnectionState& originalState) +53
System.Data.Common.DbDataA dapter.Fil lInternal( DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +188
System.Data.Common.DbDataA dapter.Fil l(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +573
System.Data.Common.DbDataA dapter.Fil l(DataSet dataSet, String srcTable) +161
System.Web.UI.WebControls. SqlDataSou rceView.Ex ecuteSelec t(DataSour ceSelectAr guments arguments) +2782214
System.Web.UI.DataSourceVi ew.Select( DataSource SelectArgu ments arguments, DataSourceViewSelectCallba ck callback) +27
System.Web.UI.WebControls. DataBoundC ontrol.Per formSelect () +261
System.Web.UI.WebControls. BaseDataBo undControl .EnsureDat aBound() +82
System.Web.UI.WebControls. CompositeD ataBoundCo ntrol.Crea teChildCon trols() +95
System.Web.UI.Control.Ensu reChildCon trols() +146
System.Web.UI.Control.PreR enderRecur siveIntern al() +61
System.Web.UI.Control.PreR enderRecur siveIntern al() +224
System.Web.UI.Control.PreR enderRecur siveIntern al() +224
System.Web.UI.Page.Process RequestMai n(Boolean includeStagesBeforeAsyncPo int, Boolean includeStagesAfterAsyncPoi nt) +3394
-------------------------- ---------- ---------- ---------- ---------- ---------- ----
Version Information: Microsoft .NET Framework Version:2.0.50727.4200; ASP.NET Version:2.0.50727.4016
Thanks
when i run the application in debug mode; got the following error:
The 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.InvalidOperationExc
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[InvalidOperationException
System.Data.OleDb.OleDbSer
System.Data.OleDb.OleDbCon
System.Data.OleDb.OleDbCon
System.Data.ProviderBase.D
System.Data.ProviderBase.D
System.Data.ProviderBase.D
System.Data.OleDb.OleDbCon
System.Data.Common.DbDataA
System.Data.Common.DbDataA
System.Data.Common.DbDataA
System.Data.Common.DbDataA
System.Web.UI.WebControls.
System.Web.UI.DataSourceVi
System.Web.UI.WebControls.
System.Web.UI.WebControls.
System.Web.UI.WebControls.
System.Web.UI.Control.Ensu
System.Web.UI.Control.PreR
System.Web.UI.Control.PreR
System.Web.UI.Control.PreR
System.Web.UI.Page.Process
--------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.4200; ASP.NET Version:2.0.50727.4016
Thanks
ASKER
my OS is window XP. I have download Component Checker; but i can't find it anywhere to run. where is it install? :(
thanks
thanks
ASKER
I've just checked my "install updates" and only found Service Pack 1 for MS SQL server VSS writer then 8 hotfix for SP!1.
Are you certain that Jet 4.0 is installed on your machine?
ASKER
how do i check it?
This shows how to determine the Jet level installed.
http://support.microsoft.com/kb/239114/
CompChecker should install in the same folder that contains the .msi file.
http://support.microsoft.com/kb/239114/
CompChecker should install in the same folder that contains the .msi file.
ASKER
both of mine are current verison. click on this link to see my printscreen: http://www.hosetech.com/msjet-screen-shot.jpg
thanks
thanks
That's a 64-bit operating system?
ASKER
i got it to work.
thanks
thanks
How did you get it to work?
ASKER
when creating the new website file; instead of of selection "HTTP" under Location in the lower left hand side; I choose "File System" instead. Not sure if it's the right way of doing it; but it works.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Are you sure that Jet 4.0 is installed on the machine?
Are you certain that you have Microsoft Data Access Components (MDAC) version 2.7 or later installed?
This from your linked page (above):
"If you are using Microsoft Windows XP or Windows Server 2003, you already have MDAC 2.7. However, if you using Microsoft Windows 2000, you might have to upgrade the MDAC version that is already installed on the computer. To download the current MDAC version, see Data Access and Storage Developer Center."
If you are certain, you might try running Component Checker to make sure the install is correct: http://www.microsoft.com/downloads/details.aspx?FamilyId=8F0A8DF6-4A21-4B43-BF53-14332EF092C9&displaylang=en
Run Component Checker and see if it turns up any troubles.