The following is the procedure recommended when any WinSPC component requires an OS reboot, assuming you are on the most recent version of WinSPC (9.0.10 is the most recent release as of today), and that the all of the installation instructions covered in the WinSPC Installation & Configuration Guide (and if applicable, the Upgrade Instructions) were originally followed. 

1) Make sure all WinSPC clients and custom applications are logged out and that software is shut down.

2) Stop the WinSPC Application Server service.

3) Shut down the SQL Server hosting the WinSPC back end database.

4) Shut down the server hosting the WinSPC Remote Directory.

5) Shut down the server hosting the WinSPC Application Server.

• NOTE: You can check the WinSPC Application Server’s logs to make sure it has stopped without any issues. See log examples below.

6) Restart the SQL Server hosting the WinSPC back end database shut down in step 3.

• NOTE: Step 6 must be completely finished before proceeding.

7) Restart the server hosting the WinSPC Remote Directory.

• NOTE: Step 7 must be completely finished before proceeding.

8) Restart the server hosting the WinSPC Application Server.

• NOTE: Step 7 should be completed before proceeding for best results.

• NOTE: You can check the WinSPC Application Server’s logs to make sure it has restarted without any issues. See log examples below.

9) Launch WinSPC.

There are times where you may need to restart various servers in your IT environment, be it for system updates or maitnence. 

The following is the procedure recommended when any WinSPC component requires an OS reboot, assuming that the all of the installation instructions covered in the WinSPC Installation & Configuration Guide (and if applicable, the Upgrade Instructions) were originally followed completely and in order. 

Please note that the procedure should be followed even on older versions of WinSPC, or environments that have chosen not to include the optional WinSPC Application Server service. If your environment falls into one of those categrories, just skip those steps referring to the WinSPC Application Server.

1) Make sure all WinSPC clients and custom applications are logged out and that software is shut down.

2) Stop the WinSPC Application Server service.

3) Shut down the SQL Server hosting the WinSPC back end database.

4) Shut down the server hosting the WinSPC Remote Directory.

5) Shut down the server hosting the WinSPC Application Server.

• NOTE: You can check the WinSPC Application Server’s logs to make sure it has stopped without any issues. See log examples below.

6) Restart the SQL Server hosting the WinSPC back end database shut down in step 3.

• NOTE: Step 6 must be completely finished before proceeding.

7) Restart the server hosting the WinSPC Remote Directory.

• NOTE: Step 7 must be completely finished before proceeding.

8) Restart the server hosting the WinSPC Application Server.

• NOTE: Step 7 should be completed before proceeding for best results.

• NOTE: You can check the WinSPC Application Server’s logs to make sure it has restarted without any issues. See log examples below.

9) Launch WinSPC.