I have a rather weird problem regarding the SharePoint webpart for paginated reports in PowerBI.
After adding the webpart and configuring it to show a report from the powerbi server, it will work at random. Most of the time it will work right away with every report I try it with, empty or full of data from SSAS connections.
But after a few minutes or hours, the web part stops working. It just says that there is a problem at the server and I should check the logs on the server but nothing is showing in any log on the powerBi server nor the SharePoint server.
Kerberos is working in the environment (verified by me and a independed consultant) and the reports are working great from the powerbi server itself.
What could cause the report to work for a random period of time in the webpart?
That is certainly interesting. A couple questions:
- Does the report stop working for everyone viewing the report or just you?
- Does the report start working again after closing & reopening the browser?
- Does "klist tickets" show any tickets with an "End Time" in the past?
- Does "klist purge" & refresh the browser cause the report to start working again?
A couple other things you can try is:
- Enable "Verbose" logging for Reporting Services to possibly get more info
- Use a tool like Fiddler to capture the requests made between SharePoint and PBIRS
Hope this helps
Hi Jason! Thanks for the reply!
Yes the report stops working for everyone viewing the report. About 4 people.
No. It does not matter if I refresh the browser with CTRL+F5, Close and reopen the browser or restarting of all servers connected to the problem.
klist shows my tickets and shows them with valid time frame.
klist purge does not help. The problem persists.
Now I have not touched the report that accesses the SSAS instance the whole weekend. No kerberos tickets on the machine.
I open the browser and browse to the page. I get a kerbticket. The error comes right away. I refresh the page, the error persists.
I delete the webpart from the page and add it again. I configure it *exactly* like before. I press "apply" and I get the same error. I press "apply" again, and it works! My poor aching heart!
It is even getting info from the SSAS instance so it is working through and through. This will be ok for a few minutes or few hours.
Verbose logging has provided me with nothing and fiddler says everything is looking good. I have not used fiddler as a proxy between the servers I admit but that would be the next step. But monitoring the traffic between user and browser verifies the kerberos traffic and that everything is delivered as expected.
I will look into sniffing the traffic between the servers but if you have any thoughts on this I would love to hear them.
Unfortunately, if there is no information in either SharePoint or RS logs, then I think that means that you'll have to capture the traffic from SharePoint to RS using a tool like Fiddler. Hopefully, you'll find a request that failed in there that will help us out in determining where the problem might lie.
I´m not sure what the problem is but I can see that must have something to do with the authentication.
This is a trace when everything is working in my webpart, until a browser refresh at line 53.
At that point it doesnt get any response header with the authentication ticket.
POST https://powerbiextended.DOMAIN.IS:443/reportserver/ReportExecution2005.asmx HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 10.0; WOW64; Trident/7.0; Touch; .NET4.0C; .NET4.0E; .NET CLR 2.0.50727; .NET CLR 3.0.30729; .NET CLR 3.5.30729)
Content-Type: text/xml; charset=utf-8
<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Body><ListSecureMethods xmlns="http://schemas.microsoft.com/sqlserver/2005/06/30/reporting/reportingservices" /></soap:Body></soap:Envelope>
This is the call at line 53 and below.