When configuring SAS software on Microsoft Windows using SAS Deployment Wizard, SAS Deployment Wizard might not progress past the SAS Metadata Server configuration step. An error message does not occur, and the step appears to be stuck.
In the SDW_yyyy-mm-dd.hh.ss.log file, the step reports a 0 return code, which indicates that the step completed.
INFO: Stage #3 Step #1 (SAS Metadata Server Configuration)
Apr 16, 2025 10:29:07 AM com.sas.ssn.Configure runAntScript
INFO: CONFIGURE: Launching Ant script - "D:\SAS\Home\SASPrivateJavaRuntimeEnvironment\9.4\jre\bin\java.exe" -Xmx1024M -classpath
<snip>
Apr 16, 2025 10:30:41 AM com.sas.ssn.Configure runAntScript
INFO: Return Code: 0
In the deploywiz_yyyy-mm-dd-hh.mm.ss.log, two exceptions might occur:
Caused by: java.lang.SecurityException: Can not initialize cryptographic mechanism
at java.base/javax.crypto.JceSecurity.<clinit>(Unknown Source)
Caused by: java.lang.SecurityException: Can't read cryptographic policy directory: unlimited
This problem is caused by the Microsoft SilentCleanup task.
To circumvent this issue, disable the Microsoft SilentCleanup task and click Retry in SAS Deployment Wizard. For more information about disabling Microsoft SilentCleanup, see Step 6 in Installation Prerequisites.