E88018 for Linux for x64 |
SAS Marketing Automation 5.41 |
Issue(s) Addressed: | Introduced: |
43171 | ALERT - The error "User does not have permission to execute campaign" is returned when you schedule a campaign |
E88001 |
43630 | The campaign-group schedule date overwrites a campaign schedule date |
E88001 |
44331 | Invalid characters within a flow name in SAS® Management Console using SAS® Marketing Automation cause an exception error |
E88001 |
44446 | SAS® Customer Intelligence campaigns and communications are slow to open if the system's metadata repository contains multiple custom associations |
E88001 |
44795 | Tests of a decision diagram or campaign fail when the diagram uses a data process for data in DB2 |
E88001 |
41838 | The first user's update to a SAS® Marketing Automation campaign is locked while a second user is loading another campaign in the same business context |
E88002 |
43031 | Executing a campaign group for a Priority Optimized campaign returns the error "com.sas.analytics.crm.util.SystemCheck - Error executing campaign" |
E88002 |
43033 | The macro &MATableforMacro might incorrectly generate an empty table when you run a Process node in SAS® Customer Intelligence Studio |
E88002 |
43410 | When SAS® Marketing Automation has a large number of concurrent users, some of processes might fail to respond, and fail to complete |
E88002 |
43928 | SAS® Marketing Automation might remove the scheduled flows for a campaign and its communications when you use "Save As" to make a copy of the campaign |
E88002 |
43931 | SAS pooled workspace server sessions are sometimes not released after they execute SAS® Marketing Automation campaigns |
E88002 |
44413 | Opening a saved campaign or diagram gives a "sas.analytics.crm.flow.FlowPostProcessor.." error |
E88002 |
44483 | A "Problem executing: communication.." error appears when multiple communications for the same campaign are executed |
E88002 |
44746 | Moving items in the criteria for a Multi-select node when the group option is used might incorrectly change the logical operator (AND/OR) |
E88002 |
44758 | SAS® Customer Intelligence Studio might return "Error running list of nodes. java.lang.NullPointerException" when you run counts |
E88002 |
45100 | SAS® Customer Intelligence Studio might not create Process node output cells if your diagram already has another Process node |
E88002 |
45136 | SAS® Marketing Automation scheduling fails to create an entry for the first month when there are fewer than 31 days in the first month |
E88002 |
45217 | Amending campaign details between occurrences of a SAS® Marketing Automation campaign might lead to corruption of the Common Data Model |
E88002 |
45218 | Amending SAS® Marketing Automation campaign treatments between campaign occurrences might lead to corruption of the data in these items |
E88002 |
45463 | SAS® Customer Intelligence Studio does not reflect the execution status of a campaign group in the campaign group window |
E88002 |
45480 | SAS® Marketing Automation returns the error "Cannot save attribute _memberTableDO..." when you try to save a campaign that contains a Prioritize node |
E88002 |
45554 | SAS® Customer Intelligence Studio exhibits poor performance when displaying a list of e-mail broadcasts in a Communication node |
E88002 |
45748 | Manually publishing in SAS® Customer Intelligence Studio results in an empty CI_DYNAMIC_TREATMENT_ATTRIBUTE table in the Common Data Model |
E88002 |
45948 | SAS® Campaign Web Studio might remove the contents of a dynamic external list in a campaign's custom details after you edit the list |
E88002 |
45969 | Campaign Group execution fails to complete in SAS® Customer Intelligence Studio when "Use Most Current Data" is checked |
E88002 |
45973 | Error "Task sequence ... contains multiple tasks with the same name" is returned when you execute a campaign group for optimization |
E88002 |
43414 | Setting the format for a custom tag in an export definition returns the message "The format is not valid" |
E88002 |
45103 | Response in SAS® Customer Intelligence Studio is slow when you drag and drop nodes |
E88002 |
44480 | Process nodes might be missing from SAS® Customer Intelligence campaigns and diagrams that are imported from another environment |
E88002 |
44854 | Viewing diagram documents fails with 'Unable to retrieve document content' after SAS® Marketing Automation 5.3 to 5.4 migration |
E88002 |
45264 | SAS® Customer Intelligence Studio returns "The user does not have permission to perform this action" when you add or edit Calculated Data Items |
E88002 |
44969 | SAS® Digital Marketing might fail to update the SAS® Customer Intelligence response and contact history tables when you use JBOSS |
E88002 |
44411 | SAS® Customer Intelligence scheduled campaigns might fail to execute when they cannot obtain a lock for the MAMISC.SEQUENCE table |
E88002 |
44745 | SAS® Digital Marketing responses might generate a unique constraint error and fail to update the SAS® Customer Intelligence response history table |
E88002 |
45806 | SAS® Marketing Automation returns an "Invalid object name..." error when you use a case-sensitive collation for your SQL Server database |
E88002 |
45809 | SAS® Marketing Automation returns the error "Teradata row not delivered (trget): Transaction ABORTed due to deadlock" when you publish a campaign |
E88002 |
44176 | Identifiers in SAS® Real-Time Decision Manager campaigns and diagrams might be unavailable for assignment |
E88003 |
45027 | Modifying the format for data item "CELL_CNTRL_GRP" in SAS® Customer Intelligence Studio gives a "The format [xxx] is not valid." error |
E88003 |
45530 | The successful execution of campaign occurrences is not displayed in the Occurrences tab of the Execution screen in SAS® Customer Intelligence Studio |
E88003 |
46122 | SAS® Management Console Schedule Manager does not list your SAS® Marketing Automation metadata generation job in the list of jobs for new flows |
E88003 |
46652 | Numbers that are used in the custom details for treatments in SAS® Customer Intelligence Studio might be displayed in scientific notation |
E88003 |
46886 | "Acquired Individual Information Map" messages when executing a Campaign Group in SAS® Customer Intelligence Studio |
E88003 |
46972 | Campaigns are listed incorrectly when you apply filter criteria in the Campaigns window in SAS® Customer Intelligence Studio |
E88003 |
47002 | Performance issues occur when executing the optimization step in a SAS® Customer Intelligence Campaign group |
E88003 |
47234 | A Process node does not receive an optimized count from a Communication node when you use SAS® Campaign Studio |
E88003 |
46976 | SAS® Customer Intelligence campaigns occasionally become unresponsive when executing |
E88003 |
45943 | SAS® Customer Intelligence Studio returns the error "InvocationTargetException" when a Code node requires user-selected values from a dynamic list |
E88003 |
46655 | Priority-based optimization is the only valid optimization option offered by SAS® Marketing Automation |
E88003 |
46721 | Some data items might be unavailable for inclusion in a seed definition in SAS® Marketing Automation |
E88003 |
46736 | SAS® Customer Intelligence Studio might not enable you to view or edit values in a "dynamic list" user-defined field |
E88003 |
44754 | SAS® Customer Intelligence Studio export files of type Excel are unreadable with Microsoft Excel 2010 |
E88003 |
45035 | The "RESPTRACKING_CD" field is incorrectly placed at the end of the data set |
E88003 |
46973 | SAS® Customer Intelligence campaigns experience poor performance or fail upon execution |
E88003 |
46999 | An error might occur when you open Microsoft Excel files that have been created from a SAS® Marketing Automation Export node or Communication node |
E88003 |
46753 | A data process in a SAS® Real-Time Decision Manager campaign returns the error "invalid column name" |
E88004 |
47014 | Error-handling logic in SAS® Marketing Automation might not identify the campaign that is causing a problem |
E88004 |
47119 | The error "java.lang.StackOverflowError" occurs when you open a large campaign in SAS® Customer Intelligence Studio |
E88004 |
47193 | Unauthorized users are able to select Diagram nodes in SAS® Customer Intelligence Studio |
E88004 |
47291 | The Group Name and Group Folder fields do not populate when you are creating a group |
E88004 |
47292 | An error occurs when saving a global calculated item in SAS® Customer Intelligence Studio |
E88004 |
47338 | The Campaign Group window in SAS® Customer Intelligence Studio does not show the actual execution date |
E88004 |
47344 | "Unable to locate node" error messages fill the SASMarketingAutomationCore.log file |
E88004 |
47776 | A SAS® Marketing Automation export definition allows for SAS® Digital Marketing e-mail broadcasts but not SMS broadcasts |
E88004 |
47930 | Campaigns are listed incorrectly when you apply filter criteria in the Campaigns window in SAS® Customer Intelligence Studio |
E88004 |
47982 | Using Boolean criteria in a Multi-filter node might not return correct results |
E88004 |
47983 | The SAS® Real-Time Decision Manager process for dynamic treatments does not insert all of the treatment_hash_val records |
E88004 |
47192 | An error occurs when you group the output cells of a SAS® Customer Intelligence Split node |
E88004 |
47341 | The functionality of the Multi-select node in SAS® Customer Intelligence Studio 5.1 is not available in SAS® Customer Intelligence Studio 5.41 |
E88004 |
48072 | A campaign brief can appear only in the first position of a campaign definition |
E88004 |
48114 | A new campaign might fail to publish when copying and pasting a Treatment Campaign in SAS® Management Console |
E88004 |
46969 | Contact history counts are not being updated for campaign occurrences when the underlying database is Teradata |
E88004 |
47043 | An Export or Communication node that is executed in SAS® Customer Intelligence Studio takes a long time to run |
E88004 |
48567 | SAS® Real-Time Decision Manager arbitration returns "Unable to execute query" when it receives more than 32KB of treatment data |
E88005 |
48964 | CleanPublish might not insert the ci_communication record for SAS® Real-Time Decision Manager campaigns |
E88005 |
46244 | COMMUNICATION_SK in table CI_COMMUNICATION is overwritten when scheduling a campaign with 999 occurrences in SAS® Customer Intelligence Studio |
E88006 |
48154 | A SAS® Marketing Automation campaign fails and generates the error "Could not get campaign manager or flow manager when resolving object names" |
E88006 |
48159 | Moving items in the criteria for a multi-select node might fail if multiple group options are used |
E88006 |
48684 | Campaign code is incorrectly represented as CAMPAIN_CD in Chinese translation properties files for SAS® Marketing Automation |
E88006 |
43343 | Renaming the column in one export definition for SAS® Marketing Automation changes the column name in another export definition |
E88006 |
47931 | Node counts cannot be cleared in a SAS® Customer Intelligence Studio diagram |
E88006 |
48708 | In SAS® Campaign Web Studio, you cannot view the custom detail on the Campaign Brief when it is held as a physical file |
E88006 |
48872 | SAS® Real-Time Decision Manager campaigns and SAS® Digital Marketing campaigns might not consistently update the contact history |
E88006 |
47819 | Temporary tables are not deleted after successful updates of the SAS® Customer Intelligence Common Data Model Response History table |
E88006 |
48032 | Export files that are generated from SAS® Marketing Automation incorrectly show quotation marks in the header |
E88006 |
48157 | Executing multiple communications concurrently in SAS® Marketing Automation using Oracle might cause deadlock errors |
E88006 |
48846 | The SAS® Real-Time Decision Manager treatment count does not accurately reflect treatments that are selected for offer arbitration |
E88006 |
48683 | Using an external table for treatments in SAS® Customer Intelligence Studio results in an error message |
E88007 |
48935 | Connection arrows are removed from a diagram when you change the "Use as a marketing cell property" of a link or reporting link node |
E88007 |
48977 | A monthly recurring SAS® Marketing Automation campaign has incorrect dates displayed in the Gantt chart |
E88007 |
48981 | SAS® Marketing Automation campaigns might open slowly if there are many global calculated data items |
E88007 |
49170 | The SAS® Marketing Automation Launcher command-line execution fails when a campaign is open in SAS® Customer Intelligence Studio |
E88007 |
49343 | SAS® Real-Time Decision Manager might not insert the correct list of treatments for a decision campaign into the Common Data Model |
E88007 |
49346 | The SAS® Real-Time Decision Manager arbitration process might log an "RTDMTimeoutException" error message and fail to finish |
E88007 |
49518 | The SAS® Customer Intelligence Treatment Utility fails |
E88007 |
49527 | User-defined values for treatments in SAS® Real-Time Decision Manager are corrupt |
E88007 |
49041 | Publishing a campaign can cause a warning |
E88007 |
49042 | Publishing a campaign in SAS® Marketing Automation results in an error message |
E88007 |
49043 | Performance problems occur when you use SAS® Marketing Automation integrated with SAS® Marketing Optimization |
E88007 |
49520 | The CI_CAMPAIGN.LAST_MODIFIED_DTTM column does not update when you publishing a campaign in SAS® Customer Intelligence Studio |
E88007 |
48029 | The expected behavior does not occur when selecting the approval options check box for SAS® Customer Intelligence Decision Campaigns |
E88008 |
49557 | A SAS® Marketing Automation Schedule Gantt chart might show an incorrect end date for recurring campaigns |
E88008 |
49655 | UDF historic data is incorrectly updated when information is changed in between a scheduled campaign or communication |
E88008 |
49659 | "The diagram is valid" message is displayed despite an invalid underlying link when you validate a diagram in SAS® Customer Intelligence Studio |
E88008 |
49669 | A date string entered in a text field on Custom Details in SAS® Customer Intelligence Studio is incorrectly converted to another date format |
E88008 |
49676 | Copying nodes in SAS® Customer Intelligence Studio might prevent a campaign from opening |
E88008 |
49690 | Copying nodes in SAS® Customer Intelligence Studio can result in duplicate node names |
E88008 |
46654 | SAS® Marketing Automation campaigns on a Netezza database might fail to execute with error "Could not serialize - transaction aborted..." |
E88008 |
49797 | SAS® Marketing Automation campaigns that are complex and use a Common Data Model held in Netezza might fail with a serialization error |
E88008 |
50018 | The error "Missing MATables" occurs in SAS® Customer Intelligence Studio when you execute a campaign group with a zero optimized count |
E88008 |
47180 | A user who does not own a campaign but may edit it will not be informed if the campaign has been optimized |
E88009 |
49673 | Generating MAMetadata fails when the underlying data is held in SAS® Scalable Performance Data Server |
E88009 |
50161 | MATables that are generated for Process nodes are not removed when you clear all counts |
E88009 |
50163 | An error might occur when you use the Save As function in SAS® Customer Intelligence Studio |
E88009 |
50334 | A SAS® Real-Time Decision Manager Reply node calculated variable that converts a numeric tag to an integer causes a campaign to fail validation |
E88009 |
50348 | A Map node returns incorrect counts if the underlying tables are connected with an outer join |
E88009 |
50421 | An approved SAS® Marketing Automation campaign that is opened by a non-approval user incorrectly remains locked when the campaign is closed |
E88009 |
50434 | The TOTAL_PREOPTIMIZED_CONTACT_CNT field in the CI_CELL_PACKAGE table does not always populate |
E88009 |
50515 | SAS® Customer Intelligence campaigns that run for a long period of time fail to finish |
E88009 |
50616 | In SAS® Marketing Automation, a change in a campaign schedule results in the Campaign Occurrence numbers being reset and the history overwritten |
E88009 |
50621 | Using "Save as" on a deployed treatment campaign and then deploying its treatment set causes the error "Event definition... does not exist" |
E88009 |
50622 | Changing the order of parameters in a treatment set event triggers "Event definition _TS_XXXX ...does not exist" when executing a parent campaign |
E88009 |
50712 | Support for the Teradata TPT method in the SAS® Marketing Automation MAUpload macro variable |
E88009 |
50762 | Scheduling recurrent campaigns in SAS® Customer Intelligence Studio do not exceed 106 occurrences |
E88009 |
51058 | A parse error occurs in the JBoss 5.1 web application server log |
E88009 |
51198 | SAS® Real-Time Decision Manager might follow incorrect branch when large numbers are used in branch criteria |
E88009 |
50917 | Contact history updates are lost when the SAS® Customer Intelligence reporting service and SAS® Customer Intelligence core become disconnected |
E88009 |
49221 | Temporary tables are not deleted after SAS® Customer Intelligence updates to Contact History, Response History, or Presented Treatment tables |
E88009 |
50742 | The error "Transaction ABORTed due to deadlock issue" occurs when you use various SAS® Marketing Automation macros |
E88009 |
50755 | Execution errors occur in SAS® Marketing Automation when you update the Contact History tables in DB2 |
E88009 |
50873 | The contact history records are not updated as failed contacts when the underlying broadcasts return as hard bounces |
E88009 |
49233 | An imported decision campaign with a treatment campaign set fails and returns an error |
E88010 |
49622 | Publishing a decision campaign also publishes its treatment campaign sets even when the sets are already marked for deployment |
E88010 |
51324 | SAS® Customer Intelligence Studio might respond slowly when you have a large number of decision campaigns and treatment campaigns |
E88010 |
51327 | Updating a SAS® Real-Time Decision Manager treatment clears its mapped custom details in decision campaign Reply nodes without warning |
E88010 |
51325 | Some pop-up menu commands cannot be used when you select more than one object in the SAS® Management Console folder view |
E88010 |
51326 | SAS® Real-Time Decision Manager uses an unnecessary JMS queue during writes to the SAS® Customer Intelligence common data model database |
E88010 |
51536 | The error "Could not serialize - transaction aborted" occurs when you update the CI_CELL_PACKAGE_TREATMENT_CNT table |
E88010 |
51779 | Drawing lines between the nodes in SAS® Customer Intelligence Studio might be slow |
E88011 |
52150 | A campaign takes a long time to open in SAS® Customer Intelligence Studio when it includes numerous Cell nodes and Treatments |
E88011 |
49627 | The response time for a SAS® Real-Time Decision Manager campaign increases with each added treatment custom detail tag that is used in a Reply node |
E88012 |
52742 | Incorrect counts might be produced when a Limit node is used in conjunction with Exclusion nodes in SAS® Customer Intelligence Studio |
E88012 |
52988 | The error "FATAL: Unrecoverable I/O error detected in the execution of the DATA step program" occurs when you execute campaigns |
E88013 |
53002 | SAS® Real-Time Decision Manager might return "java.lang.ClassCastException" when you map a character to a character list in a custom detail tag |
E88013 |
51498 | SAS® Marketing Automation might fail to delete temporary tables |
E88014 |
53222 | The error "A lock is not available for MATABLES" might occur when you execute a campaign |
E88014 |
52752 | Running multiple campaigns (or multiple nodes with a campaign) concurrently in SAS® Marketing Automation might cause errors |
E88015 |
53415 | Response time for a SAS® Real-Time Decision Manager campaign increases significantly with each additional treatment when you use sort arbitration |
E88015 |
51764 | A campaign group opens slowly in SAS® Customer Intelligence Studio |
E88016 |
52038 | A deleted default value is still used when you execute a campaign in SAS® Customer Intelligence Studio |
E88016 |
53923 | SAS® Customer Intelligence Integration Utilities might fail when you import a campaign that contains two Map nodes or two Multi-Select nodes |
E88016 |
49633 | SAS® Real-Time Decision Manager might not populate the value for a decision campaign's custom details correctly |
E88017 |
53822 | You are unable to open a decision diagram that contains a Subdiagram node |
E88017 |
54521 | Performance is slow when you are editing a complex diagram in SAS® Customer Intelligence Studio |
E88017 |
54567 | SAS® Customer Intelligence Studio multi-select node returns incorrect results for some combinations of time zone and date |
E88017 |
54696 | The error "Invalid Expression" occurs when you create a calculated variable in an expression that includes multiple variable names that are similar |
E88017 |
51990 | Associations between SAS® Real-Time Decision Manager objects might be lost if you import them using separate SPK files |
E88017 |
54568 | Importing a SAS® Real-Time Decision Manager campaign that contains a data process might trigger an incorrect warning |
E88017 |
54407 | After you apply SAS® Marketing Automation Hot Fix E88015, treatments with values of 0 or 9 can no longer be exported |
E88017 |
56903 | Exporting Numeric custom detail tags fails and returns a syntax error in SAS® Marketing Automation |
E88017 |
55673 | The error "Publish failed to insert MARKETING_CELL records" occurs when you publish campaigns in SAS® Customer Intelligence |
E88018 |
55674 | Campaigns fail with deadlock errors when you publish user-defined fields in the Communication node to the Reporting Common Data Model |
E88018 |
NOTE: If you install this hot fix and have SAS Management Console installed, you must also install hot fix:
E90005 for SAS Management Console.
NOTE: If you install this hot fix and have SAS Marketing Optimization installed, you must also install hot fix:
G05011 for SAS Marketing Optimization.
|
|
D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |