Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
racinghart
Starting Member
49 Posts |
 Posted - 2007-04-23 : 14:27:03
|
| There is an inconsistency between the SQL Server Login IDs and their passwords" error message when you try to start Microsoft Dynamics SLit says to run "Database Maintenance and update Database using the Sychronize All Ownership & Security Update Scenario"solutions would be greatly appreciated... |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-04-23 : 15:04:19
|
| What is 'Microsoft Dynamics SL'? What's your sql server version? |
 |
|
|
racinghart
Starting Member
49 Posts |
Posted - 2007-04-24 : 12:59:50
|
| Dynamics SL is also known as Solomon (by Microsoft)SQL Server 2005 |
|
|
|
racinghart
Starting Member
49 Posts |
Posted - 2007-04-24 : 13:43:57
|
| I ran the following solution guys... and it works... I can now log into Dynamics SLMethod 3: Remove the SQL user IDs Master60SP and CD7359B5576446f85EB67E824B4770 and have Microsoft Dynamics SL re-create them. To do this, follow these steps:1. Start SQL Query Analyzer, and then run the following statement against all Microsoft Dynamics SL databases. sp_changedbowner sa 2. Start SQL Server Enterprise Manager. 3. Expand Microsoft SQL Servers. 4. Expand SQL Server Group. 5. Expand your instance of SQL Server. 6. Expand Security. 7. Double-click Logins. 8. Right-click Master60Sp, and then click Delete. 9. Right-click CD7359B5576446f85EB67E824B4770, and then click Delete. 10. Exit Enterprise Manager. 11. Use Database Maintenance to connect to the server that is running Microsoft SQL Server. To do this, follow these steps: a. Open the Database Maintenance (98.290.00) dialog box. b. In the Destination SQL Server Name box, type the name of the server. c. In the Login ID box, type sa. d. In the Password box, type the password for the system administrator user. e. Click Connect. 12. Click the Update Database tab. 13. In the System Database Name box, click your system database. 14. In the Databases column, select your application database. 15. In the Update Scenarios area, select Synchronize All Ownership & Security. 16. Click Update Database. 17. Close the Database Maintenance (98.290.00) dialog box. 18. Log on to Microsoft Dynamics SL. |
|
|
|
tdrought
Starting Member
1 Post |
Posted - 2007-05-18 : 06:57:37
|
| Did this help you out?I also have this error when I try to start Dynamics SL. Though, I only get it on one of the 5 workstation we have Dynamics installed on in this company.Thanks |
|
|
|
asmith640
Starting Member
1 Post |
Posted - 2009-05-12 : 11:11:10
|
| We encountered this issue today and did the following and it resolved our error:Had to reregister the capicom.dll. Search for capicom.dll on the C drive. One should be somewhere in C:\Windows. Go to Run and type regsvr32 C:\Windows(rest of path) and hit enter. It should say it successfully registered – then Solomon was fine. |
|
|
|
Roger_L
Starting Member
1 Post |
Posted - 2009-12-16 : 18:52:18
|
| We just ran into this issue and did the regsvr32 on the capicom.dllIt fixed the issue for us. Note that the capicom.dll on the client machine having the issue is the one that needs to be registered--not the SQL server machine's capicom.dll. |
|
|
|
|
|
|
|
|
system message 9827 - There is an inconsistency