The error mentions that the request was unauthorized which indicates the user identity that Indicium is running as does not have access to the SSRS reporting server.If you are running Indicium on IIS this corresponds to the application pool user that was set.Have a look at https://learn.microsoft.com/en-us/sql/reporting-services/security/authentication-with-the-report-server?view=sql-server-ver15#authentication-types for some more information about SSRS server authentication types.By default it is set to RSWindowsNegotiate and RSWindowsNTLM which is why the current user of Indicium is used. RSWindowsKerberos would probably work as well but requires more setup. The other two (RSWindowsBasic/Custom) are currently not supported.Another thing to consider is that credentials for data sources might be overwritten by the user credentials set in Indicium’s MetaSourceConnection or via the pool user credentials that can be set per application since 2023.1: https://docs.thinkwisesoftware.com/blog
@kensonlatchmansing Sorry it took a while to find some time to try and test the scenario you've described above.Unfortunately, I also could not find a way to use the pool user of an App Service Indicium in combination with a SSRS server. A Power BI server could probably make it work when using a managed identity on the App Service but I did not test this since the Thinkwise Platform currently does not support Power BI as a report type.Setting the MetaSourceConnection:Username/Userpassword options instead also will not work since the code only seems to override the credentials on each dataset in the report and not the credentials used to authenticate with the SSRS server itself.So, for the described scenario, the platform would probably need to support configuring a location + credentials of a SSRS server in the model itself. Like how file storage locations etc. can be provided.This is just a thought since I don't know how complicated the reports are but if they only differ in styling b
Dear Mark,To explicitly prevent an Indicium from taking on background work as specified by the IAM in connects to, such as system flows, you can set the Agent setting in the appsettings to false as described here:https://docs.thinkwisesoftware.com/docs/deployment/indicium_configuration#disable-background-operations{ "Agent": { // Skip registering this Indicium instance as an agent on IAM. // Also disables adding all agent related services such as the scheduled system flow runner. "Enabled": false }}Do note that only one Indicium at a time will be receiving system flow schedules from IAM. So if you, for example, disabled the agent service on the Indicium that the Universal GUI connects to and then have two others that could both process system flows only one of them will be doing so. Of course if that Indicium were to go down somehow the other one would then take over.I hope this answers your question.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.