You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
DSC configuration
Suggested solution
I don't unfortunately.
Operating system the target node is running
PowerShell version and build the target node is running
WebAdministrationDsc version
The text was updated successfully, but these errors were encountered: