You use the LSCnfg application Run FixRights option to reset the SQL Server logins used by the Servicing Director applications to connect to the Servicing Director SQL Server.

Resetting the SQL Server logins will grant the logins access to newly restored databases.

If you restore Servicing Director database backups from one SQL Server to another SQL Server, the Servicing Director SQL Server logins will need to be reset.

The procedure below is for your local IT or system administrator familiar with Windows and Microsoft SQL Server.

All Servicing Director applications on all desktops use primarily one SQL Server login named "LoanServicing" for most features; a few features use the SQL Server login named "Reports." 

The LSCnfg application is the only method you can use to change the passwords for these SQL Server logins, because not only does the application change the passwords on the SQL Server, but it also provides the passwords to the client applications. If you change the SQL Server login passwords using commands directly in SQL Server without using the LSCnfg application, then the client applications will not have the new password, leaving the applications unable to log in and causing a login error message to be displayed when users try to open any application.

These SQL Server logins are different from the employee username and password the users are providing to log in to a Servicing Director application. The application is logging into SQL Server using these logins automatically in the background, and the users are typically unaware of these logins. The employee username and password controls the features available to the employee, while the SQL Server logins carry all the communication to the server.

If the Fixrights option is checked, the LSCnfg application rebuilds the SQL Server login accounts and the SQL Server permissions for those accounts.

1. Click Start > Programs > D+H > Servicing Director Tools > LSCnfg. The LSCnfg screen opens.
2. Confirm that the Name field in the Service SQL Server section is the correct name for your Servicing Director SQL Server or SQL Server instance name.
3. Enter 'sa' (without the quotes) in the Sys Admin Login field. The 'sa' login is a standard SQL Server login with administrator permission on the Servicing Director SQL Server.
4. Enter your 'sa' login password in the Sys Admin Password field. The 'sa' login password would have been created by your system administrator when SQL Server was first installed. If you don't know what the 'sa' login password is, check with your system administrator.
5. By default, the Event Manager SQL Server section has the "Same as Service SQL Server" check box checked. Leave this box checked.
6. Set the password for the LoanServicing SQL Server login. To set the default password, make sure the Default check box in the Loan Servicing section has a check mark. To set a custom password of your choice, make sure the Default check box in the Loan Servicing section does not have a check mark, and enter your choice for the LoanServicing login password. The password must meet the password strength requirements enforced by your version of SQL Server and Microsoft Windows.
7. Set the password for the Reports SQL Server login. To set the default password, make sure the Default check box in the Reports section has a check mark. To set a custom password of your choice, make sure the Default check box in the Reports section does not have a check mark, and enter your choice for the Report login password. The password must meet the password strength requirements enforced by your version of SQL Server and Microsoft Windows.
8. Click the Run Fixrights check box to enter a check mark. 

Note: Check the file path displayed in the Config Info section on the lower left of the LSCnfg screen. This location must be the same location your client applications use for the SvcData folder to provide the new SQL Server login passwords to the client applications. If your client applications happen to use a different location for the SvcData folder, then the LSCnfg application will not be able to provide the client applications with the new passwords, leaving the applications unable to log in and causing a login error message to be displayed when the users try to open any application.

9. Click the Apply button.
10. A text log file of the Fixrights results displays. Check the log file for any error messages, and save the error messages if any are listed. The Servicing Director SQL Server logins for the desktop applications are now reset.

If you have the optional Customer Self-Service website product, then also do the following:

Note: The optional Customer Self-Service product uses the SQL Server login named ILSWebUser. When the Customer Self-Service product was installed or last upgraded, the ILSWebUser password was set. The ILSWebUser password may have been set to the default password defined in the Customer Self-Service Installation Guide or it may be a custom password. If there is a custom password, determine what that password is from the installation or upgrade notes. Using the steps below, you will reset the ILSWebUser password back to the default; then, have your SQL Server administrator change the SQL Server login password back to your custom password.

1. Open SQL Server Management Studio.
2. Click New Query.
3. Select the Service database on the New Query toolbar.
4. Enter the following command in the New Query screen:

Use Service

W_Fixrights

5. Click the Execute button on the toolbar to run the command. The results should be a list of the W_Fixrights results. Check the results for any error messages, and save the error messages if any are listed.
6. If you have a custom ILSWebUser password, have your SQL Server administrator change the ILSWebUser login password back to your custom password.
7. Close the SQL Server Management Studio.

ArticleNumber:

000050041