Problem Note 60249: The SAS® Management Console Schedule Manager plug-in cannot handle flows with 1_ as a prefix when you schedule campaigns or communications
When you schedule campaigns or communications in SAS Management Console, the Schedule Manager plug-in cannot handle flows that have 1_ as a prefix. When the problem occurs, you receive the following error message:
Specify a deployed flow name using alphanumeric characters or underscores (_). The name cannot be blank
or contain spaces.
This problem happens when you perform steps similar to the following:
- in SAS® Customer Intelligence Studio, change your communication and campaign codes in the Business Context properties to values that have 1_ as the prefix, similar to those shown below:
- Schedule your campaigns or communications by sending them to SAS Management Console. When you do this, the campaign or communication shows 1_CAMPxxxx (where xxxx is a number) in the flow name, similar to the example below.
- Edit the flow properties in the Schedule Manager plug-in.
- Move to another tab in the properties dialog box. When you do this, you receive the error listed earlier in this note.
To avoid this problem, do not use 1_ as a prefix for your campaign or communication codes.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Customer Intelligence Studio | Microsoft® Windows® for x64 | 6.3 | | | |
Microsoft Windows 8 Enterprise 32-bit | 6.3 | | | |
Microsoft Windows 8 Enterprise x64 | 6.3 | | | |
Microsoft Windows 8 Pro 32-bit | 6.3 | | | |
Microsoft Windows 8 Pro x64 | 6.3 | | | |
Microsoft Windows 8.1 Enterprise 32-bit | 6.3 | | | |
Microsoft Windows 8.1 Enterprise x64 | 6.3 | | | |
Microsoft Windows 8.1 Pro 32-bit | 6.3 | | | |
Microsoft Windows 8.1 Pro x64 | 6.3 | | | |
Microsoft Windows 10 | 6.3 | | | |
Microsoft Windows 95/98 | 6.3 | | | |
Microsoft Windows 2000 Advanced Server | 6.3 | | | |
Microsoft Windows 2000 Datacenter Server | 6.3 | | | |
Microsoft Windows 2000 Server | 6.3 | | | |
Microsoft Windows 2000 Professional | 6.3 | | | |
Microsoft Windows NT Workstation | 6.3 | | | |
Microsoft Windows Server 2003 Datacenter Edition | 6.3 | | | |
Microsoft Windows Server 2003 Enterprise Edition | 6.3 | | | |
Microsoft Windows Server 2003 Standard Edition | 6.3 | | | |
Microsoft Windows Server 2003 for x64 | 6.3 | | | |
Microsoft Windows Server 2008 | 6.3 | | | |
Microsoft Windows Server 2008 R2 | 6.3 | | | |
Microsoft Windows Server 2008 for x64 | 6.3 | | | |
Microsoft Windows Server 2012 Datacenter | 6.3 | | | |
Microsoft Windows Server 2012 R2 Datacenter | 6.3 | | | |
Microsoft Windows Server 2012 R2 Std | 6.3 | | | |
Microsoft Windows Server 2012 Std | 6.3 | | | |
Microsoft Windows XP Professional | 6.3 | | | |
Windows 7 Enterprise 32 bit | 6.3 | | | |
Windows 7 Enterprise x64 | 6.3 | | | |
Windows 7 Home Premium 32 bit | 6.3 | | | |
Windows 7 Home Premium x64 | 6.3 | | | |
Windows 7 Professional 32 bit | 6.3 | | | |
Windows 7 Professional x64 | 6.3 | | | |
Windows 7 Ultimate 32 bit | 6.3 | | | |
Windows 7 Ultimate x64 | 6.3 | | | |
Windows Millennium Edition (Me) | 6.3 | | | |
Windows Vista | 6.3 | | | |
Windows Vista for x64 | 6.3 | | | |
64-bit Enabled AIX | 6.3 | | | |
64-bit Enabled Solaris | 6.3 | | | |
HP-UX IPF | 6.3 | | | |
Linux for x64 | 6.3 | | | |
Solaris for x64 | 6.3 | | | |
*
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: | Problem Note |
Priority: | high |
Date Modified: | 2017-07-19 10:55:07 |
Date Created: | 2017-04-04 12:40:33 |