Forum Discussion
Helper IIICOM error: Microsoft.PowerBI.ReportServer.ASEngineManagedRoot, No credentials were found for the ds
If your issue ends up showing "Datasource XXXXXX not found" at some points, there is a resolution here that might help: Fix for "Datasource XXXXXX Not Found" PowerBI Refr... - Microsoft Power BI Community
Community SupportHi, Niki
The new version logically has fixed this problem. What I can know is that the reason for this problem in the previous test is that these schedule refresh failures are occurring due to the data sources being Case Sensitive and the PBIX reports are using the new Model V3 . It’s best if you can fix it according to the reason. If you can’t, it is recommended to open a support ticket for the engineer who is responsible for handling the problem to test.
Best Regards
Janey Guo
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Helper IIIHi, not sure what you mean with the case sensitive issue... sources are all Sql server, so 2 microsoft applications should understand each other right.. also when entering credentials, the check says everything is fine, so then it should be fine on a scheduled refresh also... don't think this is up to the customer to fix right?
Anyway, yesterday morning we installed the new version and indeed this fixed the problem immediately. as well as another issue I had with URLfiltering that wasn't working after the last update, is now back on track.
Hope you can fix the problems in a way they don't come back anymore...
KR
- v-janeyg-msft
Hi, Niki
The new PBIRS model v3 doesn't seem to be case sensitive, but this problem has been fixed in the new version. So if you still have this problem, it's hard to say, forum support is difficult to help you, you can seek more professional help as mentioned above.
Best Regards
Janey Guo
- Niki
And the problem is back.
It looks like it is mainly occurring on older reports that have been changed a bit in PBI desktop and then uploaden/published/deployed to the reportserver again...
case sensitivity I cannot properly check, when I enter a source in capital , I see it back later in small (when uploaded).. so apperently I cannot affect this.... Also.. still the check when entering credentials say everything is fine.... :(:(
- v-janeyg-msft
Hi, Niki
You can try to disable the option, but I'm afraid it won't help:
If this issue is very important, I suggest you open a support ticket, there will be someone responsible for testing and investigating your issue.
Best Regards
Janey Guo
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.