Servicing Director 15.x History or Other Built-In Report Screen Causes the Application to Stop Responding

• Related Articles

• History or Other Built-In Report Screen Causes the Application to be Closed by Windows

  Clicking the Fusion Servicing Director History button or other application button, which is a built-in Crystal Reports-created screen, the applications do not open the screen. Instead, Windows reports that the application must be closed or terminated ...

• Servicing Director History or Other Built-In Report Screen Causes Windows Event Viewer Error: "...The process was terminated due to an unhandled exception..."

  Faulting application name: custsvc.exe, version: 16.1.0.145, time stamp: 0x5719d28d Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x0b9310eb Faulting process id: 0x1658 Faulting ...

• Servicing Director Event Manager>Daily Delinquency Counters Update Causes Event Manager to Stop Responding

  When you run the Event Manager event named Daily Delinquency Counters update, the event appears to not finish and Event Manager appears to stop responding. Workaround: The Servicing Director Daily Delinquency Counters Update performs many new ...

• Servicing Director 15.x History and Other Screen Windows Event Viewer Error: "...Log on failed..."

  Exception Information Log on failed. Stack Trace Information at CrystalDecisions.CrystalReports.Engine.ReportDocument.VerifyDatabase() at CRptDoc.SetLogonInfo(String DSN, String DB, String UID, String PWD) Root Cause: Servicing Director 15.1, 15.2, ...

• Events in Servicing Director Event Manager Show a Red X before the Title of the Event in the Scheduled Instances Screen

  When you run the Event Manager run all scheduled events, one or more events show a red X before the title of the event listing in the Scheduled Instances screen. Workaround: The red X indicates the event failed to run for some reason and an error ...