support.sas.com
 
 
support.sas.com


SAS Marketing Automation 5.1

Hot Fix Downloads

 
51MA01 was replaced by 51MA13

51MA02 was replaced by 51MA13

51MA03 was replaced by 51MA13

51MA04 was replaced by 51MA13

51MA05 was replaced by 51MA13

51MA06 was replaced by 51MA13

51MA07 was replaced by 51MA13

51MA08 was replaced by 51MA13

51MA09 was replaced by 51MA13

51MA10 was replaced by 51MA13

51MA12 was replaced by 51MA13

51MA13
Issue(s) Addressed :Introduced:
SN-032469Business-context objects in the SASŪ Marketing Automation plug-ins for SASŪ Management Console cannot be changed while metadata is being generated51MA01
SN-030980SASŪ Campaign Studio only allows users to select one value from a code node stored process variable list51MA01
SN-019806Populating SASŪ Marketing Optimization with input data from SASŪ Marketing Automation generates incorrect Eligible Offers counts51MA01
SN-019175Incorrect counts might be returned when the multi-select node "Exclude customers that meet these criteria" check box is selected51MA01
SN-019399Multiple tasks have the same name error when you schedule or execute campaigns in SASŪMarketing Automation 4.4 or SASŪCustomer Intelligence 5.151MA01
SN-032465An incorrect count might be returned if you use an Or node of type "meets any conditions" to combine multiple And nodes51MA01
SN-030967Unable to delete a link from a SASŪ Marketing Automation campaign user-defined field51MA01
SN-032467An error occurs when you update counts in a SASŪ Marketing Automation Or node and the first upstream Select node has a zero count51MA01
SN-016310Select node counts reset after executing a subsequent node51MA01
SN-030566Counts are not being returned for text fields that contain blank values51MA01
SN-030443Dates display incorrectly in the SASŪ Campaign Studio Communication Gantt chart if more than 50 occurrences are scheduled51MA01
SN-030989A zero count is returned after manually changing the values in a multi-select node51MA01
SN-032466Items that have been selected in SASŪ Campaign Studio cannot be deleted if the underlying information map has changed51MA01
SN-032554Only one response is reported when multiple treatments share the same response code51MA01
SN-030973Refining an export on an and node where a preceding select is using wildcards might result in a zero count51MA01
SN-030968Selection criteria might disappear after you change the rule in a SASŪ Campaign Studio select node51MA01
SN-030991Disk space is being used up because scheduled campaign and diagram exports do not always delete their underlying temporary tables in MATABLES51MA01
SN-032460An error occurs if you use SASŪ Marketing Automation Integration Utilities to import a campaign or diagram51MA01
SN-030990SASŪ Campaign Studio encountered a problem error when using an or node set to "Meets any conditions defined by input node"51MA01
SN-030972The SASŪ Campaign Studio refine functionality might return incorrect counts when used on an and node51MA01
SN-030969"Error executing query. The and node, or another node upstream from it, has failed to execute successfully"51MA01
SN-030986SASŪ Campaign Web Studio allows the Offer Group and Offer Sub group fields to have the same value51MA01
SN-030985"ERROR 20 Unable to log onto application server" error occurs when a scheduled campaign or diagram is launched51MA01
SN-032468SASŪ Campaign Studio diagram nodes are marked incorrectly as Ready when underlying processes fail51MA01
SN-032458An error occurs in SASŪ Marketing Automation if the name of a field that is being exported is exactly 32 characters long51MA01
SN-032555SASŪ Digital Marketing Response Codes are not available in SASŪ Customer Intelligence Studio when using Response Channel Codes51MA01
SN-033179Running concurrent SASŪ Marketing Automation campaigns can cause Java Messaging Service errors51MA02
SN-033057The Treatments tab is missing from the Business Context Properties window51MA02
SN-033176When using Select nodes to create an implied AND, SAS® Marketing Automation might be forced into a infinite loop51MA02
SN-030988SASŪ Campaign Studio select node calculated-data items appear twice after using the "save as" function51MA02
SN-032738Changes to calculated data items in a copy of a campaign cause unexpected changes to the original campaign, or varInfold is not found error51MA02
SN-033183SAS® Marketing Automation diagrams or campaigns might fail if they contain links with multiple outputs51MA02
SN-032492SASŪ Marketing Automation campaigns might fail when multiple campaigns are run together and are deployed against IBM Websphere51MA02
SN-032429A long delay occurs between when you submit a SASŪ Marketing Automation campaign or diagram for execution and the start of activity on the database51MA02
SN-032732Links in user defined fields are missing from Common Data Model51MA02
SN-032728Records are missing from the common data model51MA02
SN-032428Performance issues occur when you work with large diagrams in SASŪ Campaign Studio51MA02
SN-033046Select node remains in state "Not Ready"51MA02
SN-032246A scheduled SASŪ Marketing Automation campaign never completes51MA02
SN-032736Select node counts remain when an upstream node is added, which should cause them to be reset to "ready to update counts"51MA02
SN-033047Limit node shows 'Not Ready'51MA02
SN-033175The Treatments tab in the SASŪ Customer Intelligence Business Context plug-in for SASŪ Management Console might not be available51MA02
SN-032735URL or link address is missing from Common Data Model51MA02
SN-032733User defined fields are missing from Common Data Model when copying a campaign51MA02
SN-033178SASŪ Real-Time Decision Manager general I/O activities are unable to read, but can update and modify51MA02
SN-033048An error occurs when a Cell code contains a hyphen(–) or a dash (—) 51MA02
SN-033181Some fields in the SAS® Customer Intelligence common data model might not be populated51MA02
SN-033182ALERT - Executing a communication in SASŪ Marketing Automation clears the value of the campaign folder in the campaign table of the Common Data Model51MA02
SN-033567Removing the limit criteria from a SASŪ Customer Intelligence Prioritize node causes an error51MA03
SN-033566Diagrams in SASŪ Customer Intelligence Studio take a long time to open51MA03
SN-033857Communication codes might not be unique when you use the “Save As” feature to create a new campaign51MA04
SN-034329The Common Data Model in SAS® Customer Intelligence does not contain communication budget information51MA05
SN-032710SASŪ Campaign Web Studio user-defined field list selections are not reflected when reviewing the campaign or communication in SAS Campaign Studio51MA05
SN-034340Communication estimated-response rates are not being reflected in the SASŪ Customer Intelligence Reporting Common Data Model51MA05
SN-018904Counts might be incorrect if a diagram contains a map node with an underlying left join that is defined between the tables in the information map51MA05
SN-032713Cannot change shared user permissions once a campaign has been saved51MA05
SN-036366SASŪ Customer Intelligence Response and Contact History performance improvements51MA05
SN-034417The Summary procedure and SQL methods of metadata generation return different counts51MA05
SN-034333Incorrect counts are returned when priorities are changed in a split node51MA05
SN-034419An error occurs and all other fields in the dialog box are blanked out when editing the treatment field manually in a Communication node51MA05
SN-034515Cells that are created by a Prioritize or Split node are not distributed correctly on the diagram51MA05
SN-034342An incorrect count is returned when updating counts on a Select node referencing an interval item 51MA05
SN-032488SASŪ Marketing Automation campaigns fail and an out-of-memory error occurs when you execute many complex campaigns in a 24-hour period51MA05
SN-034327Contact History is not mapped for this subjectID error when updating contact history51MA05
SN-034492Today's date is not exported correctly when rows are appended to an Oracle table51MA05
SN-034338Campaigns created from campaign templates that were migrated from SASŪ Marketing Automation 4.4 cannot be approved as the approval link is not active51MA05
SN-034335Missing MATABLES file error occurs when combining the output from response nodes to a select node51MA05
SN-034339Scroll bars are missing from the diagram tool parameter dialog box when the underlying stored process contains many input fields51MA05
SN-034331Historical contents for user-defined fields are overwritten in the SASŪ Customer Intelligence Common Data Model when a campaign is published manually51MA05
SN-034341A SASŪ Customer Intelligence campaign export might fail with an error when appending to or replacing an Oracle table51MA05
SN-034337SAS® Customer Intelligence fails to update contact history when using bulkload against a Teradata database51MA05
SN-034330Netezza Data Definition Language (DDL) scripts are not included with SAS® Customer Intelligence51MA05
SN-034334An error occurs when creating an Audit Log from a diagram that contains a split node using the "values from a data item" split criteria51MA05
SN-034336SASŪ Customer Intelligence Studio might be slow to load complex diagrams that contain communications or exports using the refine functionality51MA05
SN-034416Incorrect counts are returned in a split node cell when splitting on date values51MA05
SN-034516An Exception error occurs when attempting to open or create a Business Context51MA05
SN-034332Contact History for the last occurrence in a recurring campaign might be overwritten if the number of occurrences is changed by the Administrator51MA05
SN-034420Refine criteria are not being applied when implicit or explicit AND processing feeds directly into an export node51MA05
SN-034518Cannot produce Audit Documentation when a campaign contains a split node51MA05
SN-034328Prioritize node Limit functionality does not obey the same random rules as a Limit node51MA05
SN-035514SASŪ Customer Intelligence is performing slower than anticipated51MA06
SN-036425A java.lang.NullPointerException occurs when using the Save As function for a scheduled diagram51MA07
SN-017377Async execution failure when update counts in Campaign Studio51MA07
SN-036317An error occurs when you close a campaign with a calculated data item without saving the campaign51MA07
SN-035245It is not possible to change the status of a campaign after the campaign is approved51MA07
SN-035160An incorrect count is returned when you use an Export node in SASŪ Customer Intelligence 51MA07
SN-036407Values in the selection lists of a stored process are missing when imported via Integration Utilities51MA07
SN-032746An exception error occurs when attempting to save a recurring campaign51MA07
SN-036596Slow performance occurs when viewing a report that is built from a SASŪ Information Map that contains a large number of data items51MA07
SN-036424Reference to a multi-select node still appears in the macore.log file even after the node is deleted from the diagram 51MA07
SN-036432The Link node displays as Ready to Update Count instead showing of an actual count51MA07
SN-036312Cell and And nodes might not display counts and might generate an error message in the macore log51MA07
SN-036362SASŪ Customer Intelligence Concurrency performance improvements51MA07
SN-036423A communication node shows a status of "Ready" rather than showing the actual counts51MA07
SN-035237Changes that are made to the Schedule Time will not show up in the Schedule Manager in the SASŪ Management Console51MA07
SN-034178Large SASŪ Marketing Automation diagrams take a long time to redraw after making changes51MA07
SN-035246An error indicating that MATABLES does not exist occurs when the "Use most current data" check box is selected51MA07
SN-035247The CAMPAIGN_STATUS field is set to blank when a communication is executed51MA07
SN-036211Exporting to the same file from multiple export or communication nodes can cause unpredictable results51MA07
SN-035244Only a description for the link is published in SASŪ Customer Intelligence Studio when specifying a brief type of "link" in the export definition51MA07
SN-035239You might have a campaign or diagram without an owner if you use an operation system or Regional Setting other than English51MA07
SN-036406Error "Have run out of response numbers - just generated number 1000(+)" occurs when trying to add a new Response node51MA07
SN-036422The Integration utility sasmaimport fails when you use it to import a diagram with two split nodes51MA07
SN-035242Original values for calculated data items are retained in SASŪ Customer Intelligence Studio when you use the Save As function when saving a campaign51MA07
SN-035240List values for Reporting Data are always separated by a blank space regardless of any changes that are made to settings in SASŪ Management Console51MA07
SN-035251CELL_PACKAGE_SK is not updated when using the "Save as" function for a campaign with more than one occurrence 51MA07
SN-036421The Integration utility sasmaimport fails when you move SASŪ Real-Time Decision Manager Flows between environments51MA07
SN-036310Updating the Contact History might produce unpredictable results when you have a communication node exporting into two tables in Oracle51MA07
SN-036428Concurrent processing of campaign diagrams is sometimes slow51MA07
SN-036430When performing a Save As on a Campaign in SASŪ Customer Intelligence, the Refine Output check box is cleared51MA07
SN-036482ALERT - Incorrect results, based on prior counts, might be returned when you execute a campaign for a second or a subsequent time51MA08
SN-036486ALERT - SASŪ Marketing Automation metadata fails for all tables and generates an error message51MA08
SN-036614An error occurs when when using the Structured Query Language (SQL) method to generate date histogram metadata from an Oracle database51MA09
SN-036615Optimized count is cleared in communications and exports when campaigns are executed after applying the 51MA08 hot fix51MA09
SN-036995ALERT - The contact history and export files do not reflect the most current information when campaigns are re-executed at the campaign level51MA10
SN-031800SASŪ Customer Intelligence 5.1 campaigns do not publish when the Common Data Reporting model is deployed on SASŪ Scalable Perfromance Data ServerŪ51MA12
SN-038026An error occurs when you try to publish contact history data to the SASŪ Scalable Performance Data ServerŪ51MA12
SN-038027Attempts to publish a SASŪ Customer Intelligence Studio campaign fail with an error message when using SASŪ Scalable Performance Data ServerŪ 51MA12
SN-038284An error might occur when you use the SASŪ Customer Intelligence plug-in for SASŪ Management Console to update metadata in an information map 51MA12
SN-038028An error occurs when you update contact history while running multiple campaigns concurrently against the SASŪ Scalable Performance Data ServerŪ51MA12
SN-035963MQJMS6116 errors appear in the macore and SystemOut logs51MA12
SN-038081An exception error might occur when you update counts in a campaign's Communication node or Link node 51MA12
SN-038187An incorrect count is returned when you use an outer (left) join51MA12
SN-038247Incorrect counts are returned in a Select node when you use the NOT LIKE operator51MA12
SN-038043You might experience poor performance when you use a Prioritize node in a diagram that contains more than 50 input nodes51MA12
SN-038246A Split node returns incorrect counts when sorted on a field in a folder that has a many-to-one relationship with the subject folder51MA12
SN-038029Attempts to view the details of a SASŪ Customer Intelligence business context fail with a null pointer error 51MA12
SN-037555A java.lang.IllegalStateException error message displays when you clear the metadata cache51MA12
SN-038030Attempts to publish a SASŪ Customer Intelligence Studio campaign fail with an error message when you use SAS/ACCESSŪ Interface to Netezza51MA12
SN-038323Support for Platform Suite for SASŪ (Platform LSF version 7) is required with SASŪ Marketing Automation 5.151MA12
SN-038326The status and count of a Select node are incorrect if you change the subject51MA12
SN-042088When modified, the Communication and Campaign User Defined Field (UDF) names do not save correctly51MA13
SN-042089Problems might occur when changing an existing SASŪ Campaign Management export definition or seed definition in SASŪ Management Console51MA13
SN-042090The display order of data items in SASŪ Campaign Studio is incorrectly presented alphabetically51MA13
SN-042091A target diagram might execute unnecessarily51MA13
SN-040093A Split node returns zero counts when you use values from a data item that is either of type DATE or of type TIMESTAMP51MA13
SN-040244You cannot schedule a second Communication node after the first Communication node executes in SASŪ Customer Intelligence Studio 5.151MA13
 
WindowsReleased: Jan 2011
Install Instructions: 51MA13wn.pdf
Download: 51MA13 for Windows   (file size: 175.9M)
NOTE: This hot fix is compatible with SAS Marketing Optimization hot fix 51mo14. If you are using SAS Marketing Automation in conjunction with SAS Marketing Optimization please ensure that both 51MA13 and 51mo14 are loaded.
 
HPUX 64bitReleased: Jan 2011
Install Instructions: 51MA13h6.pdf
Download: 51MA13 for HPUX 64bit   (file size: 175.9M)
NOTE: This hot fix is compatible with SAS Marketing Optimization hot fix 51mo14. If you are using SAS Marketing Automation in conjunction with SAS Marketing Optimization please ensure that both 51MA13 and 51mo14 are loaded.
 
Solaris 64bitReleased: Jan 2011
Install Instructions: 51MA13s6.pdf
Download: 51MA13 for Solaris 64bit   (file size: 175.9M)
NOTE: This hot fix is compatible with SAS Marketing Optimization hot fix 51mo14. If you are using SAS Marketing Automation in conjunction with SAS Marketing Optimization please ensure that both 51MA13 and 51mo14 are loaded.
 
AIX 64bitReleased: Jan 2011
Install Instructions: 51MA13r6.pdf
Download: 51MA13 for AIX 64bit   (file size: 239.4M)
NOTE: This hot fix is compatible with SAS Marketing Optimization hot fix 51mo14. If you are using SAS Marketing Automation in conjunction with SAS Marketing Optimization please ensure that both 51MA13 and 51mo14 are loaded.
 
HPUX for ItaniumReleased: Jan 2011
Install Instructions: 51MA13hx.pdf
Download: 51MA13 for HPUX for Itanium   (file size: 524.9M)
NOTE: This hot fix is compatible with SAS Marketing Optimization hot fix 51mo14. If you are using SAS Marketing Automation in conjunction with SAS Marketing Optimization please ensure that both 51MA13 and 51mo14 are loaded.
Top ^

 



PLEASE CAREFULLY READ THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT ("AGREEMENT") BEFORE DOWNLOADING MATERIALS FROM THIS SITE. BY DOWNLOADING ANY MATERIALS FROM THIS SITE, YOU ARE AGREEING TO THESE TERMS.
You are downloading software code ("Code") which will become part of a product ("Software") you currently have licensed from SAS Institute Inc. or one of its subsidiaries ("the Institute"). This Code is designed to either correct an error in the Software or to add functionality to the Software. The code is governed by the same agreement which governs the Software. If you do not have an existing agreement with the Institute governing the Software, you may not download the Code.
SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. ® indicates USA registration. Other brand and product names are registered trademarks or trademarks of their respective companies.

Copyright © 2014 SAS Institute Inc. All Rights Reserved.