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 by Windows. Some would describe this as the application crashes.
This symptom can be intermittent, and clicking the button may open the screen successfully on some attempts (particularly after opening Servicing Director).
Workaround:
This symptom can mean the Crystal Reports report viewer needs to be reinstalled.
To reinstall the Crystal Reports report viewer, do the following:
- Uninstall from the Windows installed applications control panel the application named The SAP Crystal Reports runtime engine for .NET Framework (32-bit).
- Delete the directory/folder the SAP Crystal Reports runtime engine was using, which by default is:
C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0
- Continue using the Windows applications control panel, and uninstall the Fusion Servicing Director Application.
- Reboot Windows.
- Install the Servicing Director applications again. Installing Servicing Director will automatically also install the Crystal Reports because it will be found not installed.
- If the issue is not resolved, look for other software that uses Crystal Reports or interacts with Crystal Reports and/or Servicing Director, such as a Phone Dialing system. Remove other software temporarily to find which one is causing the issue.
ArticleNumber:
000072253
Related Articles
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 15.x History or Other Built-In Report Screen Causes the Application to Stop Responding
After upgrading to Servicing Director 15.x, clicking the History button or other application button which is a built-in Crystal Reports created screen, the applications do not open the screen, and instead stop responding or "freeze". There is no ...
Built-in Report Error Failed to Retrieve Data from the Database Vendor Code: 229
Crystal Report Viewer: Failed to retrieve data from the database. Details: [Database Vendor Code: 229] Root Cause: The Database Vendor is Microsoft SQL server, and the error code is a Microsoft SQL error code. Microsoft support information about ...
Load Report Failed error
Error message: Load Report Failed This message indicates the Crystal Reports template file, the .RPT file, for the report you are trying to open could not be found or read from the \SvcData\Rpt folder. Workaround: Confirm your \SvcData\Rpt folder has ...
History Button Does Not Open the History Screen
Clicking the History button on any Fusion Servicing Director application does not open the History screen. There is no error message, and the Specify Additional Criteria screen opens, but after moving past that screen, the History screen does not ...