OData V4 scheduled refresh in Power BI Report server error
In Power BI Report Server I'm trying to add a scheduled refresh with Data from Business Central using the Odata V4 feed. Unfortunately, I am getting this message: OData: Request failed (404): The remote server returned an error: (404) Not Found. (Cannot process the request because the default company cannot be found. You can specify a default company in the service configuration file, or specify one for each tenant, or you can add a query string in the form of "company=[name]". You can see the available companies by accessing the default OData web service, Company. For more information, see "OData Web Services" in Help. CorrelationId: abf464e6-9697-433b-8469-79be61ed1476.) I've tried all types of verification options (Key, OAuth2 etc) Using the OData Feed in the Power BI desktop is no problem. All data is Refreshing and available. Also in the OData feed Url, the Company name is set. I don't understand why it is asking for the "company=[name]" in the report server while it is already set and works in Power BI Desktop. I look forward to your reply!
Lookup error for session ID using report server DB or API
Hi, We are using SSRS APIs to create refresh plan schedule for PBIX report on PBI report server. And we get the last run status but it does not return details. Data Refresh failed, contact the administrator, SessionId: dd13d7bf-56ef-4eed-865a-de6f67d3a50e. We do have the session ID and if we search for it in report server logs then we find the details. Also we can see details if we go to refresh plan details on report server UI. Details in SSRS log: Data Refresh failed, contact the administrator, SessionId: dd13d7bf-56ef-4eed-865a-de6f67d3a50e. Details in refresh plan UI: But we want to show this info on our web application. We already tried searching report server DB (tables, executionlog views, etc) for these details but did not find any thing. Where can we find these information/details other than reporting services logs? Any API or DB table?
Authentication error when refreshing API dataset
I have a report which has been running for almost four years that uses multiple API calls to a cloud service to pull in several different data elements in both JSON and CSV formats. These data sources are on a nightly scheduled refresh and have been working just fine until recently. I noticed as I was asked to look into an upcoming modification that the refreshes are now failing with an error stating the credentials are not valid. Thinking the bearer token in the connection string may have expired, I opened my local copy of the report in Desktop and tested the connection, and it worked just fine. The only notes I can find refer to PBIRS not supporting Web.Page and Web.BrowserContents methods for scheduled refresh, but this connection uses Web.Contents, which is supported. The connection authentication is Anonymous as the bearer token is embedded in the connection string, and this has been working until I noticed this issue. Has something changed in how the Report Server manages these types of connections? It's imperative I find a solution as my client is somewhat anxious to have their reporting stay up to date, and will have an effect on the future development they are considering.Scheduled refresh error
Hi Team, I am seeing the bellow error when the schedule refresh runs. If I download the pbix file and enter the creds locally, it does refresh and I can then republish. Why does a manual refresh work and not a scheduled refresh? We have a numer of data sources, so how do I tie this error back to which datasource is causing this failure. I've hashed out the server name. Processing errorThe operation has timed out Cluster *********.analysis.windows.net Activity ID6b31fb90-b482-4f16-9acf-8e36459a706b Request IDedcbcaf0-3f66-4392-a5c3-74a6f019a389 Time2022-03-15 14:03:57Z
