reznet
commented
5 years ago It looks like the problem is related to the LCM. I tried running Invoke-DscResource and it also failed:
PS C:\Users\wieva\source\xPackageDebugging> Invoke-DscResource -Name xPackage -ModuleName xPSDesiredStateConfiguration -Method Test -Property @{Path="C:\installers\NDP461-KB3102436-x86-x64-AllOS-ENU.exe"; Name="";ProductId=""}
WARNING: [JEFFELAPTOP]: [DSCEngine] Warning LCM is in Debug 'ResourceScriptBreakAll' mode.
Resource script processing will be stopped to wait for PowerShell script debugger to attach.
WARNING: [JEFFELAPTOP]: [[xPackage]DirectResourceAccess] Resource is waiting for PowerShell
script debugger to attach. Use the following commands to begin debugging this resource script:
Enter-PSSession -ComputerName JEFFELAPTOP -Credential <credentials>
Enter-PSHostProcess -Id 3424 -AppDomainName DscPsPluginWkr_AppDomain
Debug-Runspace -Id 4
PowerShell DSC resource MSFT_xPackageResource failed to execute Test-TargetResource functionality with error message:
Object reference not set to an instance of an object.
+ CategoryInfo : InvalidOperation: (root/Microsoft/...gurationManager:String) [], CimException
+ FullyQualifiedErrorId : ProviderOperationExecutionFailure
+ PSComputerName : localhostbut when I applied an LCM configuration that set Refresh to Disabled:
[DSCLocalConfigurationManager()]
configuration LCMConfig
{
Node localhost
{
Settings
{
RefreshMode = 'Disabled'
}
}
}I was able to successfully use Invoke-DscResource:
PS C:\Users\wieva\source\xPackageDebugging> Invoke-DscResource -Name xPackage -ModuleName xPSDesiredStateConfiguration -Method Test -Property @{Path="C:\installers\NDP461-KB3102436-x86-x64-AllOS-ENU.exe"; Name="";ProductId=""}
InDesiredState
--------------
FalseIt's not clear yet how this issue is specific to the xPackage resource, since it did not happen with xEnvironment.
JustinGrote
mhendric
Details of the scenario you tried and the problem that is occurring
I am trying to install an exe installer using the xPackage resource. I'm pretty sure it once worked on my machine (and we have been using xPackage successfully in our automation), but something broke and I've been unable to explain what. I extracted Test-TargetResource from the module and ran it manually and it did not fail, so it seems something between DSC and the module is introducing the error. I've tried debugging in PowerShell ISE but am able to step through my configuration script but not into the module. I've already tried rebooting, reinstalling the module, but nothing has helped. I've also verified that the module isn't completely broken by successfully testing the xEnvironment resource.
I've set the DscDebug mode to BreakAll, but it doesn't seem to have any effect. Even though the output says it is waiting for a debugger, the script continues to run, displays the error, and exits. I've tried this in both the console and in PowerShell ISE.
What can I try next to troubleshoot this issue?
Verbose logs showing the problem
` PS C:\WINDOWS\system32> C:\Users\wieva\source\xPackageDebugging\config.ps1
`
Suggested solution to the issue
The DSC configuration that is used to reproduce the issue (as detailed as possible)
The operating system the target node is running
OsName : Microsoft Windows 10 Enterprise OsOperatingSystemSKU : EnterpriseEdition OsArchitecture : 64-bit WindowsVersion : 1903 WindowsBuildLabEx : 18362.1.amd64fre.19h1_release.190318-1202 OsLanguage : en-US OsMuiLanguages : {en-US}
Version and build of PowerShell the target node is running
Name Value
PSVersion 5.1.18362.145
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.18362.145
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
Version of the DSC module that was used ('dev' if using current dev branch)
8.8.0.0