SqlServerDsc/SqlPermission mad error without any info

[ognif]

With an SQLServer2022 installation I try to set permissions with dscV3. The script looks like:

{
    "metadata": {
        "description": "SQL Server 2022 Installation on V-MSSQL177.xxx",
        "generated": "2025-11-04T15:42:28Z",
        "author": "Ansible DSC Automation",
        "target": "V-MSSQL177.xxx",
        "instance": "MSSQLSERVER"
    },
    "resources": [
		{
		  "type": "SqlServerDsc/SqlSetup",
		  "name": "InstallSQLServer2022",
		  "properties": {
			"InstanceName": "MSSQLSERVER",
			"Features": "SQLENGINE,FULLTEXT",
			"SourcePath": "C:\\Temp\\SQLInst",
			"SQLSysAdminAccounts": ["xxx", "xxx"],
			"InstallSharedDir": "C:\\Program Files\\Microsoft SQL Server",
			"InstallSharedWOWDir": "C:\\Program Files (x86)\\Microsoft SQL Server",
			"InstanceDir": "F:\\SQLSYSTEM\\Microsoft SQL Server",
			"InstallSQLDataDir": "S:\\MSSQL\\Data",
			"SQLUserDBDir": "D:\\MSSQL\\Data",
			"SQLUserDBLogDir": "L:\\MSSQL\\Data",
			"SQLTempDBDir": "T:\\MSSQL\\Data",
			"SQLTempDBLogDir": "T:\\MSSQL\\Data",
			"SQLBackupDir": "E:\\MSSQL\\Backup",
			"SecurityMode": "SQL",
			"SAPwd": {
			  "userName": "sa",
			  "password": "xxx"
			},
			"SQLSvcAccount": {
			  "userName": "xxx",
			  "password": "xxx"
			},
			"AgtSvcAccount":  {
			  "userName": "xxx",
			  "password": "xxx"
			},			
			"BrowserSvcStartupType": "Automatic",
			"UpdateEnabled": "True",
			"ForceReboot": false,
			"SuppressReboot": true
		  }
		},			
		{
		  "type": "SqlServerDsc/SqlPermission",
		  "name": "GrantSystemPermissions",
		  "properties": {
			"ServerName": "V-MSSQL177.xxx",
			"InstanceName": "MSSQLSERVER",
			"Name": "NT AUTHORITY\\SYSTEM",
			"Credential": {
			  "userName": "mSQLDSCinstall",
			  "password": "xxx"
			},
			"Permission": [
			  {
				"State": "Grant",
				"Permission": [
				  "AlterAnyAvailabilityGroup",
				  "ViewServerState",
				  "ConnectSql"
				]
			  },
			  {
				"State": "GrantWithGrant",
				"Permission": []
			  },
			  {
				"State": "Deny",
				"Permission": []
			  }
			]
		  },
		  "dependsOn": ["[resourceId('SqlServerDsc/SqlSetup', 'InstallSQLServer2022')]"
		  ]
		},

		
    ],
    "$schema": "https://raw.githubusercontent.com/PowerShell/DSC/main/schemas/v3.1/config/document.json"
}

But with this error I just get an zero info error:
2025-11-12T20:57:37.285318Z ERROR Error: JSON: expected value at line 1 column 1
I tried to get more infos with verbose but nothing. Just this line. Anybody know this error?

I used SqlServerDsc 17.3.0-preview0018 and also 17.2.0 both with the same error.

[Gijsreyn]

Can you dump in the -t trace in front of dsc -l trace config <operation> and paste it here? I think this is going to relate to issue: #833.

[Gijsreyn]

@johlju - do you mind stepping in here also, as you've worked with SqlServerDsc before using the dsc.exe if I'm not mistkaen?

[johlju]

I have not used DSCv3 other than trying to run integration tests, which I put on hold until the stream issue for class-based resources has been resolved. But that is the error you will get due to the stream issue. As suggested, run Invoke-DscResource to see if there are any error, warning or verbose messages in the output, any of those will most likely fail in that error. Here is an example how to run in from command line (in Windows PowerShell): https://github.com/dsccommunity/SqlServerDsc/blob/ef9ae5f6f57180ab4c6733b12784172ceaadf811/source/Classes/020.SqlPermission.ps1#L100

[ognif]

If I try this from @johlju I just get the output

Powershell 5

Failed to create an object of PowerShell class SqlPermission.
    + CategoryInfo          : InvalidOperation: (root/Microsoft/...gurationManager:String) [], CimException
    + FullyQualifiedErrorId : InstantiatePSClassObjectFailed
    + PSComputerName        : localhost

Powershell 7:
Invoke-DscResource: Failed to serialize properties into CimInstance.

I adjusted the sample from the name website with my Instance data. Also tried with localhost and real servername.

Anyway, as I understand it, this is a known bug in DSCv3?

[Gijsreyn]

At least the stream issue is.

[ognif]

Any idea when this is fixed. Maybe there is a pre-release available?

[johlju]

@ognif

I just get the output
Failed to create an object of PowerShell class SqlPermission.

This sounds like the LCM can't run/use the resource. I would look into that first to make sure the resource works in your environment, then switch to DSCv3. Note that Invoke-DscResource uses LCM and it only works in Windows PowerShell, not PowerShell 7. When you have it running successfully with LCM then you have configured all the prereq correctly, then everything should be there to run it in DSCv3 (although in theory, it is a complex resource that never have been tested with DSCv3). Are you running another resource in DSCv3 and it is only this SqlPermission that is an issue?

Anyway, as I understand it, this is a known bug in DSCv3?

As @Gijsreyn said, the stream issue is (there is an open issue that tracks it), but that said you should be able to workaround it by modifying any line that output either a warning or verbose message (normally no verbose messages should be output though). But we still don't know if this is due to the stream issue, it can be that you get an error that are not surfacing due to the stream issue, and by making sure it runs in LCM you could possible find that cause.

[ognif]

I only mentioned PowerShell 7 as a precaution. As far as I understand, Invoke-DscResource is only for PowerShell 5. But as I wrote, even PowerShell 5 doesn't work. The machine has a DSC1/2 configuration because it was previously configured with DSCv1/2. DSCv3 has since been added.

What I find strange is that I get the same output for both "SqlAgentAlert" and "SqlPermission," always ERROR: JSON: expected value at line 1 column 1. Neither of these are separate DSCResources but classes within "SqlServerDsc.psm1." The DSCResources have all worked fine so far.

I also tried using the commontasks module, hoping it would catch any problems, but unfortunately, that didn't work either.