Forum Discussion
Error when saving report to Power BI Report Server
Is this generated by you clicking the "Take me there" link?
Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item '/Dashboards/Registrants State Map' cannot be found.;
That line and the 401 error are a bit strange?
Is there anything published on your server at all?
If so have you re-saved any reports created in previous versions of Power BI with the new version?
Nothing published currently. Will try publish some of my SSRS reports shortly.
I can access the GUI (http://powerbi/reports) just fine via Chrome and IE.
- cmikos8 years agoHelper I
What do you see in the Power BI Client when you try to publish something?
- cmikos8 years agoHelper I
I'd stay away from your SSRS reports for now and just try to get something trivial published to Power BI Report Server with Power BI client getting data from an SSAS cube
- xantari8 years agoHelper II
I don't have any SSAS cubes. The PowerBI Report I am attempting to publish is hooked to an IBM DB2 database. It runs fine locally.
- xantari8 years agoHelper II
I figured out what it was.
What lead me to the clue is the following:
1. Browsing remotely to http://powerbi/reports and powerbi/reportserver worked just fine.
2. Logged into the server and tried those same URLs and got HTTP 503 server unavailable errors, which I thought was wierd.
So I did the following:
1. Disabled Loopback check in windows (method 2 from this article: https://support.microsoft.com/en-us/help/896861/you-receive-error-401-1-when-you-browse-a-web-site-that-uses-integrate)
2. Still didn't work
3. Then went to IIS and noticed default website was there listening on port 80. I said what the heck and deleted it, and all the unused App Pools in IIS as I didn't have anything running under the default web site in IIS.
That fixed it.
I'm guessing that even though I was using host headers in Power BI for the /ReportServer and /Reports URLs it must have still been having a conflict with the default website running on port 80 for some reason. Host headers are supposed to prevent this, but I'm guessing there might be an issue in Power BI in regards to host headers and when it binds or something.