Job {33B874F7-C1C0-11E4-80C9-F2AAAA00005E} :
This event indicates that failure happens when LCM is processing the configuration. ErrorId is 0x1. ErrorDetail is The SendConfigurationApply function did not succeed… ResourceId is [Package]Java8x86 and SourceInfo is ::33::9::Package. ErrorMessage is PowerShell DSC resource MSFT_PackageResource failed to execute Set-TargetResource functionality with error message: The return code -80 was not expected. Configuration is likely not correct .
Any ideas? I’ve also tried using the argument below but no luck either. The 64-bit version installs just fine.
It’s probably that the installer is doing something that requires an active user profile, which isn’t present when the LCM runs. Either that, or the 32-bit installer doesn’t like being run in a 64-bit process space. There’s not really a way to change either of those things.
Thanks for the reply. I was actually able to finally get this working by extracting the .msi from the executable. If you run the .exe, the msi file is extracted into the AppData\LocalLow\Sun folder. I then used the msi in the DSC configuration and it installed without issues.
And that folder wouldn’t necessarily exist under the LCM, which is why it wasn’t working. You run into that a lot with installers, unfortunately. It’s one reason DSC is a little dicey on client workloads - that comes up a lot more often than on servers. Glad you got it working!