lanabutana
asked on
Microsoft.Jet.OLEDB.4.0, Provider not found, Microsoft Server 2003, 64bit
I am using Windows Server 2003, 64bit and I am trying to connect to a Access DB in Visual Studio (VB) and I get the error: (It can't find the Jet 4.0)
Provider cannot be found. It may not be properly installed.
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.Runtime.InteropServ ices.COMEx ception: Provider cannot be found. It may not be properly installed.
Line 88: rs.Open("SELECT * FROM [Members]", "Provider=Microsoft.Jet.OL EDB.4.0;Da ta Source=" & Server.MapPath("App_Data/o ldMemberdb .mdb"), 3, 1)
Obviously the provider is not installed. I went on Microsoft's webpage and I downloaded "WindowsServer2003-KB82955 8-ia64-ENU .exe" which is suppose to install the Jet pack. I run the file and it says "! The image file "..\update\update.exe" is valid, but is for a machine type other than the current machine" I am guessing that I have the incorrect version of the Jet Pack.
I have read other solutions and the only one I found speaks about installing Visual Web Express and rigging it somehow. Certainly there is another way to do this?? I am under a deadline, so please help. Thanks!
Provider cannot be found. It may not be properly installed.
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.Runtime.InteropServ
Line 88: rs.Open("SELECT * FROM [Members]", "Provider=Microsoft.Jet.OL
Obviously the provider is not installed. I went on Microsoft's webpage and I downloaded "WindowsServer2003-KB82955
I have read other solutions and the only one I found speaks about installing Visual Web Express and rigging it somehow. Certainly there is another way to do this?? I am under a deadline, so please help. Thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Yes, it's a completely different animal. It's not a "server engine" rather file based like JET/Access but with the difference that SQL syntax is 100% SQL Server compatible (which JET SQL is not).
But if you have 2005 (64 bit Standard Version?) installed, why not use that?
/gustav
But if you have 2005 (64 bit Standard Version?) installed, why not use that?
/gustav
ASKER
"But if you have 2005 (64 bit Standard Version?) installed, why not use that?"
I am using that... SQL Server 2005 is installed (64 bit). I am getting an error reading Access files (mdb).
I am using that... SQL Server 2005 is installed (64 bit). I am getting an error reading Access files (mdb).
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I ended up transfering the data from the mdb to a sql table on a server that could read the mdb.
Thanks for the feedback.
/gustav
/gustav
Well, the option chosen was the one suggested:
> Your best option right now would be to move your data to
> SQL Server 2005 Express which runs smoothly with VS.
/gustav
> Your best option right now would be to move your data to
> SQL Server 2005 Express which runs smoothly with VS.
/gustav
ASKER