SAS Digital Marketing might fail to record click events for e-mails in the SAS Digital Marketing response tables. When this problem happens, the Web application server that contains the tracking servlet (bess.war) writes an error in its log similar to the following one:
[MM/DD/YY hh:mm:ss:xxx EDT] 0000006e SystemOut O Unable to execute for an
undetermined reason. SQL passthru expression contained these errors: ERROR: The
following columns were not found in the contributing tables: Browser, content,
link, linkid, RemoteIPAddress
This problem happens when the PreventDDL=True server property is set. This property is designed to improve security of the SAS Digital Marketing response table by disallowing updates to the table. If you are using this property, ensure that all tracked variables that you want to use are created using the SAS Digital Marketing broadcast creation wizard. If subsequent tracked variables are added to the broadcast via the editor or externally, then you must manually create the appropriate columns in the SAS Digital Marketing response table. If you do not create the columns manually, the click events are not recorded.
The hot fix allows for the creation of standard columns in the response table, limited to: BESSEVENT, BESSTIME, JAVATIME, REMOTEHOST, REMOTEUSER, REMOTEIPADDRESS, CONTENT,LINKID, LINK, BROWSER, AOL, CT, APPID, RSS, ITEM, BROADCAST, RTC, S1, MM_LAT, MM_LONG, MM_ZIP, MM_AREA, MM_CITY, MM_COUNTRY
A hot fix for SAS Digital Marketing 5.3 is available upon request from Technical Support.
For SAS Digital Marketing 5.4_M1, click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| SAS System | SAS Digital Marketing | Microsoft® Windows® for 64-Bit Itanium-based Systems | 5.3 | 5.41 | 9.2 TS2M3 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Datacenter 64-bit Edition | 5.3 | 5.41 | 9.2 TS2M3 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Enterprise 64-bit Edition | 5.3 | 5.41 | 9.2 TS2M3 | 9.3 TS1M0 |
| Microsoft Windows XP 64-bit Edition | 5.3 | 5.41 | 9.2 TS2M3 | 9.3 TS1M0 |
| Microsoft® Windows® for x64 | 5.3 | 5.41 | 9.2 TS2M3 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Datacenter Edition | 5.3 | 5.41 | 9.2 TS2M3 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Enterprise Edition | 5.3 | 5.41 | 9.2 TS2M3 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Standard Edition | 5.3 | 5.41 | 9.2 TS2M3 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 for x64 | 5.3 | 5.41 | 9.2 TS2M3 | 9.3 TS1M0 |
| Microsoft Windows Server 2008 | 5.3 | 5.41 | 9.2 TS2M3 | 9.3 TS1M0 |
| Microsoft Windows Server 2008 for x64 | 5.3 | 5.41 | 9.2 TS2M3 | 9.3 TS1M0 |
| Microsoft Windows XP Professional | 5.3 | 5.41 | 9.2 TS2M3 | 9.3 TS1M0 |
| Windows 7 Enterprise 32 bit | 5.3 | 5.41 | 9.2 TS2M3 | 9.3 TS1M0 |
| Windows 7 Enterprise x64 | 5.3 | 5.41 | 9.2 TS2M3 | 9.3 TS1M0 |
| Windows 7 Professional 32 bit | 5.3 | 5.41 | 9.2 TS2M3 | 9.3 TS1M0 |
| Windows 7 Professional x64 | 5.3 | 5.41 | 9.2 TS2M3 | 9.3 TS1M0 |
| Windows 7 Ultimate 32 bit | 5.3 | 5.41 | 9.2 TS2M3 | 9.3 TS1M0 |
| Windows 7 Ultimate x64 | 5.3 | 5.41 | 9.2 TS2M3 | 9.3 TS1M0 |
| Windows Vista | 5.3 | 5.41 | 9.2 TS2M3 | 9.3 TS1M0 |
| Windows Vista for x64 | 5.3 | 5.41 | 9.2 TS2M3 | 9.3 TS1M0 |
| 64-bit Enabled AIX | 5.3 | 5.41 | 9.2 TS2M3 | 9.3 TS1M0 |
| 64-bit Enabled HP-UX | 5.3 | 5.41 | 9.2 TS2M3 | 9.3 TS1M0 |
| 64-bit Enabled Solaris | 5.3 | 5.41 | 9.2 TS2M3 | 9.3 TS1M0 |
| HP-UX IPF | 5.3 | 5.41 | 9.2 TS2M3 | 9.3 TS1M0 |
| Linux | 5.3 | 5.41 | 9.2 TS2M3 | 9.3 TS1M0 |
| Linux for x64 | 5.3 | 5.41 | 9.2 TS2M3 | 9.3 TS1M0 |
| Solaris for x64 | 5.3 | 5.41 | 9.2 TS2M3 | 9.3 TS1M0 |
*
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.
