Skip to main content
NetApp Knowledge Base

SnapCenter server MySQL service is stopping constantly and any running jobs are not completing

Last Updated:

Applies to

SnapCenter Server 4.x (SC)


During a verification job or during the scheduled clean-up job, the MySQL service crashes on the SnapCenter server, causing several issues like jobs stuck in a running state, inability to log in to the SnapCenter GUI, or scheduled jobs not starting.

When the MySQL service crashes, the following error messages can be seen:

In the SnapManagerWeb.log:

2021-xx-xxTxx:00:xx+01:00 ERROR SnapManagerWeb_xxx PID=[xxx] TID=[xx] Can't connect to MySQL server on 'localhost' (10061):
No connection could be made because the target machine actively refused it

In the SnapCenter server Event Viewer Application log:

Faulting application name: mysqld.exe, version:, time stamp: 0x5cfe7a5c
Faulting module name: mysqld.exe, version:, time stamp: 0x5cfe7a5c
Exception code: 0x80000003


Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.