topic Re: Report Configuration Bugs in Report Server

Report Configuration Bugs

kungfu71186 — Thu, 09 May 2019 05:09:29 GMT

I am trying to develop a DSC resource for PowerBI and ran accross a few bugs so far.

1. If i configure everything and then go back and try and change the service account, I get an empty user name for integrated user and I can't connect using the SQL user if specified as well.

Even if that is fixed, I also noticed this code:

rc = this.GenerateAndApplyRightsHelper(connectionDialog.BuildConnectionString(), (string) null, false, account, true); which means it's also a local server and it's aways a windows user. Not sure if it matters when generating the user rights script though.

Edit:

I know why this is like this now, but still don't know why it's passing null for the database.

2. Had another bug where Service Account is the only available option. Can't replicate, but when I do, I'll post here.

Re: Report Configuration Bugs

ITGeek555 — Thu, 09 May 2019 00:39:05 GMT

Does the Power BI Report Server (PBIRS) run successfully after configuring everything?

Without knowing what your DSC is actually doing to configure the Service Account it is hard to provide assistance.

I have used the Reporting Services WMI provider successfully to script the installation and configuration of PBIRS. Perhaps you might find an answer there

Be aware that the above documentation is quite poor in terms of usable examples.

Re: Report Configuration Bugs

kungfu71186 — Thu, 09 May 2019 05:07:47 GMT

I'd have to test that scenario, but I doubt it would if the permissions weren't there already.

This isn't in DSC, this is in the config tool that it's doing this.