The Load Server Content step for SAS® Visual Analytics Services fails during migration with "An error occurred while migrating the Blacklist Database"


When you migrate SAS Visual Analytics Services to SAS® 9.4M8 (TS1M8) or SAS® 9.4M9 (TS1M9), the Load Server Content step might fail with the following error:

The following problem was encountered while configuring SAS Visual Analytics Services: An error occurred while migrating the Blacklist Database. Configuration script: /install/cfgsas1/SASHome/SASVisualAnalyticsServices/7.53/Config/bisrvmid_config.xml - For more information, see the following log file located at /install/cfgsas1/config/Lev1/Logs/Configure/bisrvmid_loadServerContent_2025-10-20-01.52.28.log - You must resolve this error as reported in the log before continuing. If you can fix the issue immediately, do so and click Retry. Otherwise, click Stop and restart the configuration at a later time, after the issue has been resolved.

In the bisrvmid_loadServerContent log file, an error similar to the following might also occur:

/install/cfgsas1/SASHome/SASVisualAnalyticsServices/7.53/Config/bisrvmid_
config.xml:300: Script Failed: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
embedded_script_in__install_cfgsas1_SASHome_SASVisualAnalyticsServices_7_dot
_53_Config_bisrvmid_config_dot_xml: 30: unable to resolve class org.springframework.dao.DataAccessException
 @ line 30, column 28.
                              import org.springframework.dao.DataAccessException
                              ^embedded_script_in__install_cfgsas1_SASHome_SASVisualAnalyticsServices
_7_dot_53_Config_bisrvmid_config_dot_xml: 31: unable to resolve class org.springframework.jdbc.core.JdbcTemplate
 @ line 31, column 28.
                              import org.springframework.jdbc.core.JdbcTemplate
                              ^embedded_script_in__install_cfgsas1_SASHome_SASVisualAnalyticsServices
_7_dot_53_Config_bisrvmid_config_dot_xml: 32:
unable to resolve class org.springframework.beans.factory.InitializingBean
 @ line 32, column 28.
                              import org.springframework.beans.factory.InitializingBean
                              ^3 errors

This problem is caused by JAR files that are incorrectly named.

Workaround

To circumvent this issue, complete the following steps:

1. Make backup copies of the following files by copying them to another directory outside of the SAS configuration directory. Do not leave copies in the original directories.

<sashome>/SASVersionedJarRepository/eclipse/plugins/org.springframework.jdbc_6.1.22.0_
SAS_20250722144515/spring-jdbc-6.1.21-spring-framework-6.1.22.jar

<sashome>/SASVersionedJarRepository/eclipse/plugins/org.springframework.beans_6.1.22.0_
SAS_20250716072145/spring-beans-6.1.21-spring-framework-6.1.22.jar

<sashome>/SASVersionedJarRepository/eclipse/plugins/org.springframework.transaction_6.1.22.0_
SAS_20250716150106/spring-tx-6.1.21-spring-framework-6.1.22.jar

<sashome>/SASVersionedJarRepository/eclipse/plugins/org.springframework.core_6.1.22.0_
SAS_20250714112503/spring-core-6.1.21-spring-framework-6.1.22.jar

2. Rename each file as follows:

spring-jdbc-6.1.21-spring-framework-6.1.22.jar to spring-jdbc.jar

spring-beans-6.1.21-spring-framework-6.1.22.jar to spring-beans.jar

spring-tx-6.1.21-spring-framework-6.1.22.jar to spring-tx.jar

spring-core-6.1.21-spring-framework-6.1.22.jar to spring-core.jar

3. Click Retry on the SAS® Deployment Wizard

Note: A permanent fix for this issue will be delivered in the Q4 SAS Security Update.