Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've tried to deploy a small website (ASP.NET) which is using an MS ACCESS 2010 db. Deploying the website on the server I get the following error:

The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine. Connectionstring used : Provider=Microsoft.ACE.OLEDB.12.0; Data Source=path-to-db

MS Office is not installed on the server and neither is the Access Database engine. The website is runnin in a shared hosting environment, so I am not able to install office on that server, so may I somehow deploy the provider by dll's?

Is it possible to deploy the drivers needed for ASP.Net to connect to the database without having to run an installation on the server. As this is in a shared hosting environment, I am not able to install anything. Only fileupload by ftp.

share|improve this question
What version of Windows is on the server? Also, does the application pool run as a 64Bit process? Many COM objects only work in 32 Bit. – Peter Hahndorf Jul 1 '12 at 10:49

so may I somehow deploy the provider by dll's?

No. Brutally speaking you fucked that up - you should have selected the provider with technology that you need, or should have (a lot more common) used SQL Server for development - Access is kind of rarely used in this environment.

Back to the drawing board, and this time make your homework properly.

share|improve this answer
We actually have the same issue. No way to use Access in a shared hosting environment? MDB is used from a 3rd party tool as a "file-type". So it's out of our hands. – Remy Nov 27 '14 at 9:01
No, not unless the shared hoster supports it. And a third party using access in 2014 is reckless - a good reason to tell that third party to go and party somewhere else. THis is not 1995. – TomTom Nov 27 '14 at 9:27
It's a legacy system. Out of my control. – Remy Nov 27 '14 at 13:45
Put it on a machien you control - then you can install the drivers necessary. The legacy obviously now needs a virtual machine. – TomTom Nov 27 '14 at 13:46
Yep, I was hopping there is a different solution. – Remy Nov 28 '14 at 8:13

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.