"Resource name 'WindowsPackageCab' is already being used by another Resource or Configuration." about psdscresources HOT 7 CLOSED

@csharmath Odd. I can't get it to reproduce either. The only difference I have here is that I didn't import xWebAdministration because I don't currently have that module on my test VM. Can you try separating the two module imports into different lines?
Like this:

Import-DscResource -ModuleName xWebAdministration
Import-DscResource -ModuleName PSDesiredStateConfiguration

I have seen this error before but it only came up when this code was written:

Import-DscResource -ModuleName PSDscResources, PSDesiredStateConfiguration

And the fix for that is to separate the imports into two lines.

from psdscresources.

Hey, sorry for the slow response.

Seems like I can't reproduce it either now.
Looking at patching, I can see lots of hotfixes installed on that server since then.
When I've tried it was a fresh build from a not so fresh image, so it can very well be that some of the hotfix fixed it then.
Looking at the patches, the first one is from 3/14/2016 so thats almost a years worth of patches which is a lot.
WMF 5.1 was manually installed.

I guess the lesson learned for me is to double check that the patching is done before I start working on new builds / get the base image updated.

If someone landed here from a google search: patch & retry :)
Thanks @kwirkykat & @mbreakey3 for taking a look as well!

from psdscresources.

I was able to work around this by adding a try/catch swallow as shown in the gist
https://gist.github.com/csharmath/f2918d4f0dc7e14bdff1fa579b49ebbb#file-psdesiredstateconfiguration-psm1-L2108

But I was not yet able to figure out the root cause and this does not seem like the best way to go of course.

Any ideas on how to debug this ?

Thanks

from psdscresources.

Is this only coming up on 2012 R2? Sorry for the late response, I was trying to repro your issue but it wasn't coming up on my machine (2016 nor 2012 R2). It looks like it could be an issue with PSDesiredStateConfiguration rather than PSDscResources. Have you tried importing PSDesiredStateConfiguration first and then PSDscResources to see if the issue still comes up?

from psdscresources.

Yes, Server 2012R2.
I guess it's environment specific, so some combination of settings/installed modules, env vars, etc. not sure yet what exactly, but will try to remove things / set them to defaults...

from psdscresources.

Have you tried running Get-Module -ListAvailable to see if there's any duplicates listed there?

from psdscresources.

@csharmath Odd. I can't get it to reproduce either. The only difference I have here is that I didn't import xWebAdministration because I don't currently have that module on my test VM. Can you try separating the two module imports into different lines?
Like this:

Import-DscResource -ModuleName xWebAdministration
Import-DscResource -ModuleName PSDesiredStateConfiguration

I have seen this error before but it only came up when this code was written:

Import-DscResource -ModuleName PSDscResources, PSDesiredStateConfiguration

And the fix for that is to separate the imports into two lines.

I had the same error using an entirely different set of modules.
I was able to solve it by separating import-dscresource statements.

from psdscresources.