When the customer is using Microsoft SQL server and Windows authentication, sometimes it will fail during the Deep Security Manager upgrade verification because the database cannot connect.
In the same folder of Deep Security Manager installer, it will also generate an error.log showing the Kerberos preauth request throws the exception shown in the screenshot below:
The solution to resolve this issue is to add the JRE options "-Dsun.security.krb5.disableReferrals=true" in the vmoptions file in both the DSM and installer.
For Windows:
1. Add "-Dsun.security.krb5.disableReferrals=true" to Deep Security Manager.vmoptions file to the DSM installation folder
2. Copy the same file to the same folder of the DSM installer and rename it to your installer file name.
For example, Manager-Windows-12.0.xxx.x64.vmoptions
1. Add "-Dsun.security.krb5.disableReferrals=true" to dsm_s.vmoptions file to the DSM installation folder
2. Copy the same file to the folder of the DSM installer and rename it to your installer file name.
For example, Manager-Linux-12.0.xxx.x64.sh.vmoptions
After applying the above steps you can now re-run the Deep Security Manager installer and this time it will pass the upgrade verification
