Breaking news from around the world
Get the Bing + MSN extension
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
I've got a small challenge to deal with. I want to set up a copy of our production enviroment to test the Update to Dynamics 365 On-Prem. So I've created a new SQL-Server (same Version) and another CRM Server with different hostnames, same network and same domain, backuped and restored the database of the production environment to the test systems and now I want to import the organization within the Deployment Manager but I always get a strange error, so I'm not able to load the Deployment Manager. I am using the same account to install CRM on the server.
Unhandled Exeption in Managed Code Snap-in
Type is not resolved for member 'Microsoft.Crm.CrmException,Microsoft.Crm.Core, Version=22.214.171.124, Culture=neutral, PublicKeyToken=xyz'.
Exeption stack trace:
at Microsoft.ManagementConsole.Internal.IMessageClient.ProcessRequest(Request request) at Microsoft.ManagementConsole.Executive.RequestStatus.BeginRequest(IMessageClient messageClient, RequestInfo requestInfo) at Microsoft.ManagementConsole.Executive.SnapInRequestOperation.ProcessRequest() at Microsoft.ManagementConsole.Executive.Operation.OnThreadTransfer(SimpleOperationCallback callback)
The eventviewer always throws a MSCRMMonitoringRuntime Error with ID 18690:
Monitoring runtime failed: Machine: CRMSERVER: Exception: Cannot open database "MSCRM_CONFIG" requested by the login. The login failed.Login failed for user 'DOMAIN\CRMSERVER$'.
Monitoring runtime failed: Machine: CRMSERVER: Exception: SmokeTests failed with exception : System.TypeInitializationException: The type initializer for 'Microsoft.Crm.Monitoring.MonitoringSettings' threw an exception. ---> System.Data.SqlClient.SqlException: Cannot open database "MSCRM_CONFIG" requested by the login. The login failed.
I've already checked that the CRM Server is part of the SQLAccess Group.+
Do you have any experience with that error?
Thank you very much!
If I am not wrong you are not able to browse the vanilla instance as well. I would suggest to setup vanilla envirmoment first then do the organization import.
Cannot open database "MSCRM_CONFIG" requested by the login. The login failed. Which means when you open deployment manager it's basically accessing MSCRM_CONFIG database to retrieve server and organization details , with the user which you logged in into the server and it's unable to access.
Try to login sql server with same user see you are able to access or not.
Also make sure the user which you are trying to open deployment manager having deployment administrator access and having following user group with full control.
- Reporting Group
- PrivReporting Group
- SQLAccess Group
- PrivUser Group
In addition go to AD user group for above group and add the user over there. Also you need to add the logged in user into above sql group as well by opening the sql server.
You can take a look below reference-
thanks for your reply. I've checked that my user is currently part of these security groups and also capable to access the databases, everything looks fine but I still get the above error when I try to connect within the deployment manager. :/
Did you find a solution to this issue?
Business Applications communities