Xml Syntax Error: Please Check the Xml Request to See if It Can Be Parsed
Error Codes in XML Response Documents
Types of errors found in a response document following a Transact XML submission
This article will show you the error codes that might be seen in a response document later on a Transact XML submission.
| Error/Warning Proper name | Description |
|---|---|
| SAVE_COLUMN_NOT_IN_DATABASE_WARNING = 7 | This is not an mistake, just a warning; one or more save columns that are not institute in the database. |
| SAVE_COLUMN_TOO_LONG = 8 | This is not an error, just a warning. |
| WARNING: Cavalcade: Torso | Torso was likewise long to save with contact (maximum characters: 255) |
| SUPPRESSED_EMAIL = 10 | Electronic mail address that is suppressed at the organization or arrangement level. |
GENERAL_ERROR = 1
This error is due to a server error. Likely, this is an exception, such as those shown in the table below.
| Exception | Clarification |
|---|---|
| Exception: javax.xml.demark.UnmarshalException: The entity proper name must immediately follow | Caused by defective CDATA tags around a value that includes an ampersand, or if you are passing the XML as part of the query cord, it can point that you lot demand to URL-encode the XML portion of the URL. |
| Exception: javax.xml.demark.UnmarshalException: Unexpected element {}:XXXXX | You are missing the slash symbol ( / ) in the closing tag (for example, ) of 1 of |
| Exception: javax.xml.bind.UnmarshalException: The element type "XXXXX" must be | The spelling of the closing tag for the specified element is different than its opening counterpart. |
| Exception: javax.xml.demark.UnmarshalException: XML document structures must start and end inside the same entity. | One of your XML declarations is missing its closing quotation or you are missing a bracket in the closing CDATA tag. Incorrect: |
| Exception: javax.xml.bind.UnmarshalException: Element type "XXXXX" must be followed by | In that location is a less-than symbol ( < ) not enclosed in CDATA tags inside one of your elements, or that was non added post-obit greater-than ( > ) symbol. |
| Exception: javax.xml.bind.UnmarshalException: a pseudo attribute name is expected. | The abaft question mark in the XML declaration string is missing: |
| Exception: javax.xml.bind.UnmarshalException: The value following "version" in the XML | There must exist quotation marks around the 1.0 in the XML declaration string, for case, <?xml |
| Exception: javax.xml.bind.UnmarshalException: Content is not immune in prolog. | You lot cannot include any content (text characters) outside of the tags |
| Exception: javax.xml.demark.JAXBException – with linked exception: [java.io.UTFDataFormatException: Invalid byte # of #-byte UTF-eight sequence.] | XML has a high-scrap grapheme in it that has not been ASCII-encoded. Accented and non-ISO |
| Exception: javax.xml.bind.UnmarshalException: The content of elements must consist of well-formed character information or markup. | In that location is likely a symbol or other consequence with an element name. For instance, entering the post-obit element <$AFW></$AFW> in the XML might crusade this error. |
| Exception: javax.xml.demark.UnmarshalException: Attribute name "XXXXX" associated with an element type "XXXXX" must be followed by the ' = ' character. | At that place is an extra discussion or character in an XML element tag that y'all should remove, every bit XML |
| Exception: javax.xml.bind.UnmarshalException: Expecting an opening quotation marking for attribute "XXXXX" associated with an element blazon "XXXXX". | An attribute has been associated with 1 of your XML elements that was not enclosed in quotation marks. For example, . You should remove the attribute and value from the Element tag. |
The document didn't parse. The message will ofttimes provide more information about the issue.
CampaignID ###### not found. Occurs when:
- Running against an Automated Message ID that doesn't be in your organization.
- The Group has non had time to synchronize (requires approximately 10 minutes).
- The Group has no mailing automation.
- There is a non-numeric graphic symbol in the Campaign ID element.
For a request (render mistake string):
- Campaign ID is missing
- Campaign ID is not numeric
- CampaignID + parsedCampaignID + not numeric
- CampaignID + CampaignID + not found
For an individual contact (return error cord):
- Missing e-mail
- Missing tag proper name
- Missing value
- Invalid electronic mail accost + emailAddress
- Invalid body type + bodyType
-
Access is not immune to awarding for this IP ###.###.###.###
-
Y'all do not have permission to admission Transact from your IP address, or you have added this IP address to your Security Settings (within Org Admin), but it has not had time to synchronize with Transact (requires approximately 10 minutes).
-
Access not allowed to application for this IP + IPAddress
-
Access is not allowed to this group mailing for this IP + IPAddress
No VMTA found for this Group - Conctact customer support for assist with this trouble.
Each mistake message besides contains a STATUS indicator that provides additional information regarding whether the email sent to your intended contact.
| STATUS Values | SEND_STATUS Values |
|---|---|
| 0 – no errors are encountered during the ship; all contacts sent. | 0 – no errors are encountered during the send. |
| 1 – encountered errors during the send; some or all contacts were not sent. | 1 – error are encountered during the send, transport will not be retried. |
| 2 – encountered errors with the XML submission; no contacts were sent; no contact error details | 2 – request received; ship cached for later send. |
Updated over 1 year ago
beckersigntearame.blogspot.com
Source: https://developer.goacoustic.com/acoustic-campaign/docs/error-codes-in-xml-response-documents
0 Response to "Xml Syntax Error: Please Check the Xml Request to See if It Can Be Parsed"
Post a Comment