timeout
6 TopicsThe connection either timed out or was lost.
I have a Power BI Report Server on-premises with a large number of paginated reports and dashboards with data models. Some are large and sometimes take over an hour to refresh, while others are small and refresh in less than two minutes. All data is imported; I don't use direct queries. I have an Intel Xeon Platinum 8-core CPU, speed 2.80 GHz. Occasionally, I receive the message "The connection either timed out or was lost." or "Timeout expired. The timeout period elapsed prior to completion of the operation. The exception was raised by the IDbCommand interface." I'd like to know which resources in my configuration file I can modify to give more processing time to dashboards with automatic updates, preventing them from failing or throwing timeout errors. I have a large number of dashboards that refresh at 7 AM, and I don't want any of them to be affected. Part of my configuration is attached: <Add Key="CleanupCycleMinutes" Value="10"/> <Add Key="MaxActiveReqForOneUser" Value="20"/> <Add Key="DatabaseQueryTimeout" Value="300"/> <Add Key="RunningRequestsScavengerCycle" Value="60"/> <Add Key="RunningRequestsDbCycle" Value="60"/> <Add Key="RunningRequestsAge" Value="30"/> <Add Key="MaxScheduleWait" Value="5"/> <Add Key="DisplayErrorLink" Value="true"/> <Add Key="WebServiceUseFileShareStorage" Value="false"/> <!-- <Add Key="ProcessTimeout" Value="150" /> --> <!-- <Add Key="ProcessTimeoutGcExtension" Value="30" /> --> <!-- <Add Key="WatsonFlags" Value="0x0430" /> full dump--> <!-- <Add Key="WatsonFlags" Value="0x0428" /> minidump --> <!-- <Add Key="WatsonFlags" Value="0x0002" /> no dump--> <IsSchedulingService>True</IsSchedulingService> <IsNotificationService>True</IsNotificationService> <IsEventService>True</IsEventService> <PollingInterval>10</PollingInterval> <IsDataModelRefreshService>True</IsDataModelRefreshService> <MaxCatalogConnectionPoolSizePerProcess>0</MaxCatalogConnectionPoolSizePerProcess> <WindowsServiceUseFileShareStorage>False</WindowsServiceUseFileShareStorage> <MemorySafetyMargin>80</MemorySafetyMargin> <MemoryThreshold>90</MemoryThreshold> <RecycleTime>720</RecycleTime> <MaxAppDomainUnloadTime>30</MaxAppDomainUnloadTime> <MaxQueueThreads>0</MaxQueueThreads>Solved1.2KViews0likes3CommentsScheduled Refresh of report timing out error
We have a Power BI Desktop (Optimised for Report Server File) report built and have uploaded it to our Power BI Report Server. The report talks to our Oracle SQL Database. If I refresh the report directly from the desktop file, the report will update and bring in any changes. I've attempted to try schedule this refresh on the report server however get the following error: "Timeout expired. The timeout period elapsed prior to completion of the operation. The exception was raised by the IDbCommand interface" My confusion is that when testing the Data Sources, our Oracle connection with our authentication when clicked 'Test Connection' brings back 'Connected Successfully'. The only other observation is under 'Scheduled Refresh', the 'Status' stays stuck at "Started Data Refresh" and doesn't change regardless of the page being refreshed. Does anyone have any ideas? Confusing me as the report refreshes locally and connection should work but the scheduled refresh fails1.2KViews1like1CommentAvoid Azure Session Timeout for ReportServer
We have setup Report Server and host several reports/dashboards. The authentication is via Azure Active Directory Authentication. One of the annoying issues users have been complaining about that the session times out while they are using the dashboard, causing them to refresh the dashboard and start over with their analysis. Is this is an expected issue that everyone is living with or is there some way around this?565Views0likes0CommentsTimeout expired. The timeout period elapsed prior to completion of the operation
Today, all our Power BI reports, the ones created with PBI Desktop stopped working. Both direct query, and those with an import. The error message for one of the Import reports was: [0] -1055784932: Timeout expired. The timeout period elapsed prior to completion of the operation.. The exception was raised by the IDbCommand interface. The immediate, while unelegant solution was to stop, and then restart the Power BI Report Server service. As to why the problem existed? No idea. The paginated reports created with Report Builder still worked. It was just the Power BI Desktop created reports. I addition to not allowing any PBI reports to work, we could not add any new ones. All very strange. We are running the current version: Power BI Report Server Version 1.8.7468.41510 (May 2020) logs: Looking at the log: RSHostingService_2020_08_31_00_00_06.log We did find several entries similar to the following: 2020-08-31 00:00:06.2551|INFO|70|Deleting expired log file: C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\RSPortal_2020_08_11_00_25_35.log Last written: 8/11/2020 12:25:35 AM 2020-08-31 00:00:06.2551|WARN|70|Exception deleting expired log fileSystem.IO.IOException: The process cannot access the file 'C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\RSPortal_2020_08_11_00_25_35.log' because it is being used by another process. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.File.InternalDelete(String path, Boolean checkHost) at Microsoft.BIServer.HostingEnvironment.Logger.DeleteExpiredFilesInternal(Int32 keepUntilDays, FileInfo[] logFiles) Not sure if this error is part of the problem, but stopping and restarting the PBIRS solved the problem. If anyone has insight into what caused the problem, and if there are any adjustments that can be made please advise.7.4KViews0likes2CommentsManage grouping (Internal error: An expression services limit has been reached...)
Hi, I have a report which has multiple direct queries coming from SQL views into Power BI Desktop (RS Server version). I am using the latest version (May 2020 with June 30th patches) One of the my direct query SQL views helps populate 2 visuals. There are about 6300 rows of data coming from the data source right now, and it runs very quick in SQL. The 1st visual (a KPI card) simply provides a count and works fine. The 2nd visual (a bar chart with 3 drill-downs, 4 fields) does not load and gives the error "Internal error: An expression services limit has been reached. Please look for potentially complex expressions in your query, and try to simplify them.. The exception was raised by the IDbCommand interface." After playing around, I noticed two things: 1. If i reduce the thr drill-down to 2 levels (3 fields), the 2nd visual (bar chart) works 2. Instead of running "Select <column names> from View" if i change the query to "Select top 7000 <column names> from View" the 2nd visual start working (note there are only 6300 rows of data in my testing, so output for both is same) This seems to be a Power BI aggregation/grouping issue in the bar chart (which has multiple drill-downs so has multiple levels of aggregation). Is there a setting which I could change? Or what esle can be done to manage this (especially if the number of rows increase in the future)? Would this have to be handled similarily in Power BI Report Server?825Views0likes0CommentsThe Web.Page function didn't finish within timeout on Server but finish fine in Desktop
Underlying error code: -2147467259 Table: GetFinIndexTable. Underlying error message: The Web.Page function didn't finish within timeout of 60 seconds ``` let Source = Web.Page(Web.Contents("https://www.dst.dk/da/Statistik/emner/priser-og-forbrug/forbrugerpriser/nettoprisindeks", [Timeout=#duration(0, 0, 0, 60)])), Data0 = Source{0}[Data] in Data0 ``` In Desktop version it loads just fine and takes few seconds to load. (edit) Sometimes it has error on desktop too. But loads next time. Is there a way to debug where the problem is? Increasing timeout time doesn't help.651Views0likes0Comments