7 months ago


Transact XML Element:

Transact XML Element: ERROR_STRING Usage: Required Sequence: after ERROR_CODE Description: Error message generated for the specific recipient. Element type: Complex Datatype: string Default Value: N/A Limit: 255 characters Values: Error message text. Occurrence indicators Attributes Note: None None None Example: Campaign ID is missing See: Error Codes in XML Response documents (next section). 86 1-866-SILVPOP (745-8767) © 2012 Silverpop Systems Inc. All rights reserved.

Transact XML Error Codes in XML Response Documents You may receive the following types of errors in a Response Document following a Transact XML submission. Notification Only • SAVE_COLUMN_NOT_IN_DATABASE_WARNING = 7 This is not an error, just a warning; one or more save columns not found in the database • SAVE_COLUMN_TOO_LONG = 8 This is not an error, just a warning; • WARNING: COLUMN: BODY Body was too long to save with contact (maximum characters: 255) • SUPPRESSED_EMAIL = 10 Email address suppressed at the system or organization level. Errors Requiring Action • GENERAL_ERROR = 1 This is due to server error (likely an exception, such as those shown below). 1. Exception:javax.xml.bind.UnmarshalException: The entity name must immediately follow the Ampersand character (&) in the entity reference. b. Caused by lacking CDATA tags around a value that includes an ampersand, or (if you are passing the XML as part of the query string) it can indicate that you need to URL-encode the XML portion of the URL. 2. Exception:javax.xml.bind.UnmarshalException: Unexpected element {}:XXXXX a. You are missing the slash symbol ( / ) in the closing tag (for example, )of one of your elements which is specified in the XXXXX area of the error. 3. Exception:javax.xml.bind.UnmarshalException: The element type "XXXXX" must be terminated by the matching end-tag "". 87 1-866-SILVPOP (745-8767) © 2012 Silverpop Systems Inc. All rights reserved.