Windows User Password policy requirements Error
Error:
[---------------------- CommerceEngine-Pre_EnsureLocalUser : EnsureLocalUser -----------------------------------------]
The user account does not exist ... creating user 'SC1RuntimeUser'.
Creating SC1RuntimeUser
Error: System.Runtime.InteropServices.COMException
The password does not meet the password policy requirements. Check the minimum password length, password complexity
and password history requirements.
Install-SitecoreConfiguration : Exception calling "SetInfo" with "0" argument(s): "The password does not meet the
password policy requirements. Check the minimum password length, password complexity and password history requirements.
"
At C:\deploy\Sitecore.Commerce.WDP.2019.07-4.0.165\SIF.Sitecore.Commerce.3.0.28\My-SC9-XC-Deploy-Sitecore-Commerce -
latest.ps1:93 char:1
+ Install-SitecoreConfiguration @params -Verbose *>&1 | Tee-Object "$PS ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Install-SitecoreConfiguration
[TIME] 00:00:35
Invoke-EnsureLocalUserTask : Exception calling "SetInfo" with "0" argument(s): "The password does not meet the
password policy requirements. Check the minimum password length, password complexity and password history requirements.
"
At C:\Program
Files\WindowsPowerShell\Modules\SitecoreInstallFramework\2.1.0\Public\Install-SitecoreConfiguration.ps1:641 char:25
+ & $entry.Task.Command @paramSet | Out-Default
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Invoke-EnsureLocalUserTask
Solution:
Since i used a machine (VM in my case) that had a minimum password length, complexity for user creation , had to modify my deploy script UserPassword param to include a password that satisfied the requirement (e.g., the password actually added to the script variable would have been 5 chars but the policy might require 12 chars - at least one small case, upper case, special char, numeric etc.)
[---------------------- CommerceEngine-Pre_EnsureLocalUser : EnsureLocalUser -----------------------------------------]
The user account does not exist ... creating user 'SC1RuntimeUser'.
Creating SC1RuntimeUser
Error: System.Runtime.InteropServices.COMException
The password does not meet the password policy requirements. Check the minimum password length, password complexity
and password history requirements.
Install-SitecoreConfiguration : Exception calling "SetInfo" with "0" argument(s): "The password does not meet the
password policy requirements. Check the minimum password length, password complexity and password history requirements.
"
At C:\deploy\Sitecore.Commerce.WDP.2019.07-4.0.165\SIF.Sitecore.Commerce.3.0.28\My-SC9-XC-Deploy-Sitecore-Commerce -
latest.ps1:93 char:1
+ Install-SitecoreConfiguration @params -Verbose *>&1 | Tee-Object "$PS ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Install-SitecoreConfiguration
[TIME] 00:00:35
Invoke-EnsureLocalUserTask : Exception calling "SetInfo" with "0" argument(s): "The password does not meet the
password policy requirements. Check the minimum password length, password complexity and password history requirements.
"
At C:\Program
Files\WindowsPowerShell\Modules\SitecoreInstallFramework\2.1.0\Public\Install-SitecoreConfiguration.ps1:641 char:25
+ & $entry.Task.Command @paramSet | Out-Default
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Invoke-EnsureLocalUserTask
Solution:
Since i used a machine (VM in my case) that had a minimum password length, complexity for user creation , had to modify my deploy script UserPassword param to include a password that satisfied the requirement (e.g., the password actually added to the script variable would have been 5 chars but the policy might require 12 chars - at least one small case, upper case, special char, numeric etc.)
Comments
Post a Comment