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.
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!
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
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.
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.
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.
@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...
systemreich
6 Posts
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