WebAdministrationDsc icon indicating copy to clipboard operation
WebAdministrationDsc copied to clipboard

xWebsite throws error using net.tcp/net.pipe

Open virtrixke opened this issue 8 years ago • 4 comments

Hi everybody,

I'm currently using the following code (where servicetype and environment are Test and DVLP for example):

xWebsite "Create-Site${ServiceType}${Environment}"
        {
            PhysicalPath = "C:\inetpub\${ServiceType}.${Environment}"
            State = "Started"
            Ensure = "Present"
            ApplicationPool = "${ServiceType}.${Environment}"
            Name = "${ServiceType}.${Environment}"
            BindingInfo     = @(
                        MSFT_xWebBindingInformation 
                        {
                            Protocol = 'net.tcp'
                            BindingInformation = "808:*"
                        }
                        MSFT_xWebBindingInformation 
                        {
                            Protocol = 'net.pipe'
                            BindingInformation = "*"
                        }                        
                    )                                      
                    
            PreloadEnabled = $true
            DependsOn = "[xWebAppPool]New-AppPool${ServiceType}${Environment}" 
        }

The check always fails with the error: PowerShell DSC resource MSFT_xWebsite failed to execute Set-TargetResource functionality with error message: Failure to successfully set the state of the website "Test.DVLP". Error: "The object identifier does not represent a valid object. (Exception from HRESULT: 0x800710D8)".

I suspect it has something to do with the net.tcp/net.pipe bindinginfo...

virtrixke avatar Mar 13 '17 15:03 virtrixke

Any progress on this issue? Same over here...

rvf148 avatar Feb 09 '18 16:02 rvf148

This sounds like a bug. I think an integration test need to be created for this issue to test this scenario.

johlju avatar Apr 26 '18 13:04 johlju

FYI. found this bug as I am using this provider. This error seems to appear when a appool that doesnt exist is selected. In my case I had a typo in the app pool name in the app pool resource

JakobGSvendsen avatar Mar 30 '20 18:03 JakobGSvendsen