The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
I have provide the credentials for SQL source. Also in local desktop it can refresh as expected. But after publish into remote service, and trigger refresh, it show the error. Don't know what the root cause.
Same here, but using Oracle data source and on-premises.
Other reports ( without parameters used in the query text) are updating nice using the same gateway with the same credentials.
I was able eliminate the credential error by removing my Incremental Refresh. Once I had the report download all data and re-publish, the report scheduler worked again and no error messages. I have a ticket open on my issue which has been pushed to the 'Product Team'.
I'm still perplexed on what's going on.
Yes! But in my case the incremental refresh is needed because the full import gives me a timeout error... thus, i use the parameters on the SQL to restrict the first query, then the M-Language enters, filtering with the same parameter. If I don't do that, the service will request all records that he allready has (consuming my database), and only then applies the filter who will select the necessary data to increment.
@cakonze @yajia - I finally heard back on my ticket for my issue (I believe you two were facing the same general error) and the agent said the PBI 'product group team' had fixed the issue. My report with Incremental Refresh did update again via the service, but only after I re-published the report back to the service. Only then did the Incremental Refresh work, the way it used to.
HTH.
I am also experiencing problems with publishing reports that refreshed as normal but now when I publish I am meet with the same error. Nothing changed. My Gateway shows that all SQL Servers are "Online: You are good to go", yet I cannot refresh the data through the Web Service.
Hi @yajia
Where the SQL source located? on-premises or Azure? It seems you added the credentials in the wrong place.
If the SQL server is on-premises, I just tested it on my side and it works fine, if it's on Azure, there's no need to configure the gateway.
For the former, Please make sure you've added the credentials on the on-going gateway. and make sure the account is consistent when you login below info:
Make sure the authentication method is the same as the desktop.
Hi Dina Ye,
Thanks for your support.
The SQL source is azure data warehouse. And we use username and password as credentials in desktop. Also we don't set any gateway. In power bi service we also set the same username and password as credentials. And that's work fine before 6/10.
In 6/10, we find refresh failed due to file size exceed 1GB. So I edit the datasets query and add some filter to reduce data size. After publish into service it failed to refresh and the error always Credentials are required to connect to the SQL source. (Source at ucmloggingdatawarehouse.database.windows.net,1433;UCMLoggingDataWarehouse.)
Do you have any ideas for this?
User | Count |
---|---|
37 | |
14 | |
12 | |
12 | |
8 |
User | Count |
---|---|
49 | |
36 | |
22 | |
22 | |
18 |