Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Name will not take ".Net6 Core ", Net6 Core works but want the "." #615

Open
bbaak opened this issue Jul 28, 2022 · 1 comment
Open

Name will not take ".Net6 Core ", Net6 Core works but want the "." #615

bbaak opened this issue Jul 28, 2022 · 1 comment
Labels
needs more information The issue needs more information from the author or the community.

Comments

@bbaak
Copy link

bbaak commented Jul 28, 2022

Problem description

Migrating from an 2012 R2 server with all the pipelines already built, and want to use the same app pool names. We have a ".Net6 Core" app pool and XWebAppPool will not take the "." in the value.

Verbose logs

PowerShell DSC resource MSFT_xWebAppPool  failed to execute Set-TargetResource functionality with error message: The
running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop:
Invalid application pool name

    + CategoryInfo          : InvalidOperation: (:) [], CimException
    + FullyQualifiedErrorId : ProviderOperationExecutionFailure
    + PSComputerName        : localhost

DSC configuration

Configuration BuildConfigureIIS_DMZ {
    Import-DscResource –ModuleName 'PSDesiredStateConfiguration'
    Import-DscResource -ModuleName 'xWebAdministration'
    Import-DscResource -ModuleName 'XSmbShare'
    Import-DscResource -ModuleName 'xpsdesiredStateConfiguration'


node "localhost" 
    {

        xWebAppPool net6Core {
            Name = "Net6 Core"
            Ensure = "Present"
            State = "started"
            managedRuntimeVersion = ""
            enable32BitAppOnWin64 = $false
            managedPipelineMode = "Integrated"
        }

}

Suggested solution

I don't unfortunately.

Operating system the target node is running

OsName               : Microsoft Windows Server 2019 Datacenter
OsOperatingSystemSKU : DatacenterServerEdition
OsArchitecture       : 64-bit
WindowsVersion       : 1809
WindowsBuildLabEx    : 17763.1.amd64fre.rs5_release.180914-1434
OsLanguage           : en-US
OsMuiLanguages       : {en-US}

PowerShell version and build the target node is running

Azure Automation DSC

Name                           Value
----                           -----
PSVersion                      5.1.17763.2931
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17763.2931
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

WebAdministrationDsc version

3.3.0

In Azure.
@johlju
Copy link
Member

johlju commented Jul 31, 2022

It says here it should work, but does not specify that it allow to start with a period.
https://docs.microsoft.com/en-us/IIS/wmi-provider/applicationpool-class

Guessing you have tried adding through GUI and it work?

Have you confirmed that it works using the command New-WebAppPool ?

@johlju johlju added the needs more information The issue needs more information from the author or the community. label Aug 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs more information The issue needs more information from the author or the community.
Projects
None yet
Development

No branches or pull requests

2 participants