COM error: Microsoft.PowerBI.ReportServer.ASEngineManagedRoot, No credentials were found for the ds

[Niki]

Hi, really need help, our full operation is depending on our reports....

end of 2020 we had this error on dreport refreshes. We have no special sources everything is via import connected to SQL server database. and suddenly reports were not refreshing. The issue was luckily solved by the January update and now since monday the issue is back.

credentials are stored, re-uploading does not work, refreshing from de pbix gives no errors and also the exact same report do not give any issues on our testserver. (which had the same version as production)

This is the error on refresh:

[0] -1056505856: COM error: Microsoft.PowerBI.ReportServer.ASEngineManagedRoot, No credentials were found for the datasource.

KR

Niki

[gsprague · Accepted solution]

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

[a4peterson]

This worked for us, and one of our error messages was:  "Microsoft.PowerBI.ReportServer.ASEngineManagedRoot, No credentials were found for the datasource."

And, we did not have to restart the report server service.

[MHaggerty_DOL]

Scheduled refresh not working with latest version:

Power BI Report Server
Version 1.10.7698.27886

Power BI Desktop
Version 2.88.1382.0 64-bit (January 2021)

From RSPowerBI log:
2021-03-19 13:00:28.4763|ERROR|66|Error Processing Data Model Refresh: SessionId: e9647ff5-b849-4f21-bf87-9d1a0c8e0b94, Status: Error Failed to refresh the model, Exception Microsoft.AnalysisServices.OperationException: Failed to save modifications to the server. Error returned: 'COM error: Microsoft.PowerBI.ReportServer.ASEngineManagedRoot, No credentials were found for the datasource.
COM error: Microsoft.PowerBI.ReportServer.ASEngineManagedRoot, No credentials were found for the datasource.
'.
at Microsoft.AnalysisServices.Tabular.Model.SaveChangesImpl(SaveOptions options)
at Microsoft.PowerBI.ReportServer.AsServer.TOMWrapper.RefreshModel(Database database)
at Microsoft.PowerBI.ReportServer.AsServer.AnalysisServicesServer.RefreshDatabase(String databaseName, IEnumerable`1 dataSources, IEnumerable`1 parameters, String clientSessionId)
at Microsoft.PowerBI.ReportServer.WebHost.EventHandler.AnalysisServicesDataRefresh.RefreshDatabase(AsDatabaseInfo asDatabaseInfo)
at Microsoft.PowerBI.ReportServer.WebHost.EventHandler.DataRefreshScope.<>c__DisplayClass34_0.<ExecuteActionWithLogging>b__0()
at Microsoft.PowerBI.ReportServer.WebHost.EventHandler.DataRefreshScope.<ExecuteFuncWithLogging>d__33`1.MoveNext()

From ASManagedRoot log:
2021-03-19 13:00:28.0700|TRACE|10|GetV3ConnectionString - dataSourceIds: {"protocol":"file","address":{"path":"\\\\XYZABC\\Deadpool$\\Deadpool_Data_Files\\Adjustments-Old.csv"},"authentication":null,"query":null}; Root activity ID: d2ae1cbb-cfb5-43f2-b3d8-4f52b8bfcf28.
2021-03-19 13:00:28.0700|TRACE|10|GetDatasources - Looking for credentials based on connection string. Root activity ID: d2ae1cbb-cfb5-43f2-b3d8-4f52b8bfcf28.
2021-03-19 13:00:28.0700|INFO|10|Getting data sources in the model for connection string for databaseName = d5151e44-feed-4bc7-90cf-5a4273b99958_-525095226
2021-03-19 13:00:28.0700|TRACE|91|Failed to find a matching datasource for ConnectionString \\XYZABC\Deadpool$\Deadpool_data_files\adjustments-old.csv in database d5151e44-feed-4bc7-90cf-5a4273b99958_-525095226. Available datasources found were DataSourceIdentifier: 2BE5BD0BF91B03EE11B67575DEF9E0206D31F5976C3A12F6B39A09E074530DD7, AuthKind: File, AuthType: Windows, ConnectionString: ????????????????????????????????????????????????????????????,DataSourceIdentifier: 5032E4FD176554754528992B9498094BD725F95BE61AC034FEB3E85B4F26EEE5, AuthKind: File, AuthType: Windows, ConnectionString: ?????????????????????????????????????????????????_??????????,DataSourceIdentifier: 684DA2F197A79C09F8372666E8CDE0347AE5C58695FCA5AE5568710AAF47E78F, AuthKind: File, AuthType: Windows, ConnectionString: ?????????????????????????????????????????????????_??????????????,DataSourceIdentifier: 98828F3672633768B8D6692AB497A043A71919AC77DC4ECE7FAC4975D0120E1A, AuthKind: File, AuthType: Windows, ConnectionString: ????????????????????????????????????????????????????,DataSourceIdentifier: 9984BF017312C7CB377E4D5EC99F6F18AE5FC9F6E16439BD653AC370F5693C9D, AuthKind: File, AuthType: Windows, ConnectionString: ????????????????????????????????????????????????????????????????????????????,DataSourceIdentifier: A6997D6A781D0359AB392B0237FBB1278FBE9396CA3FF18D7D6A61708A0CC51F, AuthKind: File, AuthType: Windows, ConnectionString: ????????????????????????????????????????????????????????,DataSourceIdentifier: A9E998531E1F1CDA6ECAB278DA93B832A6411B7C50B903BF8DDF2D0BE5C346CC, AuthKind: File, AuthType: Windows, ConnectionString: ????????????????????????????????????????????????????????????????,DataSourceIdentifier: CC73019E31E1DC4DB0D3AF1B200407F0792C78B893EDD15412A0D1FF033479ED, AuthKind: File, AuthType: Windows, ConnectionString: ???????????????????????????????????????????-?????????????Î??,DataSourceIdentifier: D4BA434E8E24A332C5699E1CDFC13DB517FF155A0343E84B6AF9589E6B756F40, AuthKind: Folder, AuthType: Windows, ConnectionString: ?????????????????????????????????????????¦??,DataSourceIdentifier: E4203739C56C79D77E4694C1E15C8057EFA906E033D3557F777CB2802C145F42, AuthKind: File, AuthType: Windows, ConnectionString: ????????????????????????????????????????????????????????????????
2021-03-19 13:00:28.0700|TRACE|10|GetDatasources - Data Source Not found, looking for datasource based on path-based hash. Root activity ID: d2ae1cbb-cfb5-43f2-b3d8-4f52b8bfcf28.
2021-03-19 13:00:28.0700|INFO|10|Getting data sources in the model for hashedDataSourceId = FDC4413CB4405094BC897964968779E7B7D05C9113E56F614447D5ADF91030EF and databaseName = d5151e44-feed-4bc7-90cf-5a4273b99958_-525095226
2021-03-19 13:00:28.0700|TRACE|10|GetDatasources - Data Source Not found, looking for legacy full hash. Root activity ID: d2ae1cbb-cfb5-43f2-b3d8-4f52b8bfcf28.
2021-03-19 13:00:28.0700|INFO|10|Getting data sources in the model for hashedDataSourceId = BDC0C1A484D540BA653FD8238F93B5FDCCE0A4CC05E6E766D0EE82DE0DA7CEE5 and databaseName = d5151e44-feed-4bc7-90cf-5a4273b99958_-525095226
2021-03-19 13:00:28.0700|WARN|10|GetDatasources - Unable to find matching datasources with the following datasourceIds: {"protocol":"file","address":{"path":"\\\\XYZABC\\Deadpool$\\Deadpool_Data_Files\\Adjustments-Old.csv"},"authentication":null,"query":null}
2021-03-19 13:00:28.0700|ERROR|10|GetV3ConnectionString - Exception occured while retrieving credentials for data model connection string.System.Exception: No credentials were found for the datasource
at Microsoft.PowerBI.ReportServer.ASEngineManagedRoot.PBIRSConnectionDetailsProvider.GetV3ConnectionString(Guid rootActivityId, String userPrincipalName, String engineConnectionString, String[] datasourceIds, String contextualIdentity, Boolean isDirectQueryExecution, PBIDedicatedProviderType& providerType, String& connectionString)

[v-janeyg-msft]

Hi, @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.

[Niki]

Hi, 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]

Hi @v-janeyg-msft 

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.

Support | Microsoft Power BI

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.

[Niki]

@gsprague , any solution on short term?

it really is a big problem!

[gsprague]

Hi @Niki - Would you be able to provide more details around the error in the logs? In particular:

1. Try turning on verbose logging Troubleshoot scheduled refresh in Power BI Report Server - Power BI | Microsoft Docs
2. After turning on verbose logging, when you try scheduled refresh again, what do the ASEngineManagedRoot logs show?

[Niki]

@gsprague, this is the error log, help me!

[Chuka]

Has this been fixed, experiencing the same issues on Jan 2021 RS version.

[v-janeyg-msft]

Hi, @Niki 

The fastest solution is to open a support ticket, there will be someone responsible for testing and investigating your issue. There is little help on the forum in your issue.

Support | Microsoft Power BI

Best Regards

Janey Guo

[Niki]

@gsprague  yes already on the January version, after installing it the problem was solved, but as of this monday the problem is back.

[gsprague]

Hi @Niki , what version of PBIRS are you on?  If you are not yet on the January 2021 release of PBIRS, could you upgrade and try reuploading? Download Microsoft Power BI Report Server - January 2021 from Official Microsoft Download Center