Publishing error

[ShabnamKhan]

Greetings everyone! 

I always found this forum super helpful and responsive to my needs. Today, I need another favor!

I have been receiving this error message for the last two days now.

I never got this error message before; and others are not getting this error when trying to publish the same PowerBI report to the same workspace. While searching online for help, I came across a few posts which did not resolve my issue yet. I tried the following:

1. Cut down on my data size and republished, didn't work 😞
2. Uninstalled and reinstalled the latest version of Power BI desktop and tried publishing, didn't work 😞
3. Went to Power BI service, Get Data-> Files to get pbix files, didn't work either 😞

Little background here: we utilize multiple workspace in our organization. And we are hosting an app to external users via one of the workspaces. Our reports are using dataflow that are stored within the workspace. Up until recently we had pro license, and we were on a trial license for Premium Per User (PPU). While being on the trial version of PPU license, we upgraded our workspace settings to Premium. It’s the same workspace that’s hosting the app for external users. Our external users are all on pro license. All the scheduled refreshes failed as we upgraded the workspace to Premium with the following error message.

Data source error:

Shared caller trying to read premium per user information.. The exception was raised by the IDataReader interface. Please review the error message and provider documentation for further information and corrective action.

So, we moved our workspace setting back to ‘Pro’ and tried refreshing. When that did not help, we created an entirely new workspace and setup a new dataflow with the same views and tables. After updating the reports with the newly created dataflow we were finally able to have PowerBI service to refresh our reports. I am still unsure what happened there. And, before I know I am stuck with this new error message and can’t even publish any report to PowerBI service.

Thanks in advance for your help and time 🙂

[Anonymous · Accepted solution]

Hi @ShabnamKhan ,

I'm sorry I didn't fix this. Please refer to the following topic to see if it helps you.

Solved: "Unable to write to the transport connection." - Microsoft Power BI Community

The report is quite large 162,106kb could this be an issue?

Yes, too large data model may be a reason for your scenario, maybe you can try to cut down you data size and try again.

Then I also found a similar blog , please refer to it.

How to Fix 'An Existing Connection was Forcibly Closed by the Remote Host' Error? - Appuals.com

• TLS 1.1/1.0 Usage: If the application is running on TLS 1.1 or TLS 1.0, it might trigger this error due to them being depreciated. TLS 1.2 is the way to go when selecting the protocol which the application uses.
• Cryptography Disabled: If Cryptography has been disabled for your machine it will prevent the usage of TLS 1.2 and will fall back on TLS 1.0 which might trigger the error.
• Socket Implementation: In some cases, a particular type of socket implementation triggers the error. There is a bug with some implementations by “.NET” application and it might cause this error.
• Missing Code: For some people who were using the Entity Framework, it was observed that a certain line of code was missing due to which the error was being triggered.
• Outdated “.NET” Framework: In certain cases, if the “.NET” Framework has been disabled, this error might be triggered. Certain tasks require the “.NET” framework to be updated to the latest version in order for them to work properly.

If still not helpful,   I suggest you to open a support ticket for help if you are a pro user.

https://powerbi.microsoft.com/en-us/support/

Best Regards

Community Support Team _ Polly

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[ShabnamKhan]

@Anonymous 
Thank you for your reply. We have already created a new dataflow on a non PPU workspace and pulling data from there and the reports are currently refreshing. But, I am still getting this error message when trying to publish to any workspace.  My co-workers are all able to publish successfully but I can't. So, I am seeking solution for that. Could you please help me troubleshoot this publishing error issue? Thanks!

[Anonymous]

Hi @ShabnamKhan ,

If you rename your report and try to publish from Power BI Desktop again, will you publish successfully? Publish from Power BI Desktop - Power BI | Microsoft Docs

There does some publish issues listed in official document, but I’m not sure whether it is applicable to you.

Best Regards

Community Support Team _ Polly

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[ShabnamKhan]

Hello @Anonymous 
Unfortunately, it did not resolve my issue. I renamed my report and saved it and then published it to recieve the error again. I sitll have the issue pending and I am using a VM to publish my report now. If you want I can accept it as a solution altough it didn't really resolve my issue. Let me know. Thanks!

[Anonymous]

Hi @ShabnamKhan ,

Does that make sense? If so, kindly mark my answer as the solution to close the case please. Thanks in advance.

Best Regards

Community Support Team _ Polly

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

Hi @ShabnamKhan ,

You cannot have a dataflow run in a PPU workspace, be imported into a Power BI dataset in another workspace, and then allow users without a PPU license to consume the content.

Power BI Premium Per User - Power BI | Microsoft Docs

I have also found a similar post, please refer to it to see if it helps you.

Solved: Re: help with error Premium caller trying to read ... - Microsoft Power BI Community

The solution is to place the Dataflow on a non PPU workspace (this losing the benefits of PPU) or place the Report and Dataset on a PPU workspace (which onlu PPU licences can access.  

Best Regards

Community Support Team _ Polly

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.