Unsolved
1 Rookie
•
5 Posts
0
1259
December 17th, 2021 12:00
WMS 3.3.1 upgrade fails to 3.5 - Error in launching script for encrypting Key Generation: Incorrect function
I've been having a bad time upgrading Dell WMS 3.3.1 to 3.5 (and then to 3.5.1).
I followed the suggestions on the forum to drop the server into an OU that gets no computer OUs, but even still I'm getting problems. It is failing at this part - it fails to initialize software valut at least a dozen times too, not sure if it gives up or it finally goes through.
2021-12-17 T14:51:51::CustomFunctions::6769::Waiting for SoftwareVault to initialize
2021-12-17 T14:51:51::CustomFunctions::6807::-classpath "C:\Program Files\DELL\WMS\Install"\lib\* -Dapp.name="InstallerScript" -Dapp.repo="C:\Program Files\DELL\WMS\Install"\lib -Dbasedir="C:\Program Files\DELL\WMS\Install" main.java.com.wyse.stratus.migration.main.LockboxServerPoller
2021-12-17 T14:51:53::CustomFunctions::6815::Software Vault is not initialized yet..
2021-12-17 T14:51:53::CustomFunctions::6474::In function GenerateSoftwareVaultEncrypKey
2021-12-17 T14:51:53::CustomFunctions::6505:: /c GenerateEncryptionKey.bat C:\Users\GESPOS~1\AppData\Local\Temp\encryptKeyOut.txt
2021-12-17 T14:52:01::CustomFunctions::6510::Script for encrypting Key Generation execution returned: 0 - 1
2021-12-17 T14:52:01::CustomFunctions::6512::Error in launching script for encrypting Key Generation: Incorrect function.
Dell marks my attempt at uploading the whole log as spam abuse, so I won't link it here.
JoshG678
4 Posts
1
February 21st, 2022 09:00
Has anyone found a fix for this? I'm also running into this on several environments. Server 2019.
JoshG678
4 Posts
2
February 21st, 2022 11:00
I figured it out.
The issue is due to the WMSUser account thats created during the 3.5.x installer not having access to run as a service.
Since our security policy only allows administrators to do this function, i was able to add that user account to the administrators group immediately once its created (During the installer) and before it attempted to start the services.
This could also be fixed by granting that user account access with your GPO's prior too the upgrade.
The 3.5 software changes all services to use this WMSUser account for login vs network/local service.
GregEsposito
1 Rookie
•
5 Posts
0
February 24th, 2022 11:00
Thanks for the guidance. With the 3.6 installer you can create a user ahead of time and denote that as the account to use. I did that, and alongside other things, it worked.
I did have to block GPOs on the server for the install, one thing I noticed was the Test-LocalCredentials.ps1/.bat did not like my server's default powershell lockdown, but couldn't override it due to policy.
Once the policy was gone, it did pass by. We'll see if it impacts usage later.