UNSOLVED

t.tsoukas

updated

4 years ago

TT

t.tsoukas

1 Rookie

•

3 Posts

0

5701

December 9th, 2021 04:00

Upgrade failed from WMS 3.3.1 to 3.5

Hello everyone,

Trying to upgrade 3.3.1 to 3.5 produces the following error:

2021-12-7 T17:20:26::Upgrade::2658::Running Action: ConfigureJavaForUpgrade
2021-12-7 T17:20:26::Upgrade::2662::Copy C:\Program Files\DELL\WMS\Archive\jdk-11.0.10\lib\security\cacerts toC:\Program Files\DELL\WMS\OpenJDK-11.0.12\lib\security
2021-12-7 T17:20:31::CustomFunctions::6116::In function createwmsuser
2021-12-7 T17:20:31::CustomFunctions::6127::User Created Successfully: The operation completed successfully.

2021-12-7 T17:20:35::CustomFunctions::6139::Failed to set change password policy
2021-12-7 T17:20:44::Upgrade::598::User creation failed, hence restoring...

This has happened on 2 production servers thus far, both being domain controllers.

Has anyone experienced this?  Please advise.

Thanks,

Ted Tsoukas

 

 

  • 4327

    0

    Posted December 10th, 2021 03:00

    Hey,

    same problem here. Also on a domain controller, same error in log.
    Reverting back the changes after the failed upgrade did not work, so restore from backup to get the 3.3.1 Version working again was necessary.
    I tried to edit the User manually and disabled the password expiration, but then the Setup complains about User already exists.
    At the moment I don't have any more ideas about it.

    Regads,
    Daniel

  • t.tsoukas

    1 Rookie

    •

    3 Posts

    4261

    0

    Posted December 14th, 2021 03:00

    Hi again,

    Same issue when trying 3.5.1 (released yesterday from what I can see.)

    2021-12-14 T13:10:09::Upgrade::2829::Running Action: ConfigureJavaForUpgrade
    2021-12-14 T13:10:09::Upgrade::2833::Copy C:\Program Files\DELL\WMS\Archive\OpenJDK-11.0.12\lib\security\cacerts toC:\Program Files\DELL\WMS\OpenJDK-11.0.12\lib\security
    2021-12-14 T13:10:11::CustomFunctions::5976::szFormattedVersion1: 3.3.1.0
    szFormattedVersion2: 3.5.0.0
    2021-12-14 T13:10:11::CustomFunctions::6118::In function createwmsuser
    2021-12-14 T13:10:12::CustomFunctions::6129::User Created Successfully: The operation completed successfully.

    2021-12-14 T13:10:21::CustomFunctions::6141::Failed to set change password policy
    2021-12-14 T13:10:40::Upgrade::634::User creation failed, hence restoring...

    Please advise, issue still persists on domain controller. Have tried this in 2 DC's, in 2 different environments.

    Thanks,

    Ted Tsoukas

     

     

  • Drewsky25

    1 Rookie

    •

    19 Posts

    •

    9 Points

    4238

    2

    Posted December 14th, 2021 10:00

    I KNOW THE ISSUE!!!!  Just battled as we speak.  It is trying to create a local account during the installer.  If you have a Domain Password Policy applying to this server, it will fail.  Here is the work around.  Throw this server in deny policy for that GPO temporarily.  It will then be able to create the lame local user for that server and use it for all services once going to 3.5.  Then the installer will complete.  Go into the services and stop them, change to a domain service account that has access to the installer and repo share.  Then you can upgrade to 3.5.1 just fine.  Also you can double back and remove the temp GPO deny and delete the local user account that was created.  Hope that helps!

  • kjhkjhjhh

    8 Posts

    4140

    2

    Posted December 15th, 2021 14:00

    This indeed seems not fixable directly on a Domain Controller or someone from Dell needs to read this and fix this issue. What you can however do to mitigate the LOG4J vulnerability is to upgrade to version 3.3.1 and then goto [WMSInstalldir]\Tomcat-9\bin\ and run tomcat9w.exe. Goto tappage Java and add the following option in a new line to the Java Options:
    -Dlog4j2.formatMsgNoLookups=true

    Just to double it up (better twice the once) you can in Windows Server also add an Environmental Variable. Goto Control Panel --> System --> Advanced System Settings --> Environmental Variables --> Under System Variables add a new entry:
    Variable name: LOG4J_FORMAT_MSG_NO_LOOKUPS
    Variable value: TRUE

    According to: https://msrc-blog.microsoft.com/2021/12/11/microsofts-response-to-cve-2021-44228-apache-log4j2/

  • Sighmon

    1 Message

    4004

    0

    Posted December 16th, 2021 16:00

    Hey Drewsky,

    Thanks for providing some info about the issue.

    I tried following your guide but could never get past user creation:

    2021-12-17 T02:57:25::CustomFunctions::6139::Failed to set change password policy
    2021-12-17 T02:57:35::Upgrade::598::User creation failed, hence restoring...

     

     

    The server I am trying to upgrade WMS on is running Windows Server 2019 Build 17763.2366 and is a domain controller.

    yigitcan.killik in this post has the extact same issue: https://www.dell.com/community/Wyse-Management-Suite/upgrade-failed-3-3-1-to-3-5-Failed-to-set-change-password-policy/m-p/8104910#M544 

    I have tried adding deny delegation to the default domain policy, creating a new GPO to set specific password requirements, running upgrade as administrator, upgrading from 3.3 to 3.3.1 then to 3.5.

    Are you able to provide some more detail about your setup and as to how you were able to get past the user creation error.

    Cheers,

    Simon

  • acertain

    1 Rookie

    •

    3 Posts

    3908

    0

    Posted December 17th, 2021 13:00

    I experienced the same issue and error in WMSInstall.log. I was running the installer from a domain user account with administrator permissions. After trying several things I eventually found a work around. It didn't require removing it from the domain or disabling the default domain policy for password complexity as other have mentioned. What I did was login to the server with a local server admin account and ran the install. It completed the setup from 3.3.1 to 3.5. I then did the same process from 3.5 to 3.5.1.

    So the issue seems to be connected to running the install from a domain account. Just trying using a local server account and it should work.

  • matteric

    1 Rookie

    •

    2 Posts

    3898

    0

    Posted December 17th, 2021 14:00

    Was able to get past the "failed to set password change policy" issue by temporarily blocking inheritance on the OU our on-prem WMS server was in, so that the domain password policy wasn't applying, then re-running the install (kudos to @Drewsky25 there). Had another issue where it failed out for "failed to grant folder level permission for LocalRepo", the fix there was to add the path for the local repository to the Uninstall key for WMS (HKLM\software\wow6432node\microsoft\windows\currentversion\uninstall\{guid-for-wms-install}\, reg_sz "LocalRepository" = "C:\path\to\repo") in case anyone runs in to that one.

  • KRoyal

    3 Posts

    3686

    0

    Posted December 22nd, 2021 06:00

    I am having this issue as well but am NOT using a DC

  • KRoyal

    3 Posts

    3674

    2

    Posted December 22nd, 2021 08:00

    I was able to resolve my issue. The fix is as follows:
     

    Move Computer object to OU with no GPO policies applied (specifically password policies but this is easiest overall)

    run gpupdate /force /boot

    Sign into machine using LOCAL admin - DO NOT use Domain admin account

    Process the update

    Optional (Best practice)
    Create a domain service account for the following services and add to Administrators group on local machine hosting WMS

    Go into services and associate the following with the service account:

    Dell WMS: Software Vault
    Dell WMS: Maria DB
    Dell WMS: Memcached
    Dell WMS: MongoDB
    Dell WMS: MQTT Broker
    Dell WMS: Tomcat Service

    Delete the local account created during 3.5 upgrade (wmsuser by default)

    Reboot and test

    After testing move computer object to Appropriate location and test again to ensure everything is working. 

  • kjhkjhjhh

    8 Posts

    723

    0

    Posted December 22nd, 2021 09:00

    @KRoyalthat would be a good idea but won't recommend doing so if the machine is a domain controller. Dell should just come up with a new installation where the user can choose and let the installer create the service account or the user can browse for custom service account...

    So Dell, when can we expect an update?