Power BI Embedded OpenConnectionError

(0) Share

Report

Posted on by Tony zhong

901

Hi all,

I'm not sure in which forum I should post this. But I got error in my D365 F&O while succeeded deploying Power BI file. The error said OpenConnectionError and all the visual error saying Cannot Load Visual (which is obvious because it can't connect)

Problem is, this is Production, I don't know where to check ? In the UAT we don't have this error.

If I looking at Microsoft document to troubleshoot : docs.microsoft.com/.../embedded-troubleshoot

It is suggested about Capacity is paused. I have "slight" idea about this Capacity, got any idea what it is ?

If not mistaken, once we deploy PowerBI files from F&O menu, the report will be published "also" to the "person who deploy" Power BI Workspace, and if not mistaken, in Power BI Workspace there is a setup to switch "On" Dedicated Capacity", is this the one ? Is the report showing/load in F&O Production is taken from that person Workspace ?

Kindly advice,

Thanks.

I have the same question (0)

All responses (15)

Answers (1)

Tony zhong 901 on at

Like (0)

Report

Dear experts,

Any idea or clue how to resolve this?

Many thanks in advance,

Was this reply helpful? Yes No
Suggested answer

Navneeth Nagrajan 2,407 Super User 2025 Season 2 on at

Like (0)

Report

Hello Tony,

The error message is a bit misleading.

Capacity is usage of resources and this is applicable to manage CPU cores for processing data in PowerBI. The data that you are trying to render is timing out and this usually happens if the dataset is growing and the capacity that is allocated to trigger those reports is not enough to process the data and display it in D365 F&O. Deployment of reports will still work but its the data that's failing to trigger considering the size that is being triggered.

Suggestion 1:
The suggestion is to switch to the Dedicated capacity and try triggering the report, but do not trigger this during working hours. I have had this issue in the past and ended up raising a support request with Microsoft. They requested me to switch to the dedicated capacity and re-started the environment for me (non-working hours) and the reports worked for me.

Suggestion 2:
If Suggestion 1 doesn't work then suggestion number 2 is to raise a request to Microsoft and increase the number of dedicated V cores that define the capacity. This is setting that's available under the PowerBI Admin center where we can scale the dedicated capacity.

In the PowerBI community forum, there is a similar thread that talks about Open Connection Errors in F&O.
References:
https://community.powerbi.com/t5/Power-Query/D365-Open-Connection-Error-on-all-visuals/m-p/617177

A few questions:
1. Is there a custom entity data set that's being rendered here?
2. Is there a gateway connector setting that was initially setup in the development or the uAT phase for any of the PowerBI reports? This might be an irrelevant or a poor question, but is there a gateway connector setup?
3. Also, has your SQL database been set to an elastic pool? (It should be set to an elastic pool, but i will suggest confirm this with Microsoft because all the databases by default are upgraded to elastic pooling SQL Server databases)

Thanks,
Navneeth Nagrajan | Dynamics 365 Technical Consultant

Was this reply helpful? Yes No
Tony zhong 901 on at

Like (0)

Report

Hi Navneeth,

Many thanks for your reply.

One question come to mine, if we switch to dedicated, may I know to which Workspace we should do the setup ? I happened to know in PowerBI.com setting only, that is to create PowerBI Workspace then go to Workspace setting, there is Dedicated Capacity switch under Premium (and yes, I have premium). But I do not know when we deploy from Dynamics 365 F&O, to where the report is deployed, I can see in MyWorkspace but I doubted this is the report that Dynamics 365 F&O reaching, or is it ?

Another question is in fact you're right, we do initially set On-premise gateway in development, and we drop it in UAT as we no longer need it. and in UAT we do not have this "OpenConnectionError". But if that is also a causing factor, may I know what should I do next ?

For the elastic pool, yes it is. And yes it is Custom Entity, may I know what should I be concerning with ?

in addition, yeah I also found the same link in Power BI community, but it's not being answered unfortunately.

Thanks again.

Tony

Was this reply helpful? Yes No
Suggested answer

Navneeth Nagrajan 2,407 Super User 2025 Season 2 on at

Like (0)

Report

Hello Tony,

My responses are inline.

1. Another question is in fact you're right, we do initially set On-premise gateway in development, and we drop it in UAT as we no longer need it. and in UAT we do not have this "OpenConnectionError". But if that is also a causing factor, may I know what should I do next ?
A] Well, if you have published reports onto PowerBI workspaces through the Gateway in case of the development machines, then yes you will need the gateway setting post UAT deployment because the connection string contains the gateway details. The connection errors come up because the gateway credentials and the connection string is missing.

2. For the elastic pool, yes it is. And yes it is Custom Entity, may I know what should I be concerning with ?
A] This was a question. Elastic pooling is recommended these days. I had to raise a service request to do so, but in your case its already done so nothing to worry as such.

Will revert back to you with a response for the workspace question.

Thanks,
Navneeth Nagrajan | Dynamics 365 Technical Consultant

Was this reply helpful? Yes No
Tony zhong 901 on at

Like (0)

Report

Hi Navneeth,

I'm sorry to confuse you, regarding the gateway, I publish again the report with new name with no gateway attached, because in UAT environment we already using the Azure SQL DB. Do you think, it is still bring the gateway information ?

I've got some information that actually F&O > Deploy Power BI File is not publishing anything to PowerBI.com.

If you can access AXUG www.pbiusergroup.com/.../viewthread

So, now I think, If it is regarding Capacity and to setting that is through Power BI Workspace, how we connecting F&O Workpsace to use which Power BI Workspace (which set to use certain PowerBIEmbedded service) ?

And is this achieve through some setup in some parameter setting in F&O ? or must do it through coding in Visual Studio ?

The menu PowerBI.com configuration only setting the Apps Registration in Azure, right ? there is no setting to PowerBIEmbedded Service during the creation.

Thanks,

Was this reply helpful? Yes No
Tony zhong 901 on at

Like (0)

Report

Hi Navneeth,

If you don't mind, let's start from the beginning.. When you said on Suggestion 1 :

The suggestion is to switch to the Dedicated capacity and try triggering the report, but do not trigger this during working hours.

What Dedicated capacity did you're referring to ? And how or where to achieve that ?

Because I might assumed wrongly, and just jump into that Power BI Embedded and Power BI Workspace stuff, which you've probably talking different thing. And about triggering, what is the exact mean of triggering you're saying ? is it by running it by mean just open the report ? or I should deploy again ?

Thanks,

Was this reply helpful? Yes No
Tony zhong 901 on at

Like (0)

Report

Hi Navneeth,

Just a few updates, I tried to deploy and check the standard Analytics pages : like for example Project management workspace - Analytics and Work Order management workspace - Analytics. It is running without any error.

So currently I'm not sure that my custom workspace error is because of the Dedicated Capacity stuff.

Was this reply helpful? Yes No
Suggested answer

Navneeth Nagrajan 2,407 Super User 2025 Season 2 on at

Like (0)

Report

Hello Tony,

I'm sorry to confuse you, regarding the gateway, I publish again the report with new name with no gateway attached, because in UAT environment we already using the Azure SQL DB. Do you think, it is still bring the gateway information ?
A] If you are publishing the report with no gateway in there, then it won't publish the report with the gateway details in the connection string.

So, now I think, If it is regarding Capacity and to setting that is through Power BI Workspace, how we connecting F&O Workpsace to use which Power BI Workspace (which set to use certain PowerBIEmbedded service) ?
A] The PowerBI workspace that you connect to through F&O will always end up showing in your Own Workspace which is called MyWorkspace. The reason for this is when you publish the PBI reports there is no option that the Publish PowerBI Report gives us with respect to publishing the report to PowerBI.com. We need to go and manually pull out the report from MyWorkspace to the App workspace.

And is this achieve through some setup in some parameter setting in F&O ? or must do it through coding in Visual Studio ?
A] Publishing to Individual workspaces would require some custom development. I am not sure whether it will be inside F&O or inside an Office project in Visual studio.

The menu PowerBI.com configuration only setting the Apps Registration in Azure, right ? there is no setting to PowerBIEmbedded Service during the creation.
A] The alternate to the Apps Registration option in Azure is go to also https://dev.powerbi.com/apps and provide the PowerbI.com setting in there. With respect to PowerBIEmbedded you will have to provide the same application id and the application secret key while setting up Embedded PowerBI in Azure.

Thanks,
Navneeth Nagrajan | Dynamics 365 Technical Consultant

Was this reply helpful? Yes No
Tony zhong 901 on at

Like (0)

Report

Hi Navneeth,

Thank you so much for the detail. It's getting clearer and clearer. Although, please allow me to take back to the original issue here, regarding the error "OpenConnectionError", your advice seems inline with Microsoft Docs about troubleshooting this embedded, they also talking about Dedicated Capacity.

So what is this Dedicated Capacity referring to ? where can I check and how can I switch to it like your suggestion no 1 ? Because there are 2 suggestions, right, and the 2nd is depends on the 1st.

Sorry for the trouble and really appreciate this.

Thanks.

Was this reply helpful? Yes No
Suggested answer

Navneeth Nagrajan 2,407 Super User 2025 Season 2 on at

Like (0)

Report

Hello Tony,

So what is this Dedicated Capacity referring to ? where can I check and how can I switch to it like your suggestion no 1 ? Because there are 2 suggestions, right, and the 2nd is depends on the 1st.

Dedicated capacity is number of processor cores dedicated to process a PowerBI report that includes, reading, processing, data transformations, latency and drill through into specific reports. This is very similar to D365 Finance and operations where the recommended Capacity is D13_V2 (if you are setting up On-Premise virtual machines). Unfortunately, there is not much documentation around how much dedicated capacity is required for PowerBI reporting.

Suggestion number 2 refers to the point that if the currently assigned dedicated capacity (as mentioned in suggestion number 1) fails to deliver the expected performance then you can raise a request to Microsoft requesting them for a recommendation about the required dedicated capacity. In the PowerBI admin center, you can scale up the dedicated capacity by reaching out to a PowerBI administrator who manages the capacity of these reports. If you happen to raise a service request with Microsoft, I would check with them the following:
1. Dedicated capacity recommended for a PowerBI report
2. If the dedicated capacity fails to deliver the required performance then what is the recommendation? This is for future references.

Happy to answer questions, if any.

Thanks,
Navneeth Nagrajan | Dynamics 365 Technical Consultant

Was this reply helpful? Yes No