Fail to Refresh, Excel host of on premises PBIRS
ERROR: "The data connection uses Windows Authentication and user credentials could not be delegated. The following connections failed to refresh: http___<server>_olap_msmdpump.dll <catalouge>" Structure: 1. Excel hosted on PBIRS 2. on prem SSAS Tabular 3. Editions are Developer, and up-to-date 4. AD connected Article: 1. https://learn.microsoft.com/en-us/power-bi/report-server/excel-oos Appreciate any help to resovel the issue. Thanks in advance.
Excel Workbook support, Office Online Server, and Windows Server 2019
We have a business need to host Excel workbooks alongside other published Power BI and Paginated (SSRS) reports on our Power BI Report Servers. We have tested Office Online Server (OOS) on one of our development servers and it works exactly as we need. The end users are excited to add this capability to make PBIRS a "one stop shop" for internal reports. We have multiple business domains, and we plan to install one OOS instance per domain. However, one of the production servers we intend to use is running Windows Server 2019, and Microsoft does not appear to support OOS instances on a 2019 box. If this is the case, how can we provide Excel workbook support on PBIRS? A short term solution would be to stand up a separate 2016 server (which we'd rather not do), but even if we did that what happens to Excel support when 2016 reaches end-of-life?OOS fails after May 2021 update
We are late testing the May 2021 Report Server update, and encountered a problem with Office Online Server (OOS) now failing when trying to view Excel workbooks. We initially received the error message "We are unable to complete your request. Please wait a few minutes and try again." Thinking we needed to restart the OOS service following the Report Server update, we did so. Now when we try to open a workbook we get a gray screen with the message "Connection has been reset". We then tried restarting both the Report Server service and OOS, but the connection error persists. Is there something else we're missing? The report server is running on a Windows Server 2012 R2 machine, and is rendering both Power BI reports and Paginated reports without issue.Current state of Office Online Server - July 2018
I've been experimenting a bit today with installing OOS on our dev PBIRS installation, and it's been a bit of a kludgy experience. Some of it may have to do the standard build of our servers, but it got me wondering why the documentation still states: https://docs.microsoft.com/en-us/power-bi/report-server/excel-oos Limitations and considerations -The ability to view Excel workbooks within Power BI Report Server is currently in preview Is there any specific reason it's still considered "preview" that we should be aware of? Most of the OOS posts I've read have been from last year. I found that I needed to track down our Server 2012 R2 installation media and modify the documented steps to let the "Add-WindowsFeature" steps complete. Once I worked past that and attempted to retrieve the dev key from MSDN as suggested, I found that even the dev key is restricted to Visual Studio Enterprise w/ MSDN, which leaves us in the lurch since we've only had need for Visual Studio Professional w/ MSDN. We're essentially stuck until I work out getting access to the OOS install from our corporate team, so I thought I'd ask here. What is needed to bring it out of preview? Is there any initiative in place to streamline some of this configuration?
OOS has Config on PBI Repoer Server but Excel workbook does not open properly
Problem: I entered my OOS discovery url on general page of site setting and then i upload my xlsx file to pbi report servermy , but after I opened my excel workbook, the powerbi report server displays a blank page, and the page prompts: "< my internalurl > take too long to respond." Background information: I have two servers, both of which use Windows Server 2012 R2 system. They are all in the same domain. One (A) is domain controller, and the other (B) has office online server and powerbi report server installed. I configured according to the document and returned the correct XML data in "< internalurl > / hosting / discovery". Possible relevant information returned from Google Chorme: "http:///x/_layouts/xlviewerinternal.aspx?WOPIsrc=http%3A%2F%2Flocalhost%3A8080%2Fwopi%2Ffiles%2F52291a55-9092-4bda-8bba-758d0585c336&ui=en-US" header:Request URL: http:///x/_layouts/xlviewerinternal.aspx?WOPIsrc=http%3A%2F%2Flocalhost%3A8080%2Fwopi%2Ffiles%2F52291a55-9092-4bda-8bba-758d0585c336&ui=en-US Preview: Fail to load response data " About version: office online server 2016 may (run on machine B, Port:80,443,809,810) powerbi report server september (run on machine B, Port:8080) IIS Express: 8.0 (run on machine B) SQL Server 2017 (run on machine A for hosting report server database)
Report Server can't open Excel files after dns changing
Report Server can't open any Excel file since we have changed DNS of the server where Office Online Server farm was deployed. In order to solve this problem I implemented the following steps: 1. Remove the old farm with inactive url link via “Remove-OfficeWebAppsMachine” command 2. Deploy new farm with active url link via “New-OfficeWebAppsFarm” command 3. Check that the new farm was already existed via “<InternalUrl>/hosting/discovery” link 4. Run several additional commands such as Set-OfficeWebAppsFarm -ExcelWorkbookSizeMax 100 Set-OfficeWebAppsFarm -ExcelUseEffectiveUserName:$true Set-OfficeWebAppsFarm -ExcelAllowExternalData:$true Set-OfficeWebAppsFarm -ExcelWarnOnDataRefresh:$false 5. Fill in new “<InternalUrl>/hosting/discovery” link to the Report Server settings and apply it. BUT! While opening any excel file on the Report Server it shows an error with the old url link. Such error occurs with excel files only.
