Is there a preferred method of reboot the SQL and CRM application servers? We've been seeing some SQL server error while using the application and just would like to know if it matters?
Thanks
*This post is locked for comments
I'm not sure about the custom page, I'm not the developer unfortunately. I would just like to know if this would be the cause of not restarting in the correct order? Why wouldn't SQL and CRM be able to understand when the services are up the application would work no matter the order?
Understood but also in this case the errors didn't occur right away, the servers were restarted over this past weeked (4-5 days ago) and only recently started to see this SQL errors. I'm trying to figure out if it's a result of CRM being restarted first and then SQL?
Most likely that's because, if some of your CRM services are sunning when SQL is being restarted, they will try to connect to SQL and they won't be able to, so there will be a SQL error. Other than that..
Well.. Front end server is using back end server, and back end server is using SQL. You try to stop them in the reverse order, and some of them will likely throw an error (as in.. if there is a sandbox plugin but the sandbox service has been stopped, you'll get an error.. not a SQL error, though)
Thanks, I would want to know if the servers were not started in the correct order what would be the reasons for seeing SQL server error i.e. why would not restarting them in the correct order affect anything?
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,235
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (