dsccommunity / dsccommunity/SqlServerDsc

SqlSetup: When setup.exe fails it does not show the error message

Open
#406 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Details of the scenario you try and problem that is occurring:
When setup.exe fails it does not show the error message normally printed to the console when running setup.exe manually. See example below. In this particular case neither was there a summary.txt (what I could find at least).

I think

In the below example it did not find the SQL2016-SYSDATA cluster shared disk which was referenced in INSTALLSQLDATADIR.

The following error occurred:
The volume that contains SQL Server data directory G:\MSSQL\Data\MSSQL12.SQL2014\MSSQL\DATA does not belong to the cluster group.

Error result: -2061893582
Result facility code: 1306
Result error code: 50

Please review the summary.txt log for further details
Microsoft (R) SQL Server 2014 12.00.4100.01

Copyright (c) Microsoft Corporation.  All rights reserved.

The DSC configuration that is using the resource (as detailed as possible):
The command line:
./setup.exe /FAILOVERCLUSTERIPADDRESSES="IPv4;192.168.0.10;Cluster Network 1;255.255.255.0" /FEATURES=SQLENGINE,SSMS,ADV_SSMS /SQLUSERDBDIR="E:\MSSQL\Data" /QUIET="True" /SQLTEMPDBLOGDIR="H:\MSSQL\Temp" /AGTSVCACCOUNT="COMPANY\svcsql" /SQLBACKUPDIR="I:\MSSQL\Backup" /ACTION="InstallFailoverCluster" /FAILOVERCLUSTERDISKS="SQL2016-BACKUP" "SQL2016-DATA" "SQL2016-LOG" "SQL2016-TEMPDB" /INSTALLSHAREDDIR="C:\Program Files\Microsoft SQL Server" /FAILOVERCLUSTERNETWORKNAME="TESTCLU01A" /SQLSVCPASSWORD="password" /INSTALLSHAREDWOWDIR="C:\Program Files (x86)\Microsoft SQL Server" /INSTALLSQLDATADIR="G:\MSSQL\Data" /SQLTEMPDBDIR="H:\MSSQL\Temp" /SQLCOLLATION="Finnish_Swedish_CI_AS" /SKIPRULES="Cluster_VerifyForErrors" /UPDATEENABLED="False" /SQLUSERDBLOGDIR="F:\MSSQL\Log" /INSTANCENAME="SQL2014" /INSTANCEDIR="C:\Program Files\Microsoft SQL Server" /IACCEPTSQLSERVERLICENSETERMS="True" /FAILOVERCLUSTERGROUP="TESTCLU01A" /AGTSVCPASSWORD="password" /SQLSYSADMINACCOUNTS="COMPANY\sqladm" "COMPANY\sqladm" "COMPANY\SQL Administrators" /SQLSVCACCOUNT="COMPANY\svcsql"

Version of the Operating System, SQL Server and PowerShell the DSC Target Node is running:
WIndows Server 2016, SQL Server 2014 and PowerShell 5.0

Version of the DSC module you're using, or 'dev' if you're using current dev branch:
Dev

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

The payload identifies setup.exe and the SQL Server DSC configuration, but no repository file or test. Start by tracing where the resource invokes setup.exe and how failures are handled, then reproduce the supplied failover-cluster command. Done means the setup failure message is surfaced instead of hidden, with the existing log behavior understood.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.