dsccommunity / dsccommunity/SqlServerDsc

SqlSetup: does not work repliably, "full-text" service does not use the service account even though it is provided as a parameter

Open
#152 7 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

I have been trying to get this to work but i get this error every time:


VERBOSE: [myServer]:                            [[xSQLServerSetup]installSQL] Test-TargetResource returned false after calling set. | ErrorType: MSFT_xSQLServerSetup.TestFailedAfterSet
VERBOSE: [myServer]: LCM:  [ End    Set      ]  [[xSQLServerSetup]installSQL]  in 63.3120 seconds.
PowerShell DSC resource MSFT_xSQLServerSetup  failed to execute Set-TargetResource functionality with error message: Test-TargetResource returned false after calling set. 
    + CategoryInfo          : InvalidOperation: (:) [], CimException
    + FullyQualifiedErrorId : ProviderOperationExecutionFailure
    + PSComputerName        : localhost

i check program files and dont see an "sql server" folder there. I check the %temp% folder nothing there as well.

The DSC logs are not helpful either:

Job {1983FE4E-8BC6-11E6-80C4-000D3A20899A} : 
MIResult: 1
Error Message: PowerShell DSC resource MSFT_xSQLServerSetup  failed to execute Set-TargetResource functionality with error message: Test-TargetResource returned false after calling set. 
Message ID: ProviderOperationExecutionFailure
Error Category: 7
Error Code: 1
Error Type: MI
Job {1983FE4E-8BC6-11E6-80C4-000D3A20899A} : 
Message Test-TargetResource returned false after calling set. 
HResult -2146233087 
StackTrack    at System.Management.Automation.Interpreter.ThrowInstruction.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)

so not sure how to troubleshoot this thing.

Also it seems the path to the setup files has been hardcoded so we have to have the setup files in a folder called "sources".For people like me who use ISO's this forces us to re-package the iso with the sources folder.

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 xSQLServerSetup resource, especially the installSQL flow and its Test-TargetResource and Set-TargetResource behavior. Reproduce the failure with the supplied service account and setup path, then verify that installation succeeds and that setup files do not require a hardcoded "sources" directory.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell, sql
Domain
databases, devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.