If you attempt to view a diagram document after migrating from SAS Marketing Automation 5.3 to 5.4, then you might receive the following error message:

Unable to retrieve document content

Select the Downloads tab in this note to access a fix for this issue.

The fix must be applied before the migration utility is run in order to be effective. The fix causes the utility to skip the migration of the diagram documents altogether. The diagram documents do not need to be migrated in order to be fully usable in SAS Marketing Automation 5.4.

Install the 5.4 migration fix:

1. Download the .zip file from the Downloads tab.
2. On your mid-tier computer, locate the SAS Versioned Jar Repository (VJR) entries. The typical windows location is: C:\Program Files\SAS\SASVersionedJarRepository\9.2\eclipse\plugins.
3. Find the subfolder named sas.analytics.crm.ciutilities_504300.18.0.20110112205000_d2ma54.
4. Move the jar named sas.analytics.crm.ciutilities.jar from its current directory to a backup location.
5. Unzip the file from the downloads tab and move the new sas.analytics.crm.ciutilities.jar file into the VJR folder, sas.analytics.crm.ciutilities_504300.18.0.20110112205000_d2ma54. In order to make sure that the replacement sas.analytics.crm.ciutilities.jar is installed, do not rename the new sas.analytics.crm.ciutilities.jar file. Do not leave the old version of the sas.analytics.crm.ciutilities.jar file in this VJR folder or any of its parent folders.

Test the installation of the fix:

Run the following script:

Unsuccessful installation: If the new jar file is not correctly installed, the script returns this message:

Successful installation: If the new jar file is installed correctly, the script returns this message:

If the test is successful, then run the utility as described in the migration documentation.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

Download the migration utilities fix.

Download the instructions for the fix in text format.

A fix for this issue for SAS Marketing Automation 5.4_M1 is available at:

A fix for this issue for SAS Marketing Automation 5.41 is available at: