The event failed and reported this error: Q_CutoffStorage: Violation of PRIMARY KEY constraint 'CutoffStorage_PK'. Cannot insert duplicate key in object 'dbo.CutoffStorage'. The statement has been terminated.

Root Cause:

This error is caused by having the Investor Cutoff Storage Update (Investor Cutoff Storage Upd) event run more than once on the same transaction date.

This update uses the Prior Transaction Date.

This update should only be run once for a specific date.

Workaround:

By itself, this Investor Cutoff Storage Update event error is usually not a problem, but this error raises a concern that other events were run more than once on the same transaction date, possibly creating other problems.

For this Investor Cutoff Storage Update event error to appear, the update must have successfully run the first time it was run for the specified date, and therefore the work of this update was successfully completed the first time it was run.

This update uses the Prior Transaction Date. The Prior Transaction Date will be the date prior to the Current Transaction Date, usually set by the Change Posting Date Update (Change Posting Date Upd) event, the event usually run before the Investor Cutoff Storage Update.

This specific error will not appear again, once the transaction date is advanced to a new date when the next Change Posting Date Update completes.

The Investor Cutoff Storage Update event is usually run as part of the Run All scheduled events, and the concern is the Run All scheduled events has been run more than once for a specific date. Having the Run All scheduled events run more than once means some or all of the other scheduled events were run more than once, which can potentially lead to various problems depending on which events were run, and which dates were set.

If the Run All scheduled events was run more than once for a specific date, you should immediately do the following:

1. Do not click on the Run All button again. Do not choose to Run All scheduled events until troubleshooting this error is completed, and you want to do move forward and the Run All scheduled events for the end of a new business day.
2. Stop all users from entering new transactions. Do not enter new transactions until troubleshooting this error is completed. Enabling Servicing Director Read-Only mode is one way to do this. See other articles for more information about how to enable Read-Only mode.
3. Confirm the transaction dates in the System Administration application by selecting Table Setup > Company, then selecting the Transactions tab. Confirm all three dates listed in the Transact Posting Dates section, for Current, Prior, and Last. See other articles about the meaning of these dates.
4. Create the Event Log By Date report from Event Manager, using the start time criteria of the last known good Run All scheduled events. Enter the StartTime > date of last known good Run All scheduled event in the criteria. See other articles about how to run the Event Log by Date report.
5. Locate and confirm your most recent Servicing Director database backup files.
6. Submit a case through Case Management to contact support.

ArticleNumber:

000044006