Share via

Tabular Model not processing in Azure AS

Scott Kent-Collins 1 Reputation point
2022-09-21T06:03:59.36+00:00

We're testing migrating existing SSAS Tabular models from on-prem to Azure AS, but I'm running into processing errors with the Azure AS model.

Background

  • Simply SSAS tabular model - compatibility level = SQL Server 2016 RTM (1200)
  • Data source connects to an Oracle DB using a Service Account.
  • Connection string = Provider=OraOLEDB.Oracle;Data Source=SERVER;User ID=SERVICEACCOUNT;Password=**********;Persist Security Info=true

The model deploys (via Visual Studio) and processes fine to our on-prem SQL Server. I can connect in SSMS, browse, re-process etc. Can connect to it via Excel etc.

When deploying to our Azure AS server the metadata deploys, but there is an error when processing:

Failed to save modifications to the server. Error returned: 'OLE DB or ODBC error: Received error payload from gateway service with ID 91022: An exception encountered while accessing the target data source..

Further details

  • We have an On-Premise Data Gateway setup and it is connected in our Azure AS server resource.
  • The SERVICEACCOUNT used in the model is included as a Server Admin for the on-prem SQL Server.
  • I have added a Data Source to the Gateway connecting to the same SERVER with the SERVICEACCOUNT details... this connects fine.

Questions

  1. How does/should the model hook into the Gateway datasource?
  2. I suspect it is auth/credential related, but very unsure what to do from here? Or what to instruct IT dept to do with accounts (local AD or Azure AD).
  3. It also might be an Oracle OLE DB Provider issue, but I'm hoping to ensure credentials are sorted first.

Kind regards.
Scott

Azure Analysis Services
0 comments No comments

1 answer

Sort by: Most helpful
  1. KranthiPakala-MSFT 46,827 Reputation points Moderator
    2022-09-22T23:33:03.377+00:00

    Hello @Scott Kent-Collins ,

    Thanks for the question and using MS Q&A platform.

    From the error message it seems like it is related to access issue but in the past, I have seen users facing this error message when there are discrepancies with data source data types, hence in order to narrow the root cause, it is required to further investigate on the on-prem gateway logs to get more clarification.

    For further troubleshooting of the gateway please refer to this documentation. https://learn.microsoft.com/en-us/data-integration/gateway/service-gateway-tshoot#troubleshooting-tools

    In case if it is not helpful, I recommend filing a support ticket for deeper investigation. If you don't have a support plan, please let me know here.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.