Violation of PRIMARY KEY constraint ...
The conversion of a varchar data type ...
Arithmetic overflow error for type int ...
Data Truncated...
UPDATE statement conflicted with the CHECK constraint...
Numeric value out of range...
Cannot insert the value into column...

Root Cause: Microsoft SQL Server is reporting a SQL error about the Servicing Director task you are attempting to complete. The full text of the error message from beginning to end may be long, but the full text may have details about what data values are the problem and where in the Servicing Director database they are having the problem. Be sure to capture the full text of the error message, and a print screen of the Servicing Director application screen with the error displayed is one way to capture to most of the details. 

Workaround:

Work with your administrator to do all of the following that apply to your situation.

In some uncommon situations, Servicing Director may have a SQL error issue for your version of Servicing Director, and it will be described in our knowledge base with an article describing the full text of the error message. Be sure to search our knowledge base for an article with an exact or very close match to the full text of your error, for the same application or workflow, and likely for the same version of Servicing Director. 

In most cases Servicing Director does not display SQL errors, and therefore you likely have a unique situation, often caused by your specific data or specific changes made to your data, with no article in our knowledge base describing your specific error.  If so, then do the following troubleshooting:

1. Confirm the exact workflow that leads up to the error, such as the last three mouse clicks, which screens and buttons are clicked, and the results.
   Note: Print screens or recordings of the workflow are also very helpful.
2. Confirm whether one loan or several loans have the same symptom.
3. Confirm the source of the loan.
   Note: For example, determine if the loan information was entered field by field using the Loan Setup application or some other method.
4. Confirm whether all users have the same symptoms.
5. Confirm when the task was last known to work successfully.
6. Confirm what changes were made prior to the symptoms.
7. Confirm that you have a current and known good backup of your database named Service.
8. Submit a case through Case Management. 

ArticleNumber:

000042582