The 'Microsoft.Jet.OLEDB.12.0' provider is not registered on the local machine

Question

User1357926729 posted

Hi..

I am trying to integrate my website with the present company website.It was running in windows server 2003 and we had to migrate the server into server 2008 because of the framework issues with VS 4.0 with which my website is made.After migration,the framework issues were solved. I am facing with another issue now.Since our database is MS Access 2010 and we use Provider=Microsoft.Jet.OLEDB.12.0;Data Source=|DataDirectory|\HR Portal.accdb as the connection string. Now when i uploaded all the pages with the existing pages,when i open my pages,connection cannot be established.error is showing as " The 'Microsoft.Jet.OLEDB.12.0' provider is not registered on the local machine". when i was running the website in windows 2003 server this error was not there.there was 4.0 framework issues.now when that got solved,this error came.What should i do?any idea?my system is 32 bit.Hope someone will help me soon..its really urgent.

Answer 1

User984714447 posted

Hi

You need to install runtime installer for office 2010.

http://www.microsoft.com/en-in/download/details.aspx?id=10910

Answer 2

User1357926729 posted

Thanks for the reply..

After installing runtime installer,what should i do next?There is no change in the error when i tried loading the pages again..Hope you will reply back soon.

Answer 3

User281315223 posted

After installing the appropriate runtime-installer, did you make sure to rebuild your application? (Ensure that it has a build-target set to x86)

This Microsoft blog post discusses a similar issues has provides a few steps to solve it.

Answer 4

User1357926729 posted

After installing the appropriate runtime-installer, did you make sure to rebuild your application? (Ensure that it has a build-target set to x86)

Ya..I rebuild my application.I have opened my appln as a website,so i cant go to build target option.Then what will i do?My system is 32 bit.Please help me...

Thanks...

Answer 5

User2108829372 posted

can you try installing Microsoft Access Database Driver

http://www.microsoft.com/en-us/download/details.aspx?id=13255

 

If you still have issue change the setting in Application Pool ( Enable 32 bit application =true ) and try

Answer 6

User1357926729 posted

Hi,

Thanks for replying..

can you try installing Microsoft Access Database Driver

Where should i install access database driver.Should we do anything with our windows server 2008.should we change the server's application pool settings ?Please can you explain it for me?

When we contacted the hosted server people telling about the issue we r facing,they replied as follows:

"Access databases are no longer supported in Windows 2008. You should port them to MSSQL databases."

"This message is sent you to confirm that MS Access drivers are not installed on Windows 2008 servers, we have MSSQL and MySQL database drivers installed on 2008 servers only. So, if your application is using MS Access database, then you need to export data to MSSQL" 

Now what should i do.i cannot change my database at the present situation.Can i install Access database driver in the server.Please someone tell me a solution.Its a really crucial situation for me...

Answer 7

User1357926729 posted

Some one please help me

 

Answer 8

User2108829372 posted

try setting the apllication pool to 32 bit in your windows 2008 server

1.Right click on the Application Pool and select “Advanced Settings…” 

2.Change the “Enable 32-bit Applications” to True 

3.Click OK. 

Answer 9

User-166373564 posted

Hi sinjumujeeb

Now what should i do.i cannot change my database at the present situation.Can i install Access database driver in the server.Please someone tell me a solution.

Sorry for the issue that you are hitting,

In this situation, I think you should consider export your Access database data to MSSQL database in Windows server 2008,

With regards

Answer 10

User1357926729 posted

Windows server 2008 does not support Access.So the only solution is to export to MS SQL or to use windows server 2003.