dsccommunity / dsccommunity/SqlServerDsc

SqlServiceAccount: Fails to change account for SSRS 2016

Open
#1,259 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug help wanted
Dominant language
PowerShell
Stars
385
Forks
224
PR merge metrics
No merged PRs in 30d

Description

Problem:

SqlServiceAccount does not work for SSRS 2016, it produced an internal error.

Description

We have successfully changed the service account for Database Services (DatabaseEngine) using SqlServiceAccount however i get an internal error when i try to set the service account for SSRS 2016.

Steps to produce error

SSRS 2016 EE on Windows Server 2016

$cred = Get-Credential -UserName "testdomain.local\testaccount" -Message "Password please"

Invoke-DSCResource -Module SqlServerDsc -Name SqlServiceAccount -Method Set -Property @{
serverName='TestServer''
InstanceName='TESTSSRS'
ServiceType='ReportingServices'
ServiceAccount=$cred
}

Error Produced

An internal error occurred.
+ CategoryInfo : NotSpecified: (root/Microsoft/...gurationManager:String) [], CimException
+ FullyQualifiedErrorId : HRESULT 0x8007054f
+ PSComputerName : localhost

Exploration

I have debugged the code and see that it errors out at SetServiceAccount. ( I also tried SetServiceAccount in standard powershell which also doesn't work for SSRS, but again works fine for database engine)

It looks like SetServiceAccount is not valid for reporting services and we should use SetWindowsServiceIdentity, a method of MSReportServer_ConfigurationSetting.

Has anyone successfully used SqlServiceAccount for SSRS 2016.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the SqlServiceAccount resource and reproduce the SSRS 2016 case using the shown Invoke-DSCResource command. Compare the failing SetServiceAccount path with the mentioned SetWindowsServiceIdentity method on MSReportServer_ConfigurationSetting. Done means changing the Reporting Services account succeeds without the internal error while the existing DatabaseEngine behavior remains intact.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.