Installation Note 55818: An upgrade-in-place on a system that contains SAS® Anti-Money Laundering does not work correctly
When you perform an upgrade-in-place on a system that contains SAS Anti-Money Laundering 6.3, the upgrade does not work properly because the SAS Anti-Money Laundering release number is the same as the release number for the upgrading release.
When this problem occurs, there is no definitive list of symptoms that can occur. However, you might experience an error or warnings similar to the following:
This problem occurs when you upgrade some other SAS product and SAS Anti-Money Laundering is included in the upgrade and when the following property is set to
true:
antimnycmnc.updateConfigure.target.is_called=true
This property is set so that customers who are updating from SAS Anti-Money Laundering 6.1 or 6.2 can update their systems. This setting causes the upgrade target to be called even when there is nothing to upgrade.
To work around this issue, perform the following steps after the installation phase in the SAS® Deployment Wizard but before the update configuration phase:
- Navigate to the SASHOME/SASDeploymentManager/9.4/product_data directory and open the following files:
- antimnycmnc__94130__prt__xx__sp0__1/configure/antimnycmnc_default.properties
- antimnylndin__94130__prt__xx__sp0__1/configure/antimnylndin_default.properties
- In those files, locate the following properties and change their values to false:
antimnycmnc.updateConfigure.target.is_called=true
antimnylndin.updateConfigure.target.is_called=true
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Anti-Money Laundering | Microsoft® Windows® for x64 | 6.1 | 6.3_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Microsoft Windows Server 2008 | 6.1 | 6.3_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Microsoft Windows Server 2008 R2 | 6.1 | 6.3_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Microsoft Windows Server 2008 for x64 | 6.1 | 6.3_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Microsoft Windows Server 2012 Datacenter | 6.1 | 6.3_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Microsoft Windows Server 2012 R2 Datacenter | 6.1 | 6.3_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Microsoft Windows Server 2012 R2 Std | 6.1 | 6.3_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Microsoft Windows Server 2012 Std | 6.1 | 6.3_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Windows 7 Enterprise x64 | 6.1 | 6.3_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Windows 7 Ultimate x64 | 6.1 | 6.3_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
64-bit Enabled AIX | 6.1 | 6.3_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
64-bit Enabled Solaris | 6.1 | 6.3_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
HP-UX IPF | 6.1 | 6.3_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Linux for x64 | 6.1 | 6.3_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Solaris for x64 | 6.1 | 6.3_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
*
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: | 2015-05-18 15:58:09 |
Date Created: | 2015-05-15 13:53:39 |