Forum Discussion

AGo's avatar
AGo
Post Patron
6 years ago
Solved

Postgresql gateway failure

Hi!

With new update I thought Npgsql was no longer mandatory, but it seems to be if connecting with the gateway, so I followed the old path as always.

Updated .NET to last version 4.8 and installed Npgsql with GAC version 4.1.3. When adding datasource to gateway cluster I've got returned this error: The installed database provider 'Npgsql' targets an incompatible .NET Framework. Please install Npgsql version 4.0.10.0 or earlier.

 

Does this version combo of .NET and Npgsql has some problem. What versions should I use?

Thanks

Need Help
Tips and Tricks
Tutorial Requests
  • AGo's avatar
    AGo
    6 years ago

    It's now working with npgsql (4.0.10 and GAC) downgrade, hope it will be fixed soon with a full implementation of the ADO .NET data provider in the gateway.

9 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable
    6 years ago

    I reinstalled Npgsql but this time making sure to select "GAC Installation" and it appears to be working now

  • v-lionel-msft's avatar
    v-lionel-msft
    Community Support
    6 years ago

    Hi AGo ,

     

    "The installed database provider 'Npgsql' targets an incompatible .NET Framework. Please install Npgsql version 4.0.10.0 or earlier."

    Please install Npgsql version 4.0.10.0 or earlier.

     

    Best regards,
    Lionel Chen

    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

    • AGo's avatar
      AGo
      Post Patron
      6 years ago
      That's what I did: installed Npgsql version is 4.1.3
  • Anonymous's avatar
    Anonymous
    Not applicable
    6 years ago

    I have the same issue (4.0.9 is installed). I installed PBI Desktop on the gateway server and connected to the same Postgres server without issue (with the same user)

    • AGo's avatar
      AGo
      Post Patron
      6 years ago

      Anonymous can you try installing precisely version 4.0.10.0 and tell me if it solves the problem?

      • Anonymous's avatar
        Anonymous
        Not applicable
        6 years ago

        AGo I tried v4.0.10 already (the git tag/package does not specify another level of versioning, so I'm not sure if that is actually the *exact* version to which you refer) and it was the same error