cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
eMarcel Frequent Visitor
Frequent Visitor

Distributed Deployment: Something went wrong. Please try again later when opening report

Hi,

 

We use AuthenticationTypes: RSWindowsNTLM.

Users are facing this error when connecting from Windows workstations, NTLM works fine. There is no issue on Macs.

 

Here is our setup:

1. Reverse Proxy on top of two nodes:

2. Node1 is running SQL Server DB and Reporting Server PBIRS instance

3. Node2 is running Reporting Server PBIRS instance and connects to database running on Node1.

 

We are facing this terrible error "Something went wrong. Please try again later" when we keep PBIRS on both nodes started.

 

Problem doesn't appear when we shutdown one of the PBIRS instances, regardless of node. 

 

How can we troubleshoot this error?

 

1 ACCEPTED SOLUTION

Accepted Solutions
eMarcel Frequent Visitor
Frequent Visitor

Re: Distributed Deployment: Something went wrong. Please try again later when opening report

Thanks for pointing this out, for the time being I resolved the issue by reinstalling Power BI software on both nodes. 

Right now we are running May-2019 release.

 

 

View solution in original post

2 REPLIES 2
Super User
Super User

Re: Distributed Deployment: Something went wrong. Please try again later when opening report

I assume by reverse proxy that this is some sort of load balancer?

 

If so, did you follow all the documented steps for configuring PBIRS in a load balancer scenario (see https://docs.microsoft.com/en-us/sql/reporting-services/report-server/configure-a-report-server-on-a...)

 

Specifically check the BackConnectionHostNames settings. If you don't have that set then requests between the various components of PBIRS can "jump" across nodes which causes issues with many operations such as publishing reports.

eMarcel Frequent Visitor
Frequent Visitor

Re: Distributed Deployment: Something went wrong. Please try again later when opening report

Thanks for pointing this out, for the time being I resolved the issue by reinstalling Power BI software on both nodes. 

Right now we are running May-2019 release.

 

 

View solution in original post

Helpful resources

Announcements
Can You Solve These Challenge

Challenge: Can You Solve These?

Find out how to participate in the first Power BI 'Can You Solve These?' challenge.

New Badges

Incoming: New and Improved Badges

Exciting news: We've given our badges an overhaul and added brand news ones.

Ask Amir Anything

Exclusive LIVE Community Event No. 2 – Ask Amir Anything

Next in our Triple A series: Ask Amir Netz questions about the latest updates, features and future.

Analytics in Azure virtual event

Analytics in Azure virtual event

Experience a limitless analytics service built to ingest, prep, manage, and serve data for immediate use in Power BI.

Users Online
Currently online: 294 members 2,618 guests
Please welcome our newest community members: