SUMMARY
When you try to start Microsoft Dynamics SL, the program does not start. Instead, you receive the following error message.
System Message 9827- There is an inconsistency between the SQL Server Login IDs and their passwords stored in the Solomon System Database. Please have the System Administrator run Database Maintenance and update the database using the Synchronize All Ownership & Security update scenario.
Cause
This problem occurs if one of the following conditions is true:
The Capicom.dll file is not registered. See method 1 in the "Resolution" section.
The database version and the product version do not match. This problem might occur if the Microsoft Dynamics SL program files were not updated to the same version as the database. For example, you try to use Microsoft Solomon 6.0 Service Pack 1 (SP1) program files to access a database that you created when you were using Microsoft Business Solutions - Solomon 6.0. See method 2 in the "Resolution" section.
The SQL user IDs Master60SP and CD7359B5576446f85EB67E824B4770 do not synchronize with the Master user ID in the Microsoft Solomon 6.0 Service Pack 1 (SP1) system database. See method 3 in the "Resolution" section.
The Microsoft Dynamics SL databases were moved to a new server, but the Solomon.ini file still points to the old server. See method 4 in the "Resolution" section.
The Microsoft Dynamics SL databases are in single-user mode. See method 5 in the "Resolution" section.
The Named Pipes protocol is not the first protocol that is listed in Client Network Utility. This problem occurs when you log on to Microsoft Dynamics SL 6.5 Service Pack 1. See method 6 in the "Resolution" section.
A Fully Qualified Domain Name (FQDN) is being used for the server that is running Microsoft SQL Server. See method 7 in the "Resolution" section.
A password policy is being enforced against the CD7359B5576446f85EB67E824B4770 SQL ID account. See method 8 in the "Resolution" section.
You logged on by using a Windows domain user account that is not associated with a Microsoft Dynamics SL user account. See method 9 in the "Resolution" section.
The domain table contains an IP address in the ServerName field but the Solomon.ini file contains the actual name of the server (by using characters). See method 10 in the "Resolution" section.
RESOLUTION
To resolve this problem, use the appropriate method.
Method 1: Manually register the Capicom.dll file. To do this, follow these steps:
NOTE This resolution does NOT apply to Microsoft Dynamics SL 2011
Locate and then open the Windows\System32 folder.
Right-click the Capicom.dll file, and then click Open With.
In the Windows dialog box, click Select the program from a list, and then click OK.
In the Open With dialog box, click Browse. Locate and then open the Windows\System32 folder.
Double-click the Regsvr32.exe file, and then click OK. You receive the following message:
RegSvr32 - DllRegisterServer in C:\windows\system32\capicom.dll succeeded.
Click OK.
Repeat these steps on any computer on which you receive the error message that is mentioned in the "Symptoms" section.
Method 2: Verify that the database and the program files have the same version number. To do this, follow these steps:
To find the database version, run the following query against the application database in SQL Query Analyzer.
SELECT S4Future01 FROM GLSetup
To find the program files version, follow these steps:
Start Microsoft Dynamics SL.
In the Login (98.000.00) dialog box, double-click in the empty area that is directly above the Cancel button. The signon dialog box appears.
Note the product version and the kernel build number.
Locate the product version and the kernel build number in the lists that are in the following Knowledge Base article:For more informationabout the product version and kernel build, click the following article number to view the article in the Microsoft Knowledge Base:
850447 How to determine the version, release, or kernel build of Solomon
Verify that the database version that you noted in step 1 corresponds with the product version that you noted in step 2c.
If you have an incorrect version of Microsoft Dynamics SL installed, install the correct version of the program. Alternatively, you can upgrade the database to the version of Microsoft Dynamics SL that you installed.
Method 3: Remove the SQL user IDs Master60SP and CD7359B5576446f85EB67E824B4770 and have Microsoft Dynamics SL re-create them. To do this, follow these steps:
Start SQL Query Analyzer, and then run the following statement against all Microsoft Dynamics SL databases.
sp_changedbowner sa
Start SQL Server Enterprise Manager.
Expand Microsoft SQL Servers.
Expand SQL Server Group.
Expand your instance of SQL Server.
Expand Security.
Double-click Logins.
Right-click Master60Sp (Master80 in Dynamics SL 2011), and then click Delete.
Right-click CD7359B5576446f85EB67E824B4770 (CD8359B5576446f85EB67E824B4770 in Dynamics SL 2011), and then click Delete.
Exit Enterprise Manager.
Use Database Maintenance to connect to the server that is running Microsoft SQL Server. To do this, follow these steps:
Open the Database Maintenance (98.290.00) dialog box.
In the Destination SQL Server Name box, type the name of the server.
In the Login ID box, type sa.
In the Password box, type the password for the system administrator user.
Click Connect.
Click the Update Database tab.
In the System Database Name box, click your system database.
In the Databases column, select your application database.
In the Update Scenarios area, select Synchronize All Ownership & Security.
Click Update Database.
Close the Database Maintenance (98.290.00) dialog box.
Log on to Microsoft Dynamics SL.
Method 4: Rename the Solomon.ini file that is on the local workstation. To do this, follow these steps:
Search for the Solomon.ini file that is on the local workstation. This file is usually located in one of the following folders:
C:\Windows
C:\Winnt
Important Do not rename the Solomon.ini file that is in the program files folder for Microsoft Dynamics SL.
Right-click the file, and then rename it Solomonini.bak.
Restart Microsoft Dynamics SL.
Method 5: Take the databases out of single-user mode. To do this, follow these steps:
Log in to SQL Server Enterprise Manager.
Expand Microsoft SQL Servers, expand SQL Server Group, expand the appropriate server, and then expand Databases.
Right-click the appropriate database, and then click Properties.
Click the Options tab.
In the Access area, clear the Restrict access check box, and then click OK.
Note The databases are put in single-user mode as part of the backup process and then automatically changed to normal mode after the backup is completed. If a failed backup occurs, the databases may be left in single-user mode. In this situation, the mode must be manually changed back to normal mode.
Method 6: Make Named Pipes the first protocol that is listed in Client Network Utility. To do this, follow these steps:
In the Microsoft SQL Server program group, locate and then open the Client Network Utility from the Microsoft SQL Server program group.
On the General tab, locate Named Pipes under Enabled Protocols by Order.
If Named Pipes is not the first protocol that is listed in the Enabled Protocols by Order dialog box, select Named Pipes, and then click the up arrow to move Name Pipes to the top of the list.
Click OK to accept the changes.
Restart Microsoft Dynamics SL.
Method 7: Add the appropriate domain suffix. To do this, follow these steps:
Open the Advanced TCP/IP Settings dialog box. To do this, follow these steps:
Log on to the computer as an Administrator.
Click Start, point to Control Panel, and then click Network Connections.
Right-click the local area connection that you want to modify, and then click Properties.
In the This connection uses the following items dialog box, click Internet Protocol (TCP/IP), and then click Properties.
Click Advanced.
Click the DNS tab.
Click Append these DNS suffices, and then click Add.
Add the appropriate domain suffix. For more information, contact your network administrator.
Method 8: Clear the Enforce Password Policy check box in SQL Server Management Studio. To do this follow these steps:
Log on to SQL Server Management Studio.
In Object Explorer, expand Security, and then expand Logins.
Right-click CD7359B5576446f85EB67E824B4770, and then click Properties.
Clear the Enforce password policy check box, and then click OK.
Exit SQL Server Management Studio.
Note You may have to repeat steps a through e for the Master60 SQL ID account.
Method 9: Associate the Windows domain user account with a Microsoft Dynamics SL user account. To do this, follow these steps.
Note These steps apply only to Microsoft Dynamics SL 7.0 or later versions that are configured to use Windows authentication.
Log on to Microsoft Dynamics SL as the sysadmin user.
In the Navigation pane, click Administration.
In the System Manager details pane, click User Maintenance in the Security section.
Type the appropriate Microsoft Dynamics SL user ID in the User ID box, and then press the TAB key.
Type the appropriate Windows domain user account ID in the Windows User Name box, and then click Save.
Note You must type the Windows domain user account ID in the following format:
Domain\Windows domain user account ID
Method 10: Verify that the ServerName field in the Domain table contains the same value as the server name that is defined in the Solomon.ini file. To do this, follow these steps.
Log in to SQL Query Analyzer or to SQL Server Management Studio.
Run the following command against the Microsoft Dynamics SL system database:
SELECT ServerName FROM Domain
Open the Solomon.ini file in a text editor. In the [System32 Database] area, note the value after Server=.
If the Domain table contains an IP address and the Solomon.ini file contains the actual server name (by using characters), you must update the Domain table with the actual server name. To do this, run the following statement against the Microsoft Dynamics SL system database:
UPDATE Domain SET ServerName = '<Nameofserver>' In this command, "<Nameofserver>" is the actual name of the server that you noted in the Solomon.ini file.
Method 11: Configure SQL Server to allow for remote connections.
Views:
Keywords: Error Message 9827