The 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine - by DevMstech

Status : 

  External<br /><br />
		This item may be valid but belongs to an external system out of the direct control of this product team.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


3
0
Sign in
to vote
ID 350908 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 6/13/2008 8:37:01 AM
Access Restriction Public

Description

Hello,

We have deployed a solution in a Windows Server 2003 64-bit using ASP.NET 2.0, and in our website we have a feature that reads an XLS file uploaded from a client user.

I read some forums, but in none of them a reasonable solution was found. 

I tried the following:

1 - Compile our solution (its projects - VS2005) in x86, but IIS response was "Service Unavailable".

2 - Install the Jet 4.0 SP8 for Windows 64-bits (KB829558). The installation process stops with the following message: "\update\update.exe" is valid, but is for a machine type other than the current machine". I think it's instruction set incompatibility, but I could not find the SP8 download for x64 architecture.

3 - Use the version 12.0 (changing the connection string properly), but it was not able to read the XLS 2003 format, raising the same Exception.

I have some urgeny on this issue, because it is in final test phase and it's expected to have 1.6 million users on the website (Live@edu large deployment).

What is the best solution for this issue?

Regards
Sign in to post a comment.
Posted by dreamzt on 12/13/2009 at 9:02 PM
Hello:
i have the same issue now and very urgent.
Do you have the best solution for this issue?
Regards
Posted by Microsoft on 9/8/2008 at 4:27 PM
Thank you again for you feedback; We currently don't have a 64bit JET provider but are considering it for a future release. As a workaround you may consider running in WOW.
Posted by Microsoft on 6/16/2008 at 11:55 PM
Thanks for your feedback. We are escalating this bug to the product unit who works on that specific feature area. The team will review this issue and make a decision on whether they will fix it or not for the next release.

Thank you,
Visual Studio Product Team
Posted by Microsoft on 6/16/2008 at 3:26 AM
Thank you for your feedback, We are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)

If at any time your issue is closed unsatisfactorily, you may edit your issue via Connect and change the status to “Active.”

Thank you,
Visual Studio Product Team