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 Open.
Workaround:
Have your system administrator or local IT do the following:
- Use the Servicing Director LSCNFG application on the server to set the Reports login password to a password of your choice. To learn more about LSCNFG, select the related article about Changing the Servicing Director SQL Login Passwords.
- Set just the Reports login password (the procedures are in the related article).
- Have your users log out and back into the applications for the change to take effect.
- Confirm your SQL server login named Reports is enabled and not locked by SQL.
- If it is locked, unlock it.
- Provide the password you set above if prompted for the password. For more information about how to Microsoft SQL server products and SQL login locks, see your Microsoft support information for SQL server.
ArticleNumber:
000063063
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 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 ...
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 ...
Customer Service History Button Error: "Failed to open the connection...Vendor Code: 4060"
Crystal Report Viewer Failed to open the connection. Details: [Database Vendor Code: 4060] Root Cause: The Database Vendor is Microsoft SQL server, and the error code is a Microsoft SQL error code. Microsoft support information about error code 4060 ...
Customer Service>History Button Error: "Logon failed...Vendor Code: 18456"
Crystal Report Viewer Logon Failed. Details: [Database Vendor Code: 18456] Root Cause: The Database Vendor is Microsoft SQL server, and the error code is a Microsoft SQL error code. Microsoft support information about error code 18456 is this: "Logon ...