Symptoms
- Plesk Obsidian running on a Windows server
-
Plesk is not accessible, with the following error displayed in the Plesk GUI:
500 PleskExceptionDatabase
DB query failed: SQLSTATE[HY000] [2002] No connection could be made because the target machine actively refused it. -
Plesk SQL server service can not be started in the Plesk Service Monitor, while having the following error displayed:
Incorrect function. (Error code 1) at Start service PleskSQL server at (service::startStopService line 997)
-
When you try accessing
%plesk_dir%MySQLData, the following error appears:C:Program Files (x86)PleskMySQLData is not accessible.
The file or directory is corrupted and unreadable.
Cause
Windows filesystem corruption on the drive that contains the Plesk installation files. The native Windows OS command chkdsk reports issues on disk C where Plesk is installed:
C:> chkdsk C:
The type of the file system is NTFS.
WARNING! /F parameter not specified.
Running CHKDSK in read-only mode.
Stage 1: Examining basic file system structure ...
Attribute record (80, "") from file record segment 47AF6
is corrupt.
Attribute record (80, "") from file record segment 47C6A
is corrupt.
Attribute record (80, "") from file record segment 7B7AD
is corrupt.
837888 file records processed.
File verification completed.
File record segment 6134 is an orphan.
File record segment 6137 is an orphan.
File record segment 16545 is an orphan.
File record segment 16547 is an orphan.
File record segment 16730 is an orphan.
File record segment 16732 is an orphan.
File record segment 16733 is an orphan.
File record segment 16738 is an orphan.
14477 large file records processed.
Errors found. CHKDSK cannot continue in read-only mode.
Resolution
-
Connect to the server via RDP.
-
Scan the file system for errors and fix them by executing the following command:
C:> chkdsk c: /f /v /r
Note: More information about the general usage of the chkdsk command and its purpose is available in the official chkdsk | Microsoft Learn article