The views and opinions expressed in this blog are those solely of the author(s) and do not necessarily reflect Microsoft’s current policy, position, or branding. For official announcements and guidance on Dynamics 365 apps and services, please visit the Microsoft Dynamics 365 Blog.
Personalized Community is here!
Quickly find the content you seek
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
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 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 | Upcoming TechTalks
I was trying to import a solution but it was throwing an SQL Server timeout error
I was looking at CRM instance, I had remote desktop rights to the CRM server.
I was getting some SQL problems and I could see the SQL server wasn’t on the CRM Server but where was it.
Unfortunatly my user couldn’t access the Deployment Manager and I didn’t know or have access to a user who did.
So I was in an odd situation of wanting to find the SQL Server for CRM Instance and not knowing what server it was on.
So how could I check where the SQL Server was?
Investigating why my solution was timing out
I searched for CRM 2011 solution import timeout and came right back to my own blog
CRM 2011 – A time-out occurs when you import a solution in Microsoft Dynamics CRM 2011
The blog post above is quite a popular one and it has had about 5000 views and still gets 6 a month.
There are a couple of time out settings, the SQL timeout setting which is held in OLEDBTimeout, I had to have a peek in the Registry and the settings in MSCRM
I noticed there was a configdb value and before I go any further DO NOT EDIT THIS VALUE, imagine it’s read only and for information purposes only.
Data Source=COM-UKG-SQL\HOSKORG;Initial Catalog=MSCRM_CONFIG;Integrated Security=True;Connect Timeout=60
Frustratingly my user didn’t have access to the server but it was a way to find out the server name, in times of need. There probably is an easier way but this has happened to me a few times where I have been trying to work out the location of the SQL Server, even if it’s to point IT support in the right direction
Looking at the Registry fields reminds me of my CRM 4 development days
Business Applications communities