Forum Discussion

MYeung's avatar
MYeung
New Member
4 years ago
Solved

Gateway Connection Error after Removing Datasource

I'm running into a "You don't have any data gateways" error after removing a data source that has a gateway connection. We moved to using a different connector for the data, so I no longer need this datasource in my data model. However, whenever I remove it from the data model, I'm unable to connect to the live gateway connection for my new data sources. Adding the data source back in resolves the issue, but the data source will be deprecated eventually.

 

I've tried clearing the cache on my browser, deploying to other workspaces, deleting the dataset and report and redeploying, but haven't had any success. Any thoughts or ideas on how to fix this?

 

 

  • Issue appeared to be related to a service account. Using an individual's account for the gateway authentication appears to have solved this error.

5 Replies

  • Issue appeared to be related to a service account. Using an individual's account for the gateway authentication appears to have solved this error.

  • re-authenticate the remaining data sources further down in the page.

    • MYeung's avatar
      MYeung
      New Member

      The "Data source credentials" is grayed out for me. In my experience, you connect to the gateway connection before authenticating the data sources in the workspace. I also tried clearing and reentering my credentials for all data sources in desktop before deploying to the workspace, and that didn't work either.

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi MYeung ,

     

    Please try adding new data source and matching the new data source for dataset before deleting the previous data source.

     

    Best Regards,

    Jay

    • MYeung's avatar
      MYeung
      New Member

      Hi Jay,

       

      I've tried this without success. I added a new Denodo connection in increments and replaced 8 SQL Server connections with Denodo connections in sets of 2 data sources. After removing the last SQL Server connection the error started to appear. 

       

      Thanks,
      Marvin