Skip to main content
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

rsocol

Error pinning SSRS report

Submitted by on ‎09-30-2019 01:49 AM

I am trying to follow the steps in the article https://docs.microsoft.com/en-us/sql/reporting-services/pin-reporting-services-items-to-power-bi-das..., but after clicking the "Pin to Power BI" button I am getting the following error message:

"Power BI is unable to process requests currently. Please contact PowerBI Support Correlation:9287ac8f-0e98-47ac-a4c4-6a6735b3f88b"

Status: New
See more ideas labeled with:
3 Comments (3 New)
Comments
v-qiuyu-msft
Community Support
Community Support
‎09-30-2019 11:04 PM

Hi @rsocol, 

 

It looks like it's a temporary issue. Please restart reporting services service then test again to see if the issue still occurs. 

 

Best Regards,
Qiuyun Yu

rsocol
New Member
‎10-01-2019 11:57 AM

Hello, Qiuyun Yu

 

I have restarted SQL Server Reporting Services, but the same error appears (of course, with a different correlation: 1edad34e-d3f0-4328-a4d9-5239433801cc.

 

In the ReportServerService log file I don't find any useful info either:

library!ReportServer_0-1!2740!10/01/2019-21:49:35:: i INFO: Call to GetUserSettingsAction(). User: ASNET\rsocol.
resourceutilities!ReportServer_0-1!2740!10/01/2019-21:49:57:: e ERROR: PBI service request failed, RequestId: 1edad34e-d3f0-4328-a4d9-5239433801cc with following exception: 1edad34e-d3f0-4328-a4d9-5239433801cc
library!ReportServer_0-1!2740!10/01/2019-21:49:57:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.PBIServiceUnavailable: , Microsoft.ReportingServices.Diagnostics.Utilities.PBIServiceUnavailable: Power BI is unable to process requests currently. Please contact PowerBI Support Correlation:1edad34e-d3f0-4328-a4d9-5239433801cc;

 

Could this be due to the fact that we are using a proxy to access the internet?

eldarkt
Employee
Employee
‎05-20-2021 09:48 AM

I know it's a late response, but for anyone who will find this question, below is a possible solution.

You may have this issue because of the TLS version PBIRS server configured. TLS 1.2 or newer required to make this functionality work. 
Check for more info:

https://powerbi.microsoft.com/en-us/blog/deprecating-tls-1-0-and-1-1-support-in-power-bi/

https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls

 

You can force TLS 1.2 usage by updating the registry, as described here:
https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls#systemdefaulttlsversions

 

 

 

 

Idea Statuses