CRM and SQL reboot order?

(0) Share

Report

Posted on by Community Member

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 have the same question (0)

All responses (11)

Answers (1)

Verified answer

a33ik 84,331 Most Valuable Professional on at

Like (2)

Report

Hello,

I believe that the right order is following:

1. Turn off your frontend server(s).

2. Turn off your backend server(s).

3. Restand your SQL Server and wait until it's up and running.

4. Turn on your backend server(s).

5. Turn on your frontend server(s).

Was this reply helpful? Yes No
Suggested answer

Gopalan Bhuvanesh 11,401 on at

Like (0)

Report

I would go with Andrii.

Please also refer

community.dynamics.com/.../124997

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

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?

Was this reply helpful? Yes No
ashlega 34,477 on at

Like (0)

Report

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)

Was this reply helpful? Yes No
ashlega 34,477 on at

Like (0)

Report

That's not a SQL error - that's a web server error. But do you mean that all your services are started and you are still seing this error?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

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?

Was this reply helpful? Yes No
ashlega 34,477 on at

Like (0)

Report

Actually, what is that page you have there? It's not a CRM page - it's some custom application in an iframe within CRM..

Was this reply helpful? Yes No
Gopalan Bhuvanesh 11,401 on at

Like (0)

Report

This error looks like, from another asp.net application, you are using.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

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?

Was this reply helpful? Yes No
ashlega 34,477 on at

Like (0)

Report

Well that's the thing.. it's the custom page that's not working - it's not crm. At least not according to the screenshot. You will need to check with that app developer

Was this reply helpful? Yes No