Bug #85698 MySQL57 Service will not start - error number 3 in a file operation
Submitted: 30 Mar 2017 6:24 Modified: 8 Feb 2018 9:50
Reporter: Mark Anderson Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server Severity:S2 (Serious)
Version:5.7.17 OS:Microsoft Windows (Server 2012)
Assigned to: CPU Architecture:Any
Tags: error number 3, mysql service will not start

[30 Mar 2017 6:24] Mark Anderson
Description:
Operating system error number 3 in a file operation

When database folder is renamed or removed from the Data folder, the MySQL service does not start, reporting a range of files not found.

I understand that if the whole Data directory is relocated / removed thus the indicated path in the my.ini file cannot be found, the yes it makes sense for the service to choke. 

However simply renaming or removing a single database folder should simply throw a warning or three, not prevent the service from starting up entirely.

How to repeat:
Simply rename a sub directory of Data 

For example say you have three mySQL databases  test1 test2 test3  all sitting inside the designates mySQL Data folder. The service is started and life is good. 

Now delete or rename test1 to say  test_1  and the service will not start. 

Suggested fix:
Instead of terminating the service (mySQL57) simply issue Warnings in the log file, not terminating Errors.
[8 Feb 2018 9:50] Chiranjeevi Battula
Hello Mark Anderson,

Thank you for the bug report.
I could not repeat the issue at our end using Windows Server 2012 and Mysql 5.7.21 version.

Thanks,
Chiranjeevi.