Forum Discussion

Sokon's avatar
Sokon
Advocate V
8 years ago

Using MS Access as a data source with On-Premises Data Gateway

23.11.2018: Another update: The order of the installations is important. 22.11.2018: I updated this article. Let me know if it works for you!   When publishing a report that uses an on-Premises MS...
Tips and Tricks
Sokon's avatar
Sokon
Advocate V
8 years ago

Anonymous's comment is not about the enterprise gateway but about the personal gateway. In that case, people install their own gateway and are likely to run into 32bit/64bit issues depending on various circumstances, one of them being the version of the installed Office.

 

As far as i know, there's only one version of the "On-Premises Data Gateways" that should be 64bit.

 

In your case, i think you should be fine. In my scenario we use 32bit as well.

 

It should also be possible to mix 64bit und 32bit db drivers on a gateway. You just can't run both the Access 32bit an 64bit driver on the same machine - or at least not without additional tricks.

 

Hope that helps!

 

 

BWL's avatar
BWL
Helper II
8 years ago

Sokon, you are right! I  have the 64 bit "On-Premises Data Gateways" installed. 

I tried your approach and I set up an file DSN for an MS Accces DB. 

But what is exactly the string I have to use, (Gateway & Desktop) when I try to connect through DSN file?

Thank you!


  • Sokon's avatar
    Sokon
    Advocate V
    8 years ago

    Using a file DSN is not my approach and it won't work. :smileyhappy: Use a DSN-less connection. Example for that is in the main post.

    • BWL's avatar
      BWL
      Helper II
      8 years ago

      Sorry!! It is all quite new for me! ;)
      I tried your set up, and used the DSN-less connection. 

      But I get the following error. 


      Statuscode:400
      Foutcode:DMTS_PublishDatasourceToClusterErrorCode
      Tijd:Wed Jul 11 2018 16:32:20 GMT+0200 (Midden-Europese zomertijd)
      Versie:13.0.5933.161



      Warehouse:Kan geen verbinding maken met de mashup-gegevensbron. Raadpleeg de foutdetails voor meer informatie.
      Onderliggende foutcode:-2147467259
      Onderliggend foutbericht:De eigenschap 'Driver' met de waarde '{Microsoft Access Driver (*.mdb, *.accdb)}'komt niet overeen met een geïnstalleerd ODBC-stuurprogramma.
      DM_ErrorDetailNameCode_UnderlyingHResult:-2147467259
      Microsoft.Data.Mashup.ValueError.ClientLibraryName:Microsoft Access Driver (*.mdb, *.accdb)
      Microsoft.Data.Mashup.ValueError.DataSourceKind:Odbc
      Microsoft.Data.Mashup.ValueError.DataSourcePath:dbq=*path*;driver={Microsoft Access Driver (*.mdb, *.accdb)}
      Microsoft.Data.Mashup.ValueError.Reason:DataSource.MissingClientLibrary

       

      • Sokon's avatar
        Sokon
        Advocate V
        8 years ago

        Looks like you have the wrong driver installed on the gateway, if any. For a older driver you need to change the connection string like that: 

        driver={Microsoft Access Driver (*.mdb)};dbq=C:\database.mdb