Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
9 years ago
Solved

DMTS

i'm using on promise gateway as data source and when i try to publish to service i got the following error. 

 

"publishing failed for an unknown reason.
(DMTS_InvalidFormatConnectionDetailsError)"

 

Does anyone have same or similar problem? May I know how to fix?

 

Many thanks,

JS 

  • Anonymous BIXL I get the feedback internally, the is a known issue with ODBC data source types. The PG implemented a change that should fix this issue. The fix is scheduled to hit Prod last Thursday and should be available sometime this week. They suggested to work around the issue follow below steps currently:

     

    1. Go to manage gateways page and remove all ODBC data sources under their Enterprise Gateway
    2. Publish / Import the affected workbook
    3. Add back the ODBC data source under their Enterprise Gateway

     

    Best Regards,
    Qiuyun Yu

9 Replies

  • v-qiuyu-msft's avatar
    v-qiuyu-msft
    Community Support

    Hi Anonymous,

     

    Based on my understanding, you created a data source under on-premise data gateway, and when you published the report from Power BI Desktop, the error threw out, right?

     

    In your scenario, please try the way below to see if issue occurs:

     

    1. Publishing the file from a different machine

    2. Use Get Data->Files-> Local File in Power BI Service to connect to and upload a Power BI Desktop file.

     

    If you have any question, please feel free to ask.

     

    Best Regards,
    Qiuyun Yu

     

     

     

    • Anonymous's avatar
      Anonymous
      Not applicable

      Hi Qiuyun, 

      Thanks so much for your reply. 

       

      Do I have to publish it from a different machine? It will be hard to work in the future.
      Our on-promise gateway is installed on a server and using a service account.

      I am using an ODBC driver to connect to the data source under that gateway. 

      Right now, data source name under gateway is the same as my ODBC connection string. Do you think that's causing the problem?

      Many thanks,
      JS

      • BIXL's avatar
        BIXL
        Resolver I

        Hi Anonymous,

        I have the same problem right now working with odbc driver (over intersystem cache).

        did you manage to resolve this ?

        what kind of DB are you using with odbc ?

         

        thanks.