Check out the latest features available in Dynamics 365 for Customer Engagement, including LinkedIn Connect, Voice of the Customer and Universal Resource Scheduling.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
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 and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
our hard disk crashed on our CRM 4.0 Server, which also was our SQL Server.
I setup a new system, installed CRM 4.0 (which works fine), Now i want to import a backup from the old Organization into the new system. I attached both database files into the SQL Server (org_MSCRM + MSCRM_Config), but when i enter the Deployment Manager only the new Organization appears.
Can you tell me what causes this issue?
Hi Felix, how are you
My name is Andrés Guzmán, I'm glad to help you.
If you create a new implementation for CRM 4 and this works fine, you can use the MSCRM_CONFIG database for both organizations (for the new and empty org, and for your backup)
Please delete the backup from MSCRM_CONFIG database and try to import again the your backup from <YOUR_ORG>_MSCRM backup.
Let me know if this info can help you
You should not restore the MSCRM_Config database - only the Org database.
Please can you try again with a fresh server installation.
Thanks for your help. I checked now the Build Number of my database Backup and it is Major 5, while CRM is running Major 4. So an CRM upgrade should solve my issue.
Business Applications communities