[tweetmeme source=”BenHosk” only_single=false]
I recently had a very unusual error on the CRM installation.
For some reason the MSCRM_CONFIG database is suddenly entered an odd state where it can no longer be opened in SQL Manager or any applications, without this CRM won’t work (the database is where all the CRM configurations are held)
this is part of the error
Cannot open database “MSCRM_CONFIG” requested by the login. The login failed.
Login failed for user ‘DOMAIN\IISADMIN’.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.Exception Details: System.Data.SqlClient.SqlException: Cannot open database “MSCRM_CONFIG” requested by the login. The login failed.
Login failed for user ‘DOMAIN\IISADMIN’.Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.Stack Trace:
[SqlException (0x80131904): Cannot open database “MSCRM_CONFIG” requested by the login. The login failed.
Login failed for user ‘DOMAIN\IISADMIN’.]
here is a picture of a similar error
This error was very odd because I couldn’t think of what could have caused it. When I tried to view the MSCRM_CONFIG database you couldn’t do anything with the database.
Googling the problem didn’t show many solutions but these two gave me the most hope and they are the same solution, I prefer the second one because it has pictures and is written by a user rather than a support document
http://support.microsoft.com/kb/946286
this is the most straight forward explanation
http://crmhacks.blogspot.com/2008/04/mscrm4-diagnostic-cannot-open-database.html
The solution in the end was to add the computer into SQLAccessGroup, the below solution is from here
Method 2
Add the Microsoft Dynamics CRM server to the SQLAccessGroup group in Active Directory. To do this, follow these steps:
- Click Start, click Run, type dsa.msc, and then click OK.
- Click the organizational unit in which you install Microsoft Dynamics CRM.
- Double-click SQLAccessGroup.
- In the SQLAccessGroup dialog box, click Members, click Add, click Object Types, click to select theComputers check box, and then click OK.
- In the Enter the object names to select box, type the name of the Microsoft Dynamics CRM server, and then click Check Names.
- Verify that the name of the Microsoft Dynamics CRM server in the Enter the object names to selectbox is available, and then click OK two times.
- Restart the Microsoft Dynamics CRM server.
I did these changes and nothing had happened and it wasn’t until I restarted the CRM Server machine and then the database started working again.
The unusual thing I noticed was there was two SQLAccessGroup‘s and I do remember there being an MSCRM_CONFIG database already there before I installed CRM. I wasn’t sure if this was created by a failed install I tried (but failed on the checks) but thinking back this surely can’t have been the case.
It seems to me like CRM might have been installed on the server or maybe CRM had been installed on another server within the domain, this would explain the two SQLAccessGroups (with different guids).
Hosk's Dynamic Blog 