User Profile
JanRambo
Regular Visitor
Joined 8 years ago
User Widgets
Contributions
Re: MS SQL server timeout
Hi, we have checked on the SQL server timeout and it set far beoynd our timeout error. We have one more time republished all reports and manually set timeout to 120min prior to publishing to PBI service and it worked. Very strangely, now data sets are refreshed normally without hitting original timeout period of around 55 mins. I just hope this will be stable now :) Thanks for help! Jan32KViews1like3CommentsPorts to be opened for On-Premise Gateway towards MS SQL
On top of the: https://community.powerbi.com/t5/Service/MS-SQL-server-timeout/m-p/375307#M41329 What ports should be opened between the On-Premise Gateway, which is installed on an app server, and MS SQL server based elsewhere? Is 1433 sufficient? Thanks a lot! JanSolved23KViews0likes1CommentMS SQL server timeout
Hello PBI team, we have following scenario: a) On-Premise Data Gateway is installed on an app server, b) MS SQL as a source data is geographically elsewhere, c) 3 reports published on PBI service, each max 3 MB: 1 report with 3 queries 2 report with 4 queries 3 report with 1 query All ports from app server allowed to Azure, as well Azure data center reachable from SQL server. App server allowed to communicate on port 1433 towards SQL server. All reports (data sets) had been scheduled to refresh for a moth without a single failure. Then suddenly from 1st of March, only 1 report is being updated every day, also without a single failure, #3 with 1 query. The other ones always fail: - when scheduled, timeout happens after around 55 mins - when refreshed on demand from PBI service, timeout happens between 10-20 mins. Type or error: Microsoft SQL: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. What we tried: - republishing 2 reports, still the same. We are really frustrated, as network team says all is good. Any ideas please, what went wrong? Thank you very much for help! Jan Rambousek Underlying error code: -2147467259 Table: Query1. Underlying error message: Microsoft SQL: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259 Microsoft.Data.Mashup.ValueError.Class: 11 Microsoft.Data.Mashup.ValueError.DataSourceKind: SQL Microsoft.Data.Mashup.ValueError.DataSourcePath: xxxxxxx Microsoft.Data.Mashup.ValueError.Message: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. Microsoft.Data.Mashup.ValueError.Number: -2 Microsoft.Data.Mashup.ValueError.Reason: DataSource.Error Cluster URI: WABI-US-NORTH-CENTRAL-redirect.analysis.windows.net Activity ID: 7c3d4321-07d5-4f14-81b4-a99ecf2ae78a Request ID: 22b38473-5eb1-4167-9af2-04fc727d48af Time: 2018-03-14 10:24:48ZSolved30KViews0likes6Comments
Data Privacy
Microsoft Fabric Community and Privacy
To learn more about how we manage your data, please review the Microsoft Fabric Community Data Privacy guide.