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

    Question

  • Hi all,

    I am receiving the above error on my Report server, when I am trying to run a report-which is Windows Server 2008. I am running Reporting Services 2008.

    From reading up I beleive this is because there is not Jet Provider for 64bit.

    How can I force Reporting Services to run in 32bit mode or run this Jet Provider in 32bit mode?

    If thats not the issue I apologies, what could be the cause of this error.

    Many Thanks

    Milli

    Monday, June 01, 2009 3:07 PM

Answers

  • Hi Milli,

     

    As you have mentioned, the Microsoft Jet 4.0 Database Engine is not worked for X64.

     

    I assume you want to show data from Excel, Access, flat file or the others in a report. If so, I suggested you to use SQL Server Integration Service (SSIS) package as a workaround, Please follow the below steps to use SSIS packages:

    1.      Open SQL Server Business Intelligence Development Studio.

    2.      Create a new project. Select “Integration Services Project” under “Business Intelligence Projects”

    3.      In the Data Flow tab, add an Excel Source and a DataReader Destination.

    4.      Double click each item and create a connection.

    5.      In the DataReader Destination make the mapping between the Excel sheet and the ADO.NET data reader.

    6.      In Solution Explorer, right click and select Properties.

    7.      Click the Debugging node.

    8.      Set Run64BitRuntime to False.

    9.      Build the project.

    10.  Open the Reporting Services project.

    11.  Create a new datasource point to the SSIS package.

    12.  In report designer, in the data tab, use the name of the data reader to retrieve data from SSIS package.

     

    For more information about using SSIS package as a workaround, please see the following articles in SQL Server Books Online:

    Configuring Reporting Services to Use SSIS Package Data: http://msdn.microsoft.com/en-gb/library/ms345250(SQL.90).aspx

    Defining Report Datasets for Package Data from SQL Server Integration Services: http://msdn.microsoft.com/en-gb/library/ms159215(SQL.90).aspx

     

    Please feel free to ask, if you have any more questions.

     

    Best Regards,

    Jin Chen


    Jin Chen - MSFT
    Wednesday, June 03, 2009 9:33 AM
    Moderator

All replies

  • If you ever find a way let us know--AFAIK it's not possible outside of running a separate 32-bit HyperV.

    --
    _____________________________________________________________________ _____
    William R. Vaughn
    President and Founder Beta V Corporation
    Author, Mentor, Dad, Grandpa
    Microsoft MVP
    (425) 556-9205  (Pacific time)
    Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)
    http://betav.com  http://betav.com/blog/billva
    ________________________________________________________________________ ____________________
     
     
    "Milli_22" wrote in message news:9e999fb4-5a39-41c 4-8fd7-46193a223673...

    Hi all,

    I am receiving the above error on my Report server, when I am trying to run a report-which is Windows Server 2008. I am running Reporting Services 2008.

    From reading up I beleive this is because there is not Jet Provider for 64bit.

    How can I force Reporting Services to run in 32bit mode or run this Jet Provider in 32bit mode?

    If thats not the issue I apologies, what could be the cause of this error.

    Many Thanks

    Milli

    Tuesday, June 02, 2009 6:14 PM
  • Hi Milli,

     

    As you have mentioned, the Microsoft Jet 4.0 Database Engine is not worked for X64.

     

    I assume you want to show data from Excel, Access, flat file or the others in a report. If so, I suggested you to use SQL Server Integration Service (SSIS) package as a workaround, Please follow the below steps to use SSIS packages:

    1.      Open SQL Server Business Intelligence Development Studio.

    2.      Create a new project. Select “Integration Services Project” under “Business Intelligence Projects”

    3.      In the Data Flow tab, add an Excel Source and a DataReader Destination.

    4.      Double click each item and create a connection.

    5.      In the DataReader Destination make the mapping between the Excel sheet and the ADO.NET data reader.

    6.      In Solution Explorer, right click and select Properties.

    7.      Click the Debugging node.

    8.      Set Run64BitRuntime to False.

    9.      Build the project.

    10.  Open the Reporting Services project.

    11.  Create a new datasource point to the SSIS package.

    12.  In report designer, in the data tab, use the name of the data reader to retrieve data from SSIS package.

     

    For more information about using SSIS package as a workaround, please see the following articles in SQL Server Books Online:

    Configuring Reporting Services to Use SSIS Package Data: http://msdn.microsoft.com/en-gb/library/ms345250(SQL.90).aspx

    Defining Report Datasets for Package Data from SQL Server Integration Services: http://msdn.microsoft.com/en-gb/library/ms159215(SQL.90).aspx

     

    Please feel free to ask, if you have any more questions.

     

    Best Regards,

    Jin Chen


    Jin Chen - MSFT
    Wednesday, June 03, 2009 9:33 AM
    Moderator