Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Sammy Cantrell]

I need to connect an Actian Zen v14 Pervasive data base to Power BI On-Premises Gateway.
1. ODBC Connection to Desktop works well
2. Actian Zen v14 data base manager connects correctly with Win 10 ODBC 64 bit configured driver.
3. Gateway requires a connection string, below is the string being used. (fully descriptive have tried fewer components still same error)
    a. DSN =Pervasive2 – name setup in ODBC manager
    b. DRIVER = {Pervasive ODBC Interface} – the one working with PBI Desktop
    c. SERVER = same machine name as the gateway is installed on. So same pc as gateway has the database (no network issues)
    d. PORT = 1583 – as displayed by Zen Control Center for working connection to PBI Desktop
    e. DATABASE = PERVASIVE2 – data base name created through ODBC Manager.
    f. POOLING = false
4. Get default Gateway error -Unable to connect to data source – 2147467259

5. Please see ODBC connection that is working with the PBI Desktop, DSN, DATABASE, and DRIVER all confirmed with this connection.

6. Gateway and dataflow connecting okay
  – Please note the Gateway is online and ready for connections
  – Also please note the Dataflow is connected, but when I remote the skip test connection and test, get an error.

7. Error when try to test connection.

8. Testing of flow between gateway and PBI cloud shows all 32 servers connecting successfully.

9. Registry Changes made: TLS 1.2 settings
  – based on reviewing other solutions recommended making some registry changes. These have been made.
[HKEY_LOCAL_MACHINESOFTWAREMicrosoft.NETFrameworkv4.0.30319]”SchUseStrongCrypto”=dword:00000001 [HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoft.NETFrameworkv4.0.30319]”SchUseStrongCrypto”=dword:00000001

Any suggestions greatly appreciated.
Sammy Cantrell

——————————
Sammy Cantrell
Consultant
Franklin, TN
——————————

[Lutz Bendlin]

Oh where to begin 🙂

Let’s begin with the basics.  The gateway acts like your PC, and it needs to have the exact same setup to do that. That means exactly the same ODBC settings like you have on your PC, and a verified ability to connect to the data source via that ODBC connection (via the test facility, or a client on the gateway)

Next you need to consider that the gateway needs to use the EXACT same connection parameters as the desktop. That includes using the same DSN= string, down to the case (spelling)

And finally the connection impersonator on the gateway needs to have a sufficient level of access to your data source to serve all the refresh requests from the different developers that consume the connection.

Having the data source on the gateway is sub optimal.  Do not attempt to use things like “localhost”  – that will make the connection not match, and can cause issues.  Ideally the gateway cluster members use dedicated VMs with lots of memory, processors, and disk space, and no other workload.

——————————
Lutz
——————————
——————————————-

[Sammy Cantrell]

Lutz,
Thanks for taking time to review the issue.
Since the ODBC link is working great with the desktop, feel pretty sure I have all the DSN names and user rights correct.
They are exactly the same as the ones working with desktop just don’t understand what makes it different with the Gateway.
Just noticed something that may help.
 – When I select the data pathway name in the Manage Gateway view, it shows connected successfully to the pathway.
– But when I remove the check to by pass checking the system is when I get the error.

What is showing first connected and then fails?
Oh, and yes you are right, the long term plan is not to have the data base on the same machine as the gateway. This is to test the setup.
Thanks Again,
Sammy

——————————
Sammy Cantrell
Consultant
Franklin
——————————
——————————————-