Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
While doing CRM server migration activity of CRM 2013 from one organization to other, database server being a cluster one was not possible to migrate, therefore, we prepared a database server in SQL Always on Cluster. Data from the CMO database was successfully imported to the new FMO DB server with new connection String (SQL Listener)
The issue was encountered while making a connection between the application and the database with the new connection string and from the application, communication was unsuccessful. We tried "Edit Organization" in deployment and couldn't complete as it gave error "SQLServerAgent" services not running on new server.
We followed below steps:
Options tried for error "SQLServerAgent" services not running on new server:
Restarting the SQL Server Agent Services
Changing parameter string, server string from DB(Organization, Server table) instead of Deployment Manager
Starting SQL Server Agent Services on Old DB
Opened TCP/UDP 443, 445 port from CRM server to SQL server
Is there any other place new server details should be updated before changing in Deployment Manager? Or any settings which should be changed?
Note: Logged In user has complete access everywhere
Can anyone help on this?Thanks
Hello Chintan Gangwar,
Hope you are well.
Is this still a blocker for you?
That message normally comes as a warning and doesn't block saving the configuration when editing an org.
Anyway, it seems you followed all the possible steps including changing the connection string on the DB.
Would you like to share the specific error you are facing?
Business Applications communities