Error: DMTS_invalidFormatConnectionDetailsError

[brunozanoelo]

I cant send my reports to the web app because this error, i already sent a lot of times, i don't know what happen!

The error say STATUS 200.



Cans someone help me?

[Chinoos]

I'm also getting the similar error while publishing, please help in resolving this issue and the cause of this error.

This checked the gateways and data sources, all are well and fine.

[brunozanoelo]

I managed to solve this problem in a temporary way. In my case, I changed the ODBC driver name that is in the file to another name, after doing this, I tried to publish it again in power bi app and got success.

Problem ocurred for before i changed this: For some reason, the power bi failed to make data update when I published the files in the power bi platform, this was the only way I could but I do not believe that is the final solution.

[v-qiuyu-msft]

@brunozanoelo Would you please translate error messages in those two images to English, so that we can see which error throws out?

In your scenario, as you mentioned you create a .pbix file in desktop connects to ODBC driver, after change the ODBC name in data source, publish is working. I would suggest you check is there any difference between those two ODBC file.

Also from the first image, there is a issue when you create a ODBC data source under data gateway. You need to install the on-premises data gateway on the server which has ODBC file.  

In addition, to publish the report to Power BI Service, you can use Get Data->Files-> Local File in Power BI Service to connect to and upload a Power BI Desktop file.

@Chinoos You can also try the Get Data->Files-> Local File in Power BI Service to see if the report can be published successfully.

Best Regards,
Qiuyun Yu

[brunozanoelo]

Sure @v-qiuyu-msft!

I have not yet understood what is the origin of this error, as previously I usually sent my reports to the Power BI service. After I made the settings for the gateway's on premises for them, I published again these same files over a 5 or 6 times.

This error began to appear when I created a NEW file and contained no data, when I tried to publish it, the system showed me this message, in my view, I see no problems in sending a file without data, as it can come to contain data refresh gradually by the gateway.

The problem is not in Desktop Pro, but in the Power BI service because the same error occurs when I select a file from the browser and not using the Desktop Pro.

First time tried:
Error status 500 >error status 200

other's:
Just error status 200

The Power BI is a great tool but perhaps be starting, still has many bugs and practical problems

[v-qiuyu-msft]

Hi @brunozanoelo,

1. Would you please use Fiddler trace as well as the .pbix file for us? That would be helpful for investigating the issue.
3. Please try to publish the file from a different machine to see if the same issue occurs.

Best Regards,
Qiuyun Yyu

[brunozanoelo]

@v-qiuyu-msft, hello! Fine?

1. Would you please use Fiddler trace as well as the .pbix file for us? That would be helpful for investigating the issue.
What fiddler trace? It's a debugger?

3. Please try to publish the file from a different machine to see if the same issue occurs..
I already tried in another computer but the error continues... Idk exacty why the error appeared but i think is something about the gateway connection...

[v-qiuyu-msft]

---

What fiddler trace? It's a debugger?

---

@brunozanoelo Fiddler is a web debugger. You can monitor HTTP traffic during the time error throws out. You can take a look at this video: Tracing Power BI with Fiddler . Please share this trace file with us. Also would you please share which Power BI Service account you used when the issue occurs? The product group should be able to also do a clean up on the user side, but they need this account.

@BIXL@Chinoos Please take a look at my posts in this thread.  If possible, you can also share Fiddler trace file, Power BI Service account with us to look into the issue.

Best Regards,
Qiuyun Yu 

[v-qiuyu-msft · Accepted solution]

@brunozanoelo@BIXL@Chinoos 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

Please implement the above action plan and update the results to me.

Best Regards,
Qiuyun Yu

[BIXL]

Hi
Thanks for the information

It seems that the issue is resolved now (at least for me).
I can now publish the same file without work around.
I must say that my new client with the odbc issue was very concerned about the time that it took to fix this and even more, the fact that no one from support team contact me about my ticket yet.
I "found out" about the fix least week when I tried to debug the problem....
I also posted another question in this forum about the support team SLA. I can say that the current response time is far from good.
Thanks

[BIXL]

HI @v-qiuyu-msft

Is there another place beside this thrade where I can upload the fiddler log file and give the account name (that only the microsoft team can look at ?)

thanks

[BIXL]

I opened a support ticket for that issue.

hope they can resolve it soon.

[BIXL]

I have the same problem working with odbc driver over intersystem cache DB.

Working in the desktop is fine and I can refresh data.

I also managed to publish it and configure data gateway so data is refreshing regulary.

after mading some minor changes in the model (new measures over the same data), when republishing it I get the error :

DMTS_InvalidFormatConnectionDetailsError.

in my case It's seems that the service is unstable

when can we expect a solution for that ?

thanks

[Chinoos]

I have tried the same, by Get Data option, still getting error.

I'm able to do successful data refresh(up-to-date data) on power BI desktop,