Random Service Crash in Windows VPS Print

  • 0

It's quite often when we face problems of Random Service Crash in Windows VPS. You may come across situations wherein;

  1. Some of VPS services like MS SQL, MySQL, SmarterMail, WebsitePanel stop automatically.
  2. Random service crash occurs, and it reappears after some hours/days.
  3. Your applications failed to connect to the MS SQL database; you go ahead and check the MS SQL service and find the MS SQL service in stopped status. After restarting the MS SQL service manually, the application - database connection becomes normal.
  4. You cannot connect to the SmarterMail web interface due to the SmarterMail service crash.
  5. Your web pages with MySQL database backend throw database connectivity errors.
  6. After loading for a long time, WebsitePanel URL ends in error.
You may face the above errors if any of your VPS services has crashed. Default Windows VPS services like MySQL, MS SQL, SmarterMail, DNS, and IIS are relatively heavy and demand a significant amount of resources like CPU, RAM, and Disk space.

When your VPS fails to feed these services with a minimum required RAM, CPU, and Disk space, they will get crashed. Usually, a service crash occurs when VPS is heavily utilizing allotted CPU and RAM resources. In case you face such a problem, go through the following checkpoints:

Check CPU and RAM Usage of VPS through Windows Task Manager >> Performance

1. Right-click on Task Bar and Select Start Task Manager.

random service crash1 

You will see the current RAM and CPU usage of your VPS. Some of your VPS services won't function expectedly if your RAM and CPU usage is above 90%.

Check Diskspace Usage of VPS

1. Go to Start → Click Computer.

random service crash2

You will see current VPS disk space usage here. If your disk space usage exceeds 95%, some VPS services won't function expectedly. Remove unwanted data from VPS and release some disk space. As an alternate, you can also purchase additional disk space for VPS.

Configure Service Recovery Properties

Services can also be configured to recover automatically after the crash. Follow the below mentioned steps:

1. Go to Start → Run → Type services.msc Click OK.

random service crash3

2. In Services Window, locate the service you want to configure, Right click on the service name, and Click on Properties.

3. In the Service Properties Window, Click on the Recovery tab.

random service crash4

  • Select the option Restart the Service in the First failure Dropdown.
  • Select the option Restart the Service in the Second failure Dropdown.
  • Select the option Restart the Service in the Third failure Dropdown.
  • Click on Apply and then OK.

You can also set several other properties like Reset Failure Counter after x days and Restart the service after 1 minute since the crash. Repeat the above steps for each service you want to configure for the automatic recovery.

Determine the Root Cause of Service Crash Through Event Viewer

Event Viewer is the most powerful tool to check logs of various warnings and errors registered on VPS. Each application/program or service crash is logged in the Event viewer with sufficient information to get hold of the crash or problem location most of the time. The event viewer is generally located at C:\Windows\system32\eventvwr.exe, and once launched, the Application event logs can easily be viewed.

1. Go to Start → Run → Type eventvwr, and Click OK.

random service crash5

2. In the Event Viewer Window, Under Windows Logs, Check Application and System logs.

random service crash6

random service crash6
3. Locate the Error logs recently registered for the service in question.

4. Click on the Log entry.

Under the General tab, you will see the full description of the logged error. The essential details the application event log gives us are Source, Event ID, User, Exception Code, etc. In addition, the exception code explains what exactly this error means. You can also google the exception code for more information on a registered log.

Was this answer helpful?

« Back