Errors which begin with:

Run-Time Error...

Followed by other messages which begin with text like this:

Object: "TheView", Event EventInitialize", Line #...

Type mismatch...

Object required...

Declarations...

GlobalDeclarations...

Root Cause:

The Servicing Director applications are reporting a Run-Time  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 fields or values are the problem and further something about the nature of 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 Run-Time error issue for your version of Servicing Director, and it will be described in the Knowledge Center with an article describing the full text of the error message.  Be sure to search Knowledge Center 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 Run-Time errors, and therefore you likely have a unique situation, often caused by your specific data or specific environment, with no article in Knowledge Center 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 if you are using an application server, where the server has multiple Servicing Director users running multiple copies if the applications at the same time and users use thin client remote connections from their desktops. If so, then confirm the outcome of the workflow on a single application user standalone desktop computer, where the Servicing Director applications are locally installed on the desktop hard drive, and the desktop is running the applications locally for the one user, removing the unsupported application server environment from the troubleshooting.
6. Confirm when the task was last known to work successfully.
7. Confirm what changes were made prior to the symptoms.
8. Confirm that you have a current and known good backup of your database named Service.
9. Contact customer support using Case Management in Finastra Customer Success Community.

ArticleNumber:

000043387