Loading

Marketing Cloud Alert Manager Errors

Date de publication: Oct 13, 2022
Description

Table of Contents:

 

 

Alert Manager Overview


Since the July 2020 release, Marketing Cloud users are able to set up a feature called Alert Manager. Alert Manager allows users to configure a user as the designated email recipient for when Email Jobs go into an errored state. When an Email Send or Triggered Send gets stopped for any number of issues, we send a notification email to the designated email address with details on which send failed and what error occurred. Learn more about common errors below. To quickly find the section related to your error, search by the "Error Code" value you received in the email. If you haven't already done so, opt your account in to Alert Manager and reattempt the send in order to get details on why it is erring. Not seeing your Error Code? Create a Support case through Salesforce Help for further assistance.

 

 

How to Set a Designated Recipient in Alert Manager


Required Permissions to Perform These Steps:
  • Administration | Users | View
  • Administration | Account | View
  • Administration | General | Access
 
  1. Click your name in the upper right-hand corner of the screen
  2. Click Setup
  3. Search for "Alert Manager" in the Quick Find box
  4. Click Alert Manager
  5. If you have not yet selected a Recipient, you will be prompted to select one
  6. Select a user from the picklist 
  7. Click Save
  8. If you need to change the Recipient, Click Alert Manager
  9. Click Edit
  10. Pick a different user and Click Save

  


 

Error Codes


The following sections include a list of possible email error codes and relevant information to review if you receive an Alert Manager notification relating to any of these errors.

 

 

DE_BATCH_UPDATE_ERR


The DE_BATCH_UPDATE_ERR indicates an issue when attempting to update values in a data extension for a batch of subscribers in the affected job. This error is typically observed for emails containing InsertDE, UpdateDE, or UpsertDE AMPscript function calls.

Review the details of the error in the alert. The error includes the name of the data extension that failed to update and may contain more information about the reason the update failed. Some common subtypes of this error are outlined in the following table.
 
Error TextMeaningSuggested Action
Cannot insert duplicate key in object 'c123456.DataExtensionName'An InsertDE function call attempted to insert a record into a Data Extension with a value in the primary key field that exists on the Data Extension. When a primary key exists on a Data Extension, each record must have a unique primary key value.Review the InsertDE function calls in your email AMPscript. If records exist in the target data extension with the same primary key values, should this InsertDE function be replaced with an UpsertDE/UpdateDE function call? If you have multiple InsertDE function calls that could occur in the email at the same time for the same contact, consider consolidating the functions so that there is no potential overlap. 
Message: Invalid column name 'Column Name'An AMPscript function call has a column name in its function parameters that does not exist on the data extension it is attempting to update.Review any InsertDE, UpdateDE, or UpsertDE function calls in your email AMPscript that include the invalid column from the alert notification. If this column name does not exist on the data extension refactor your code so it no longer returns this error.
Cannot insert value NULL into column 'fieldname'. An AMPscript function call has a NULL value being inserted into a non-nullable field.If NULL values are not expected, review the AMPscript to ensure there are not possible NULL values being used. If NULL values are expected, make the Data Extension field nullable. 
SqlDateTime OverflowAn AMPscript function call is inserting or updating a date field with a date value that is not permitted.Review the values being passed. They must be between 1/1/1753 12:00:00 AM and 12/31/9999 11:59:59 PM.
Invalid Object Name 'c123456.DataExtensionName'An AMPscript function call is attempting to insert data into a Data Extension that does not exist by that name.Review the Data Extension name for accuracy. Also, confirm the Data Extension has not been deleted. Confirm the Data Extension has not been moved from a Business Unit to a Shared Folder, or the reverse.
  
 

​​​​OMM_ARCHIVE_ERR


An OMM_ARCHIVE_ERR error can occur in accounts that have the Email Archiving feature enabled. Generally this type of error is observed due to issues accessing SFTP folder locations that should have been set up to store archive data during provisioning. If you receive an alert regarding a job failing with this error code, please create a Support case through Salesforce Help for further assistance.

 

 

OMM_EXCLUDE_FILTER_ERR


An exclusion script containing AMPscript code can be configured for Triggered or User-Initiated Sends and also when configuring an Email Activity in Journey Builder. However, if the AMPscript does not compile your email job may be canceled with the error code OMM_EXCLUDE_FILTER_ERR. This error generally points to the location of the error, but not the cause. The Error Message and Additional Error Details should have more information.

Please review and test the AMPscript configured in your exclusion script for the affected send. If the AMPscript is valid it will compile without errors when you add it to a HTML-based email in Content Builder and Perform a Subscriber Preview and Test Send. 

See Exclude Subscribers from a Triggered or User-Initiated Send in Marketing Cloud and Create Exclusion Script for use in Journey Builder Email Activity for more information on how exclusion scripts are configured.

 

 

OMM_FUNC_EXEC_ERROR


The OMM_FUNC_EXEC_ERROR indicates there is an AMPscript exception with a specific function used within your email. Generally, the Error Message will indicate which function caused the email to fail. The Additional Error Details should go into further detail about what specifically failed with the AMPscript function. Review Marketing Cloud AMPscript OMM_FUNC_EXEC_ERROR for more details on common examples of errors.

 

 

OMM_FUNC_EXPR_INVALID


The error code OMM_FUNC_EXPR_INVALID is observed when an AMPscript function in your email code is unable to execute. Review the error message in the alert notification for further details. A common root cause for this error code is the passing of null or invalid values in the function parameters of a nested function call. For example, in the following error a Content Block is being referenced in an email, which contains a Field AMPscript function call that is being passed a null or empty AMPscript variable. 
ExactTarget.OMM.InvalidScriptException: The function expression is invalid. See inner exception for detail.
Script: ContentBlockbyKey("block-key")
Index: 3
ListID: 27
Error Code: OMM_FUNC_EXPR_INVALID
- from OMMCommon -->

--- inner exception 1---

ExactTarget.OMM.FunctionExecutionException: An error occurred when attempting to evaluate a ContentBlockByKey function call.
Function Call: ContentBlockbyKey("block-key")
See inner exception for details.
Error Code: OMM_FUNC_EXEC_ERROR
- from OMMCommon -->

--- inner exception 2---

ExactTarget.OMM.FunctionExecutionException: Invalid row (parameter 1) passed to Field function. Row is null or empty.
Function: Field(@AMPVariable,"FieldName")
Error Code: OMM_FUNC_EXEC_ERROR
- from OMMCommon

 

 

OMM_GETSUBLSTERR


The OMM_GETSUBLSTERR indicates there was an issue finding or building the send list. Ensure that the Data Extensions or Lists used for the send are still active. This includes Lists or Data Extensions used for suppression or exclusions. Ensure the sendable relationship for any Data Extension used in the send is using a text field when mapping to Subscriber Key and is the expected field name. The max Subscriber Key value must not exceed 254 characters or the email will fail.

 

 

OMM_INVALIDSTATE

 

The OMM_INVALIDSTATE error can occur when a Data Extension used as part of the send is deleted. This error can also occur when sending from an unverified From Address. Ensure the From Address is registered for your account. 
 

OMM_INVALID_FUNCT_PARAM


The error code OMM_INVALID_FUNCT_PARAM is observed when an AMPscript function in your email code is unable to execute due to invalid function parameters. Review the error message in the alert notification for the name of the AMPscript function in your email that is causing this issue. 

 

 

OMM_JOB_STATUS_INTERRUPT


The OMM_JOB_STATUS_INTERRUPT indicates there was an issue processing the send. This error may result in a partial send where some of your audience received the email but others did not. If you plan on sending to the remaining audience, cancel the job from the Tracking screen in Email Studio.

 

 

OMM_JOBDETAIL_ERR


The OMM_JOBDETAIL_ERR typically indicates there is a system issue with the send. This is not expected behavior and is addressed under this Known Issue. Follow the workaround in the Known Issue to resume the sends. 

 

 

OMM_SCRIPT_SYNTAX_ERR


An OMM_SCRIPT_SYNTAX_ERR error occurs when a syntax issue in your AMPscript code is encountered that prevents the code from compiling. For example an unexpected character or an invalid property or expression can cause the AMPscript to fail with this error. Please review your AMPscript code for the syntax error highlighted in the alert notification.

 

 

OMM_SUBBATCHERR

 

The OMM_SUBBATCHERR can happen when the Data Extension being used as part of a send is cleared/overwritten while the send is in progress. Ensure any Imports, Filters, or Query activities do not overwrite the Data Extension until the send is complete. This error can also occur if the Data Extension used in a send is renamed while the send is in progress.

 

OMM_VAR_SET_EXPR_INVALID


An OMM_VAR_SET_EXPR_INVALID is encountered when a SET statement in the AMPscript of your email cannot be compiled. As seen in the example provided below, this error can occur when you set a variable to an attribute that does not exist or the returned value of an AMPscript function call that fails during execution. As a result, you will often see OMM_SCRIPT_SYNTAX_ERR errors nested inside a OMM_VAR_SET_EXPR_INVALID error. Please review and test your email code to correct this error.
  
ExactTarget.OMM.InvalidScriptException: The SET variable value expression is invalid. See inner exception for detail.
Script: set @AMPVariable = [InvalidPropertyName]
Variable Name: @AMPVariable 
Index: 4
ListID: 0
Error Code: OMM_VAR_SET_EXPR_INVALID
- from OMMCommon -->

--- inner exception 2---

ExactTarget.OMM.InvalidScriptException: An error occurred when attempting to resolve a script expression. See inner exception for detail.
Script Expression: [InvalidPropertyName]
MemberID: XXXXXXX
JobID: 0
Error Code: OMM_SCRIPT_SYNTAX_ERR
- from OMMCommon -->

--- inner exception 3---

ExactTarget.OMM.InvalidScriptException: An unrecognized expression appears in a script block.
Script Expression: [InvalidPropertyName]
MemberID: XXXXXXX
JobID: 0
Error Code: OMM_SCRIPT_SYNTAX_ERR
- from OMMCommon



NOTE: If you still get the same error after making edits or removing the AMPscript, be sure to check both the text and html versions to ensure your content updated in both places. If the content is apart of a triggered send, be sure to publish a new version of the triggered send - Edit a Triggered Email.
Numéro d’article de la base de connaissances

000393037

 
Chargement
Salesforce Help | Article