Adding ODBC connection in Power BI service fails; works locally

Greetings, 

I'm running into a roadblock attempting to add an ODBC data source via Power BI Service via +New / Data sources page from the following URL. https://app.powerbi.com/groups/me/gateways 

Here are a few facts:

  1. The ODBC driver (for Sage 100) is 64-bit and on a workstation that contains Power BI Gateway (July 2022).  On the debug tab of the ODBC Manager, the test is successful: Connection succeeded. Datasource includes xxxx tables.
  2. The Gateway passes the network test. Its status is online.
  3. From Power BI Service (New), if I purposely mistype the DSN name (system DNS, not user DSN) I receive the following message (expected result). ODBC: ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified.   Note: This helps illustrate that Power BI Service is able to communicate with the driver:.
  4. If I provide the correct DSN, I received the following error: ODBC: ERROR [S0000] [ProvideX][ODBC Driver][PVKIO]Logon failed
    ERROR [S0000] [ProvideX][ODBC Driver][PVKIO]Logon failed.
  5. I've tried several variations with/without credentials embedded in the DSN string; always with the same result.
  6. From the workstation that contains the Gateway, I can successfully use Power Query in Excel locally to use the same DSN I am attempting to use in Power BI Service and it works fine.
  7. The network firewall was temporarily disabled; same results. 

Does anyone have any suggested troubleshooting steps?  

Parents Reply Children
  • 0 in reply to Russell Libby

    Solved!  The solution required manually changing the Windows account being used by Power BI Gateway.  Noteworthy: I either encountered a bug or experienced a quirk: when I followed the steps to change the Gateway service account, it completed without complaining but did NOT end up changing the account to the domain account specified, instead it changed it to LocalSystem. I had to manually change the account via editing PBIEgwService via windows Services; once I did that and confirmed that the selected account was displayed in Service Settings in the on-premises data gateway, it worked.

    Thanks Russell