Installation Note 69492: Running the SASĀ® Anti-Money Laundering "csCore_load_seed_data.sh"/"cscore_load_seed_data.sh" post-configuration script fails with a fatal error
When running the SAS Anti-Money Laundering csCore_load_seed_data.sh post-configuration script in SAS Anti-Money Laundering 8.2 or the cscore_load_seed_data.sh post-configuration script in SAS Anti-Money Laundering 8.3, you might encounter a fatal error similar to the following when running the post-installation instructions:
"ERROR: The archive directory /opt/sas/viya/home/amlRegReportConfiguration/resources/data does not exist"]}
An example of the full error message is shown in the following screenshot:
To address the issue, implement the following workaround.
For SAS Anti-Money Laundering 8.2.x, the workaround is to modify the statement in line number 133 of the csCore_load_seed_data.sh script by removing the space between "=" and the "$".
The script is found in the opt/sas/spre/home/SASFoundation/misc/amlcoresrv/csCore/deploy_scripts/tasks/ directory. Here is an example of the change that you should make:
Original: artifacts_dir= ${artifacts_dir//opt\/sas\/viya\/home/tmp/\sas/\fcf}
Correction: artifacts_dir=${artifacts_dir//opt\/sas\/viya\/home/tmp/\sas/\fcf}
For SAS Anti-Money Laundering 8.3.x, the workaround is to modify the statement in line number 288 of the cscore_load_seed_data.sh script by removing the space between "=" and the "$".
The script is found in the /opt/sas/spre/home/SASFoundation/misc/amlcoresrv/bin/ directory. Here is an example of the change that you should make.
Original: artifacts_dir= ${artifacts_dir//opt\/sas\/viya\/home/tmp/\sas/\fcf}
Correction: artifacts_dir=${artifacts_dir//opt\/sas\/viya\/home/tmp/\sas/\fcf}
Click the Hot Fix tab in this note for a link to instructions about accessing and applying the software update.
Operating System and Release Information
SAS System | SAS Anti-Money Laundering | Linux for x64 | 8.2 | | Viya | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Installation Note |
Priority: | high |
Date Modified: | 2023-06-21 12:15:42 |
Date Created: | 2022-08-23 13:50:17 |