Exception Messages
Due to the configurable nature of Emplifi Agent and the range of situations that can generate the same exception in a variety of ways, only the more common explanations and resolutions are provided.
If you found this topic while searching for a particular LCID using the Help Search, scroll down to the highlighted LCID.
LCID | Exception Message | Explanation of the Exception | Action to Resolve Exception | Resolved By | Fulfillment Type |
---|---|---|---|---|---|
LC009873 | Enclosure: {1} has been picked or allocated to another batch since processing began | While the Batch process was running an outside process "grabbed" the enclosure or someone manually picked the enclosure. | Nothing to correct. Verify that Fulfillment filters are correct if attempting to segregate processing. Administrator can run a report and filter to isolate batches to reveal what is happening. | Administrator | Case Enclosure |
LC009817 | Enclosure: {1} Enclosure Code does not specify an Enclosure Type | An enclosure type needs to be specified and it is either missing or invalid. | Go to Administration > Company Setup > Fulfillment > Enclosure Codes. On the Enclosure Codes page, the Enclosure Type field is blank or invalid and requires a valid value. | Administrator | Case Enclosure |
LC009818 | Enclosure: {1} does not specify an Enclosure Code. | This relates to there being no enclosure_code on the CASE enclosure. The Enclosure Code field is blank or null on the case. | Only happens when there is a "bad" import or there was a change made to the database outside of Emplifi Agent. When adding enclosures, it is necessary to specify an enclosure code. Go to Administration > Company Setup > Fulfillment > Additional Enclosure Definition > Enclosure Attribute (J) Categories > Checking Account. A code may be set up incorrectly or may not be set up at all. The value corresponding to "Default Code" or "InfoCenter Code" may be blank or may not be set to the correct value. | Agent | Case Enclosure |
LC009819 | Enclosure: {1} has not been marked Ready to Pick | This enclosure needs to be marked as "Ready to Pick" before it can be used. This exception is a warning and serves as a reminder to mark the enclosure as "Ready to Pick". | Clear the Requires Approval check box on the enclosure code in Company Setup or run the Enclosure Approval Utility and mark the enclosure as "Ready to Pick". | Agent | Case Enclosure |
LC009820 | Enclosure: {1} has not been Approved | The enclosure needs to be approved using the Enclosure Approval Utility. This is not an error; this message warns the user that approval is required. This is a configurable feature (common warning). | Clear the Requires Approvalcheck box on the enclosure code in Company Setup or run the Enclosure Approval Utility and mark the enclosure as "Approved". | Agent | Case Enclosure |
LC009821 | Non-check enclosure not supported for this Check Export. | The Check Export option only processes enclosures with a check Enclosure Type. This mode of Create Batch requires you to use filters to select cases with only checks or letter checks on them. This message indicates that an enclosure was found that contained something other than checks or letter checks. | The filter may be wrong. This mode is run by an expert agent and assumes the only enclosure in the batch are checks from a specific checking account in which filtering is used to only include desired cases. Go to Utilities > Fulfillment Utilities > Manage Batches. Within the Special Processing Mode section, the Single Checking Account, No Documents, Expert Only Mode check box is selected. This is a special high-performance processing mode, where the physical documents are being produced by a third-party outside the Emplifi Agent system. It assumes the Filter tab is selecting a subset of Cases containing letter and checks only, all from the same Checking Account (specified in the next option). No letters are prepared, and no check documents are created, but check numbers are assigned to the next available for the account, and the case enclosures are picked, and the letters marked sent. | Administrator | Case Enclosure |
LC009822 | Enclosure: {1} references missing/sent letter_seq | An Enclosure, {1} = enclosure sequence, is associated with a letter that was already sent or a letter that has been deleted. | Find the enclosure on the case that is either not linked to any letter or linked to a letter that has already been sent/deleted. This is normally caused by an enclosure getting associated with an email response. There are other situations that can cause this exception; however, this is the most common. | Agent | Case Enclosure |
LC009823 | Enclosure: {1} 'SEND TO' value does not match the 'SEND TO' value for its linked letter, as required by the enclosure definition. | When attaching enclosure to case ensure Send To address matches Send To on letter. | Open the case, ensure enclosure Send To address matches the Send To address for the letter. | Administrator | Case Enclosure |
LC009824 | Enclosure:{1}is associated with an Email letter | Enclosures are not able to be sent via email. | The fix is to open the case, change the letter to non-email or remove enclosure. More resolutions are available however this is the most common. | Agent | Case Enclosure |
LC009825 | Enclosure: {1} is associated with a Related Letter | A "Related Letter" is a special type of letter (defined by its Letter Type Code), that is sent with another letter in the same batch, almost like an enclosure. The "Related Letters" cannot have enclosures themselves. | Open the Case, change enclosure to point to the base letter and NOT the related letters. Other solutions exist; however, this is the most common. | Agent | Case Enclosure |
LC009826 | Enclosure: {1} is not associated to any letter, and letter to the same Send To Address is an Email letter | The exception occurs when trying to auto-associate enclosure to letters during Batch Fulfillment. Enclosures are not able to be sent via email. The enclosure in question {1} is not associated with a letter. The logic finds a letter on the same case going to the same Send To Address, that happens to be an Email Letter. Emails cannot have enclosures and do not include any unsent parts of the Case in this batch (assuming it is fixed before the next batch is run). | Open case, determine if the Send To addresses are noted, or there is a wrong letter type. This exception is usually attributed to a complex situation on the case and most often requires PS assistance to resolve. | Agent | Case Enclosure |
LC009827 | Enclosure: {1} is not associated to any letter, and letter to the same Send To Address has already been prepared | It is invalid to auto-link an enclosure to a letter where the letter was already prepared, since that means the letter may not contain a reference to this enclosure. Prepping a letter on a case does auto-assign also, so this means the enclosure was added later. This is allowed, but it must be manually linked to the letter, and it's assumed the text of the letter does not mention the enclosure, or already does. | The enclosure may have been added after the letter was prepared; if this doesn't invalidate the letter, all that's needed is to reference the letter_seq in the enclosure. | Agent | Case Enclosure |
LC009828 | Enclosure:{1} is required to be linked to a letter and it is not associated to any letter, and no Letter going to that Case/Send To Address is in this batch | The exception occurs because the enclosure {1} that is configured to be linked to a letter is not linked to a letter and there is no letter to be linked to. | This is a configured setting on an enclosure and the enclosure needs to be linked to the letter. The letter may have not been included or the Send To address is incorrect. (For example: a brochure was added and the link to letter is required and there is not a letter on the case.) | Agent | Case Enclosure |
LC009829 | Enclosure: {1} sending to non-existent Address ID: {1} | The address_id on the enclosure is "bad", either because of a bad import or there was a change in database outside of Emplifi Agent, or someone deleted the address. | Go to the case, navigate to the enclosure on that case and correct the Send To address. | Agent | Case Enclosure |
LC009830 | Enclosure: {1} does not specify a Send To Address | Enclosure added to a case does not specify the Send To address on the case enclosure | Navigate to the case, select enclosure within the case, enter value in the Send To field. | Agent | Case Enclosure |
LC010085 | No Label Standard Letter ID defined for Label | This is an admin error an agent cannot resolve. | Navigate to Administration > Company Setup > Fulfillment > Enclosure Codes. Add the missing "Label Std Letter." | Administrator | Labels |
LC009831 | No Label Standard Letter ID defined for Label Enclosure Code: {1} | This is an admin error an agent cannot resolve. | Navigate to Administration > Company Setup > Fulfillment > Enclosure Codes. Add the missing "Label Std Letter." | Administrator | Labels |
LC009832 | No Label Standard Letter ID defined for Enclosure Code: {1} | This is an admin error an agent cannot resolve. | Navigate to Administration > Company Setup > Fulfillment > Enclosure Codes. Add the missing "Label Std Letter." | Administrator | Labels |
LC009835 | Invalid Label Standard Letter ID: {1} See related error message this batch. | There is an underlying error and the text "See related error message this batch" references an earlier problem that once the root cause is resolved this error will also be resolved. | Resolve root case error related to the label processing and the specified "Standard Letter ID" | Agent | Labels |
LC009833 | Letter: {1} with Letter Type Code: {2} has an invalid Label Standard Letter ID: {3} See related error message this batch. | There is an underlying error and the text "See related error message this batch" references an earlier problem that once the root cause is resolved this error will also be resolved. | Resolve root case error related to the label processing and the specified "Standard Letter ID." This is an enclosure calling for the use of a label that is already has an existing problem specified elsewhere in the batch. | Agent | Labels |
LC009834 | Enclosure: {1} with Enclosure Code: {2} has an invalid Label Standard Letter ID: {3} See related error message this batch. | There is an underlying error and the text "See related error message this batch" references an earlier problem that once the root cause is resolved this error will also be resolved. | Resolve root case error related to the label processing and the specified "Standard Letter ID." This is an enclosure calling for the use of a label that already has an existing problem specified elsewhere in the batch. | Agent | Labels |
LC009838 | Unknown Label Standard Letter ID: {1} | There is a configuration calling for a label which is defined by "Standard Letter ID" and the label is either missing, incorrect, or deleted. | Check label configuration in the various locations: letter type label or enclosure type label. | Agent | Labels |
LC009836 | Letter: {1} with Letter Type Code: {2} has an unknown Label Standard Letter ID: {3} | A letter type calling for a label which is defined by "Standard Letter ID" and the label is either missing, incorrect, or deleted. | Letter type code label has an incorrect "Standard Letter ID". Navigate to Administration > Company Setup > Fulfillment > Letter Types. Tab: Letter Type, and "Label Std Letter" field is incorrect. | Administrator | Labels |
LC009837 | Enclosure: {1} with Enclosure Code: {2} has an unknown Label Standard Letter ID: {3} | An enclosure code is calling for a label which is defined by "Standard Letter ID" and the label is either missing, incorrect, or deleted. | Letter type code label has an incorrect "Standard Letter ID". Navigate to Administration > Company Setup > Fulfillment > Enclosures Codes. Select a code within enclosures. Tab: Enclosure, and "Label Std Letter" field is incorrect. | Administrator | Labels |
LC009841 | Label Standard Letter ID: {1} is not Document Type 3 - Label | This exception refers to the Letter Format defined by the drop down on the "Standard Letters (H02)" Code the Enclosure is pointing to. The value for the field should be Label. | Navigate to Administration > Company Setup > Fulfillment > Standard Letters (H02).Select Tab: Standard Letter. Verify the value found in the Letter Format field. It should be the value of "Label" (assuming the correct standard letter ID was intended). | Agent | Labels |
LC009839 | Letter: {1} with Letter Type Code: {2} the Label Standard Letter ID: {3} is not Document Type 3 - Label | This exception refers to the Letter Format defined by the drop down on the "Standard Letters (H02)" Code the Enclosure is pointing to. The value for the field should be Label. The standard letter on the letter type code is incorrect. | Navigate to Administration > Company Setup > Fulfillment > Standard Letters (H02). Tab: Standard Letter; Field: Letter Format should be the value of "Label" (assuming this is the correct standard letter ID intended). | Administrator | Labels |
LC009840 | Enclosure: {1} with Enclosure Code: {2} the Label Standard Letter ID: {3} is not Document Type 3 - Label | This exception refers to the Letter Format defined by the drop down on the "Standard Letters (H02)" Code the Enclosure is pointing to. The value for the field should be Label. The "Label Std Letter" on enclosure is not marked as a label. | Navigate to Administration > Company Setup > Fulfillment > Standard Letters (H02). Tab: Standard Letter; Field: Letter Format should be the value of "Label" (assuming this is the correct standard letter ID intended). | Administrator | Labels |
LC009844 | Label Standard Letter ID: {1} is missing the Standard Letter File Name | The Standard Letter File Name is incorrectly spelled or non-existent. | Navigate to Administration > Company Setup > Fulfillment > Standard Letters. Drill down to the sub folders, then code. Verify the Standard Letter tab within the designated code that is missing, if it has a Standard Letter File Name designated. Confirm the file exists in the <folder>. Verify referenced Standard Letter File name is spelled correctly. The Standard Letter File Name is missing. | Agent | Labels |
LC009842 | Letter: {1} with Letter Type Code: {2} the Label Standard Letter ID: {3} is missing the Standard Letter File Name | The Standard Letter File Name is incorrectly spelled or non-existent. | Navigate to Administration > Company Setup > Fulfillment > Standard Letters. Drill down to the sub folders, then code. Verify the Standard Letter tab within the designated code that is missing, if it has a Standard Letter File Name designated. Confirm the file exists in the <folder>. Verify referenced Standard Letter File name is spelled correctly. The Standard Letter File Name is missing. | Administrator | Labels |
LC009843 | Enclosure: {1} with Enclosure Code: {2} the Label Standard Letter ID: {3} is missing the Standard Letter File Name | The Standard Letter File Name is incorrectly spelled or non-existent. | Navigate to Administration > Company Setup > Fulfillment > Standard Letters. Drill down to the sub folders, then code. Verify the Standard Letter tab within the designated code that is missing, if it has a Standard Letter File Name designated. Confirm the file exists in the <folder>. Verify referenced Standard Letter File name is spelled correctly. The Standard Letter File Name is missing. | Administrator | Labels |
LC009847 | Label Standard Letter ID: {1} could not read the Standard Letter File: {2} Error: {3} | There is a problem with the file designated by "Label Std Letter". | Navigate to Administration > Company Setup > Fulfillment > Letter Types. Within the Standard Letter tab, the file identified by the "Standard Letter File Name" may not be located in the folder designated by this field or the file name is not correct. Select code corresponding to the checking enclosure and verify. Common result pertains to file permits. | Agent | Labels |
LC009845 | Letter: {1} with Letter Type Code: {2} the Label Standard Letter ID: {3} could not read the Standard Letter File: {4} Error: {5} | There is a problem with the file designated by "Label Std Letter". | Navigate to Administration > Company Setup > Fulfillment > Letter Types. Within the Standard Letter tab, the file identified by the "Standard Letter File Name" may not be located in the folder designated by this field or the file name is not correct. Select code corresponding to the checking enclosure and verify. Common resolution pertains to file permits. | Administrator | Labels |
LC009846 | Enclosure: {1} with Enclosure Code: {2} the Label Standard Letter ID: {3} could not read the Standard Letter File: {4} Error: {5} | There is a problem with the file designated by "Label Std Letter". | Navigate to Administration > Company Setup > Fulfillment > Letter Types. Within the Standard Letter tab, the file identified by the "Standard Letter File Name" may not be in the folder designated by this field or the file name is not correct. Select code corresponding to the checking enclosure and verify. Common result pertains to file permits. | Administrator | Labels |
LC009848 | Check with null/zero value is invalid. | Checks must have a fixed value printed, zero is not acceptable. | Open the Case / Enclosure shown and enter the Value of the Check. | Agent | Checks |
LC009728 | Checking account not specified for enclosure: {1} | When a check is an enclosure, the appropriate checking account needs to be included. | Navigate to Administration > Company Setup > Fulfillment > Enclosure Codes and specify the "Checking Account" field. | Administrator | Checks |
LC009850 | Checking account not supported for this Check Export: {1} | This applies when the "Single Checking Account, Export Only Mode" option is in use. A different checking account is noted on the enclosure in the batch than what was specified in the Manage Batch utility. Filters must be used to limit the cases. | Navigate to Utilities > Fulfillment Utilities > Manage Batches. Within the Special Processing Mode section, select the Single Checking Account, No Documents, Expert Only Mode check box. This is a special high-performance processing mode, where the physical documents are being produced by a third-party outside the Emplifi Agent system. It assumes the Filter tab is selecting a subset of Cases containing letter and checks only, all from the same Checking Account (specified in the next option). No letters are prepared, and no check documents are created, but check numbers are assigned to the next available for the account, and the case enclosures are picked, and the letters marked sent. | Administrator | Checks |
LC009851 | Check printed with letter does not reference one of that type. | The exception occurs when an Enclosure defined as a "Letter Check" type is linked to a Letter that is not defined as a "Letter Check" type. | Open the Case and navigate to the enclosures on the case. Verify and correct either the Letter or the Enclosure, whichever is wrong. | Agent | Checks |
LC010306 | Check printed with letter does not match Letter Type Code values, Check Letter Type Code: {1} vs Case Letter Type Code: {2} nor Standard Letter Type Code: {3} | Applies to "Letter Check" Letter + Enclosure combos. The Letter Type Code on the Checking Account related to the Enclosure (check) does not match neither the Letter Type Code on the related Letter on the Case, nor the Letter Type Code on the Standard Letter ID table defining that Letter. (This is so clients can set up different "natures" of Letter+Check and agents do not cross-wire them, so the combo is nonsense.) | Open the Case and navigate to the enclosures on the case. Verify and correct either the Letter or the Enclosure, whichever is wrong. There is a combination that is valid: IE Canadian letter/Canadian check, US letter / US check and a combination that is invalid: IE US letter / Canadian check. | Agent | Checks |
LC009853 | Checking account {1} doesn't exists. | The checking account is not set up or designated. The checking account used for checks and coupons is just a standard category code. You add one code for each checking account | Navigate to Administration > Company Setup > Fulfillment > Additional Enclosure Definition > Enclosure Attribute Categories Checking Account. | Administrator | Checks |
LC009854 | Checking account {1} marked as 'bad'. See exception messages before. | To avoid repeating the same message repeatedly, once a problem is found related to a specific checking account, all enclosures trying to produce checks against that account are excluded from the batch. | Look elsewhere in the batch errors for the root cause of the problem related to the checking account. Correct the root cause and subsequent error will be resolved. There is nothing wrong with the enclosure and it is explained elsewhere in the batch. Fix the root cause and this error will self-resolve. | Administrator | Checks |
LC010086 | Warning: Inconsistent Check Number Format found, using first non-empty one. Checking Account: {1} First Enclosure: {2} Format: {3} Other Enclosure: {4} Format: {5} | The exception occurs when the logic has detected 2 (or more) different formats were specified for the same checking account, which is bad. Checks and Coupon numbers have "Formats" defined at the Enclosure Code level. | Navigate to Administration > Company Setup > Fulfillment > Enclosure Codes. Find and fix all enclosure codes that share the same checking account. | Agent | Checks |
LC009855 | Checking account {1} doesn't exists. | The checking account is not set up or designated. The checking account used for checks and coupons is just a standard category code. You add one code for each checking account. It is specified, however missing or deleted. | Navigate to Administration > Company Setup > Fulfillment > Additional Enclosure Definition > Enclosure Attribute Categories Checking Account. Enter the Standard Letter ID code of the letter used to print checks for this checking account in the Description 2 field of the code definition. | Administrator | Checks |
LC009856 | Checking account {1} doesn't provide standard letter ID. | When creating a checking account, a standard letter ID must also be included. The first time you create a checking account you may have to first create the Checking Account category. The Checking Account category is called JFA. When defining the actual code values for each checking account, the only special step you need to take is to enter the Standard Letter ID code of the letter used to print checks for this checking account in the Description 2 field of the code definition. | Navigate Administration > Company Setup > Fulfillment > Additional Enclosure Definition > Enclosure Attribute Categories Checking Account. A code may not be set up correctly or may not be set up at all. | Administrator | Checks |
LC009857 | Unknown Check's Standard Letter ID: {1} for checking account {2}. Check custom config settings. | When creating a checking account, a standard letter ID must also be included. The first time you create a checking account you may have to first create the Checking Account category. The Checking Account category is called JFA. When defining the actual code values for each checking account, the only special step you need to take is to enter the Standard Letter ID code of the letter used to print checks for this checking account in the Description 2 field of the code definition. | Navigate to Administration > Company Setup > Fulfillment > Additional Enclosure Definition > Enclosure Attribute Categories Checking Account. A code may not be set up correctly or may not be set up at all. | Administrator | Checks |
LC009858 | Check's Standard Letter ID: {1} is not Document Type 2 - Formatted Text, the only one supported currently. | Printed checks only support HTML (Doc Type 2), the one specified for this account is not that. | Verify that the check configuration is correct for the checking account related to the standard letter. | Administrator | Checks |
LC009859 | Check's Standard Letter ID: {1} does not have any required Standard Letter File Name provided. | When creating a checking account, a standard letter ID must also be included. The first time you create a checking account you may have to first create the Checking Account category. The Checking Account category is called JFA. When defining the actual code values for each checking account, the only special step you need to take is to enter the Standard Letter ID code of the letter used to print checks for this checking account in the Description 2 field of the code definition. | Navigate to Administration > Company Setup > Fulfillment > Additional Enclosure Definition > Enclosure Attribute Categories Checking Account. A code may not be set up correctly or may not be set up at all. | Administrator | Checks |
LC009860 | Could not open Check's Standard Letter Path: {1} File: {2} Standard Letter ID: {3} Error: {4} | Letter may not exist, the letter name may be misspelled, the path to the letter may be invalid or incorrect preventing the file from being found. (Or, more likely there is a Windows Permission problem.) | Navigate to Administration > Company Setup > Fulfillment > Standard Letters. Verify Category Name and Category Label are correct. | Administrator | Checks |
LC009861 | Check template {1} for account: {2} doesn't have the <DocumentNumber/> tag. | Checks and coupons must have the tag <DocumentNumber/> in the HTML so the logic knows where to embed the generated check/coupon number. Otherwise, it won't work without it. | Special HTML tag is needed. Verify that the correct Standard Letter ID is being used. | Administrator | Checks |
LC009862 | Check template {1} for account: {2} doesn't have letter type code. | Letter Type Codes are typically used to differentiate between types of media, such as different letterheads or paper stock, labels, envelopes, or emails. Every Standard Letter that you define must be assigned a specific letter type code. During batch fulfillment processing, each letter type can be created as a separate print document so that it can be sent to the appropriate printer, or so that other special handling can be applied. | Navigate to Administration > Company Setup > Fulfillment > Letter Types. Verify letter type exists. Navigate to Administration > Company Setup > Fulfillment > Letter Types > "Checks-Use for checks". Verify Fulfillment type has a valid selection. | Administrator | Checks |
LC009863 | Coupon with null/zero value is invalid. | Coupons must have a value associated with them and are not to be blank or equal zero. | Open case, navigate to the enclosure on the case and enter the correct value of the coupon. If this is a fixed value coupon, you may also need to check the enclosure code configuration. (Navigate to Administration > Company Setup > Fulfillment > Enclosure Codes.) | Agent | Coupons |
LC009730 | Coupon template doesn't specified for enclosure {1} | When an enclosure is a coupon, the appropriate checking account needs to be included. | Navigate to Administration > Company Setup > Fulfillment > Enclosure Codes and specify the coupon template / Checking Account field. Provide an appropriate Coupon Std Letter. | Administrator | Coupons |
LC010087 | Coupon printed with letter does not reference one of that type | Similar to the message for Letter + Check above, however with this exception, this is for Letter + Coupon. The exception occurs when an Enclosure defined as a "Letter Coupon" type is linked to a Letter that is not defined as a "Letter Coupon" type. | Open the Case and navigate to the enclosures on the case. Verify and correct either the Letter or the Enclosure, whichever is wrong. | Agent | Coupons |
LC010088 | Coupon printed with letter does not match Letter Type Code values: {1} vs {2} | Similar to the message for Letter + Check above, however with this exception, this is for Letter + Coupon. Applies to "Letter Check" Letter + Enclosure combos. The Letter Type Code on the Checking Account related to the Enclosure (check) matches neither the Letter Type Code on the related Letter on the Case, nor the Letter Type Code on the Standard Letter ID table defining that Letter. (This is so clients can set up different "natures" of Letter+Check and agents don't cross-wire them- so the combo is nonsense.) | Open the Case and navigate to the enclosures on the case. Verify and correct either the Letter or the Enclosure, whichever is wrong. There is a combination that is valid: IE Canadian letter/Canadian check, US letter / US check and a combination that is invalid: IE US letter / Canadian check. | Agent | Coupons |
LC009864 | Standard Letter ID {1} marked as 'bad'. See exception messages before | Relating to Coupons, earlier in the Batch the Coupon Template (Standard Letter ID of the Coupon HTML layout) has some error so It cannot be prepared. To avoid repeating the same message repeatedly, once a problem is found related to a specific coupon template, all enclosures trying to produce coupons against that template are excluded from the batch. | Look elsewhere in the batch errors for the root cause of the problem related to the checking account. Correct the root cause and subsequent error will be resolved. There is nothing wrong with the enclosure and it is explained elsewhere in the batch. Fix the root cause and this error will self-resolve. | Agent | Coupons |
LC009865 | Warning: Inconsistent Coupon Number Format found, using first non-empty one. Coupon Standard Letter: {1} First Enclosure: {2} Format: {3} Other Enclosure: {4} Format: {5} | (Like Check Format above, the Coupon Number format specified for the Enclosure Code (for a given coupon template) should all be the same, but it's not.) The exception occurs when the logic has detected 2 (or more) different formats specified for the same coupon template, which is bad. Checks and Coupon numbers have "Formats" defined at the Enclosure Code level. (A combined field.) | Navigate to Administration > Company Setup > Fulfillment > Enclosure Codes. Find and fix all enclosure codes that share the same coupon template. | Agent | Coupons |
LC009866 | Warning: Inconsistent Last Coupon Seq found, using maximum value. Coupon Standard Letter: {1} First Enclosure: {2} Seq: {3} Other Enclosure: {4} Seq: {5} | For a given coupon template, the value specified by Next Coupon Number for the Enclosure Codes should all be the same, but its not. The exception occurs when the logic has detected 2 (or more) different formats specified for the same coupon template, which is bad. Coupon Templates have last_coupon_seq defined at the Enclosure Code level. | Navigate to Administration > Company Setup > Fulfillment > Enclosure Codes. Find and fix all enclosure codes that share the same coupon template. | Agent | Coupons |
LC009867 | Unknown Coupon's Standard Letter ID: {1}. Check custom config settings | When creating a checking account, a standard letter ID must also be included. The first time you create a checking account you may have to first create the Checking Account category. The Checking Account category is called JFA. When defining the actual code values for each checking account, the only special step you need to take is to enter the Standard Letter ID code of the letter used to print checks for this checking account in the Description 2 field of the code definition. | Navigate to Administration > Company Setup Fulfillment > Additional Enclosure Definition > Enclosure Attribute Categories Checking Account. A code may not be set up correctly or may not be set up at all. | Administrator | Coupons |
LC009868 | Coupon's Standard Letter ID: {1} is not Document Type 2 - Formatted Text, the only one supported currently | Printed coupons only support HTML (Doc Type 2), the one specified for this template is not HTML. | Verify that the check configuration is correct for the coupon template related to the standard letter. | Administrator | Coupons |
LC009869 | Coupon's Standard Letter ID: {1} does not have any required Standard Letter File Name provided | The coupon template definition requires a standard letter file name and does not have the value filled in for the field. | Navigate to Administration > Company Setup > Fulfillment > Standard Letters, {1}, add the missing value for the standard letter filename. | Administrator | Coupons |
LC009870 | Could not open Coupon's Standard Letter Path: {1} File: {2} Standard Letter ID: {3} Error: {4} | Location where letter is stored either has incorrect path or incorrect syntax preventing the file from being located and opened. | Attempting to open a file and is most likely due to permit error, hard drive offline, mount point, corrupt file, etc. | Administrator | Coupons |
LC009871 | Coupon's Standard Letter ID: {1} does not have letter type code | The standard letter definition for the coupon template must specify a letter type code and the value for that field is missing. | Navigate to Administration > Company Setup > Fulfillment > Standard Letters. Drill down to the code level within the {1} sub folder. Select the Standard Letter tab within the designated code and verify the Standard Letter File Name is designated. Confirm the file exists in the <folder>. Verify referenced Standard Letter File name is spelled correctly. | Administrator | Coupons |
LC009899 | Letter: {1} cannot be batched due to unassociated enclosure on Case | The specified letter is being excluded from the batch, because of an unrelated enclosure on the same Case which has a problem. Ordinarily, there is nothing wrong with the letter. | Find the enclosure on the case that is either not linked to any letter or linked to a letter that has already been sent/deleted. Troubleshoot as needed to rectify the situation. | Agent | Case Letter Exceptions |
LC009900 | Letter: {1} has been sent or allocated to another batch since processing began | While process was running something outside of the process stepped in and "grabbed" the enclosure or someone manually picked the enclosure. | Nothing to be done, except verify that Fulfillment filters are correct if attempting to segregate processing. Admin can run a report and filter to isolate batches to reveal what is happening. | Agent | Case Letter Exceptions |
LC009745 | Internal error attempting to mark letter as sent: {1} StackTrace: {2} | The possibility exists that the letter was deleted while the batch was running or was locked by another process during the batch run. | Possibly the letter was deleted while the batch was running. Review the case to identify current status, view audit trail. | Administrator | Case Letter Exceptions |
LC009918 | Letter: {1} letter row not found | The possibility exists that the letter was deleted while the batch was running or was locked by another process during the batch run. | Possibly the letter was deleted while the batch was running. Review the case to identify current status, view audit trail. | Administrator | Case Letter Exceptions |
LC009920 | Letter: {1} has not been Prepared (case_paragraph row not found) | There is an un-prepared letter on the case and AUTO PREP is not configured for that type. | Prepare the letter in the case or delete the letter from the case if it does not need to be there. | Agent | Case Letter Exceptions |
LC009921 | Letter: {1} Prepared text is blank (case_paragraph.text) | There is prepared letter that is totally blank and the intent was to not send blank letters. This traps the exception and the agent is notified via the exception. | Prepare the letter in the case or delete the letter from the case if it does not need to be there. | Agent | Case Letter Exceptions |
LC009919 | Letter: {1} Could not get text of Word Document: {2}{3} Error: {4} | Emplifi Agent, while trying to send an email by extracting the text of a Word .doc or Word.docx file, failed for the specified reason. | Contact Emplifi Level2/Support. | Administrator | Case Letter Exceptions |
LC009762 | Letter: {1} Failed to send Email to: {2} Error: {3} | Email could not be sent, for the specified reason. | There could be a transient problem with the electronic external email server, or it might be an invalid email address. For other than invalid email address, contact your internal IT department. | Administrator | Case Letter Exceptions |
LC009763 | Letter: {1} Failed to send Email to: {2} Error: {3} | Email could not be sent, for the specified reason. | There could be a transient problem with the electronic external email server, or it might be an invalid email address. For other than invalid email address, contact your internal IT department. | Agent | Case Letter Exceptions |
LC009913 | Related Letter: {1} does not have a Primary Letter for Case with same Send-To Address in Batch | The "Related Letter" is a special type of letter (defined by Letter Type Code) where it acts like an enclosure and gets sent to the same address as the "prime" letter. There is no "prime" letter. | Open the Case and fix the Send To Address, add the "prime" letter, or remove the related letter, or fix the Letter Type Code. | Agent | Case Letter Exceptions |
LC009914 | Letter of a type that requires a single check is missing related Check | Letter+Check combo, the enclosure is not on the Case (in the batch). | Open the Case, change the letter, or add the missing enclosure. | Agent | Case Letter Exceptions |
LC009915 | Letter of a type that requires a single check has more than one related Check | Letter+Check combo, there are 2+ checks. | Open the Case, remove the extra check, or add an additional letter corresponding to the second and subsequent checks. | Agent | Case Letter Exceptions |
LC010091 | Letter of a type that requires a single coupon is missing related Coupon | Letter+Coupon combo, the enclosure is not on the Case (in the batch) | Open the Case, change the letter, or add the missing coupon enclosure. | Agent | Case Letter Exceptions |
LC010092 | Letter of a type that requires a single coupon has more than one related Coupon | Letter+Check combo, there are 2+ coupons. | Open the Case, remove the extra check, or add an additional letter corresponding to the second and subsequent coupons. | Agent | Case Letter Exceptions |
LC009917 | Letter: {1} no custom_file_name after Batch Prep for Word Doc! | Some error happened during auto-prep of a Word letter, where no error was returned, but also the file name created is missing. Admin needs to check the main LOG file for errors. | Open the Case, manually prepare the letter. | Agent | Case Letter Exceptions |
LC009882 | Letter: {1} does not specify a Letter Type Code | The letter is missing its Letter Type Code. | Open the Case Letter and enter the correct Letter Type Code. | Agent | Case Letter Exceptions |
LC000000 | Unknown Letter Type Code: {1} or no Fulfillment Type defined for that Letter Type Code | The case letter Letter Type Code is invalid or the additional required configuration for that code is missing. | Open the Case and verify that the Letter Type Code is correct. If it is correct, then go to Administration > Company Setup > Fulfillment > Letter Type Codes. Select specific code, go to the Letter Type Code tab, and fill in the information needed. | Administrator | Case Letter Exceptions |
LC009883 | Letter: {1} has not been marked Ready to Prep/Print | The letter Ready checkbox is clear. | Select the Ready check box on the top right of the Letter section. | Agent | Case Letter Exceptions |
LC009884 | Letter: {1} has not been Proofed | The letter has not been proofed. | Use the Letter Proofing Utility to review and approve letters before they are sent out. | Administrator | Case Letter Exceptions |
LC009885 | Letter: {1} has a Letter Type of Email, not supported in Check Export Mode | Email letter types do not support Check Export Mode. This exception applies to the special Manage Batch mode only. Managed batch export mode, in this mode email is not permitted. | More than likely the filter used on the batch is incorrect and includes the wrong cases. | Administrator | Case Letter Exceptions |
LC009886 | CORRUPT Letter for Check Enclosure, missing <DocumentNumber/> tag | Checks and coupons must have the tag <DocumentNumber/> in the HTML so the logic knows where to embed the generated check/coupon number. Otherwise, it won't work. | Special HTML tag is needed. Verify that the correct standard letter ID is being used. | Agent | Case Letter Exceptions |
LC009887 | Letter: {1} document type: {2} requires Microsoft Word to be installed on the server, and it is not. Error Creating Object: {3} | To open Word letters, the server must have Microsoft Word installed. | Install Microsoft Word on the server or open the word document on a server that had Microsoft Word installed. | Administrator | Case Letter Exceptions |
LC009888 | Letter: {1} could not open Word Document: {2}{3} Error: {4} | There are a variety of reasons this exception can occur. | Contact Emplifi Level 2 Support or your internal IT department for assistance. | Agent | Case Letter Exceptions |
LC009889 | Letter: {1} has not been Prepared | The letter has not been prepared. | Prepare the letter in the case or delete the letter from the case if it is not needed. | Agent | Case Letter Exceptions |
LC009890 | Letter: {1} document type: {2} does not match the Standard Letter document type: {3} | The Letter on the Case is flagged as Word, while the Standard Letter ID it was derived from is HTML (or vice versa). Normally caused by bad import data, or someone changed the types after the letter was added to the Case. | Either select a Std. Letter ID or delete the letter from the case. Usually, you will delete the letter from the case. | Agent | Case Letter Exceptions |
LC009738 | Letter: {1} does not specify an Email Address | The field Email To address is not specified and is needed to know where to send a letter soft copy electronically. | Navigate to the case, verify the CALLER has valid contact information entered. | Agent | Case Letter Exceptions |
LC009891 | Letter: {1} neither the Letter nor the Send To Address specify an Email Address | The Send To or Email Toaddress fields are not specified and are required to know where to send the letter either by hard copy through a designated carrier or soft copy electronically. | Navigate to the case, verify the CALLER has valid contact information entered. | Agent | Case Letter Exceptions |
LC009892 | Letter: {1} Send To Address does not exist | The field Send To address is not specified and is needed to know where to send a hard copy letter through a designated carrier. | Navigate to the case, verify the CALLER has valid contact information entered. | Agent | Case Letter Exceptions |
LC009893 | Letter: {1} does not specify Send To Address | The field Send To address is not specified and is needed in order to know where to send a hard copy letter through a designated carrier. | Navigate to the case, verify the CALLER has valid contact information entered. | Agent | Case Letter Exceptions |
LC009894 | Letter: {1} Send To Address does not specify Last Name | The field Send To does not specify the Last Name of the Caller that is to receive a letter. | Navigate to the case, verify CALLER has an address provided. Select enclosure within the case, enter value to the Send To field. | Agent | Letter Address Block Exceptions |
LC009739 | Enclosure: {1} Send To Address does not specify Last Name | The field Send To does not specify the Last Name of the Caller that is to receive a letter. | Navigate to the case, verify CALLER has a last name provided. Select enclosure within the case, enter value to the Send To field. | Agent | Letter Address Block Exceptions |
LC009895 | Letter: {1} Send To Address does not specify Address1 | The field Send To does not specify the Address1 of the Caller that is to receive a letter. | Navigate to the case, verify CALLER has an address provided. Select enclosure within the case, enter value to the Send To field. | Agent | Letter Address Block Exceptions |
LC009740 | Enclosure: {1} Send To Address does not specify Address1 | The field Send To does not specify the Address1 of the Caller that is to receive a letter. | Navigate to the case, verify CALLER has an address provided. Select enclosure within the case, enter value to the Send To field. | Agent | Letter Address Block Exceptions |
LC009896 | Letter: {1} Send To Address does not specify City | The field Send To address does not specify the City of the Caller that is to receive a letter. | Navigate to the case, verify CALLER has an address city provided. Select enclosure within the case, enter value to the Send To field. | Agent | Letter Address Block Exceptions |
LC009741 | Enclosure: {1} Send To Address does not specify City | The field Send To address does not specify the City of the Caller that is to receive a letter. | Navigate to the case, verify CALLER has an address city provided. Select enclosure within the case, enter value to the Send To field. | Agent | Letter Address Block Exceptions |
LC009897 | Letter: {1} Send To Address does not specify State/Province | The field Send To address does not specify the State/Province of the Caller that is to receive a letter. | Navigate to the case, verify CALLER has an address state/province provided. Select enclosure within the case, enter value to the Send To field. | Agent | Letter Address Block Exceptions |
LC009742 | Enclosure: {1} Send To Address does not specify State/Province | The field Send To address does not specify the State/Province of the Caller that is to receive a letter. | Navigate to the case, verify CALLER has an address state/province provided. Select enclosure within the case, enter value to the Send To field. | Agent | Letter Address Block Exceptions |
LC009898 | Letter: {1} Send To Address does not specify Postal Code | The field Send To address does not specify the zip code of the Caller that is to receive a letter. | Navigate to the case, verify CALLER has an address postal code provided. Select enclosure within the case, enter value to the Send To field. | Agent | Letter Address Block Exceptions |
LC009743 | Enclosure: {1} Send To Address does not specify Postal Code | The field Send To address does not specify the zip code of the Caller that is to receive a letter. | Navigate to the case, verify CALLER has an address postal code provided. Select enclosure within the case, enter value to the Send To field. | Agent | Letter Address Block Exceptions |