You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$result=get-dbastartupparmaeter-sqlinstance $VNN-credential $CRED# please include variable values (redacted or fake if needed) for reference
Please confirm that you are running the most recent version of dbatools
2.1.14
Other details or mentions
This behavior only happens with FCIs.
I am running this against a two-node multi-subnet FCI. I have confirmed that the FCI is online and in good state. I'm pulling the master data and log paths for some code that moves the system dbs. The script that performs the work randomly fails with "cannot call a method on a null object" and in rarer cases "there is no TraceFlags property on the object".
I ran the same code successfully against a half-dozen standalone instances last week and all returned the expected result set, every time.
The FCI behavior is unpredictable, and varies inconsistently with whether I pass the 'short' name, the FQDN, etc. Sometimes it returns an array where the first object is null and the rest are correct; sometimes it returns an array of three objects, sometimes it returns an array of up to eight objects, and sometimes it returns a single object. I assume it is iterating over multiple variants of the FCI name and over each cluster node, but I cannot put any rhyme or reason to it. Nor can I figure out why sometimes it returns exactly what it ought, and then fails several times in a row, with different results.
What PowerShell host was used when producing this error
Windows PowerShell (powershell.exe)
PowerShell Host Version
5.1.19041.4780
SQL Server Edition and Build number
Microsoft SQL Server 2019 (RTM) - 15.0.2000.5 (X64) Sep 24 2019 13:48:23 Copyright (C) 2019 Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2022 Datacenter 10.0 (Build 20348: ) (Hypervisor)
.NET Framework Version
.NET Framework 4.8.9261.0
The text was updated successfully, but these errors were encountered:
Verified issue does not already exist?
No, I did not search
What error did you receive?
Steps to Reproduce
or
Please confirm that you are running the most recent version of dbatools
2.1.14
Other details or mentions
This behavior only happens with FCIs.
I am running this against a two-node multi-subnet FCI. I have confirmed that the FCI is online and in good state. I'm pulling the master data and log paths for some code that moves the system dbs. The script that performs the work randomly fails with "cannot call a method on a null object" and in rarer cases "there is no TraceFlags property on the object".
I ran the same code successfully against a half-dozen standalone instances last week and all returned the expected result set, every time.
The FCI behavior is unpredictable, and varies inconsistently with whether I pass the 'short' name, the FQDN, etc. Sometimes it returns an array where the first object is null and the rest are correct; sometimes it returns an array of three objects, sometimes it returns an array of up to eight objects, and sometimes it returns a single object. I assume it is iterating over multiple variants of the FCI name and over each cluster node, but I cannot put any rhyme or reason to it. Nor can I figure out why sometimes it returns exactly what it ought, and then fails several times in a row, with different results.
What PowerShell host was used when producing this error
Windows PowerShell (powershell.exe)
PowerShell Host Version
5.1.19041.4780
SQL Server Edition and Build number
Microsoft SQL Server 2019 (RTM) - 15.0.2000.5 (X64) Sep 24 2019 13:48:23 Copyright (C) 2019 Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2022 Datacenter 10.0 (Build 20348: ) (Hypervisor)
.NET Framework Version
.NET Framework 4.8.9261.0
The text was updated successfully, but these errors were encountered: