Resolve MySQL appears can ' t create/write to file ' #sql

Today I am on the site management background, log in prompt
MySQL error:can ' t create/write to file ' #sql_5c0_0. MyD '
MySQL Server Error:
Can ' t create/write to file ' c:/windows/temp/#sql_a80_0. MyD ' (errcode:17) (1)
based on the online search problem tips and their own situation analysis, solutions are as follows:

Description
This problem occurs because the server environment does not allow database checksums to be performed.
solution to the idea and reason:
1, Permissions issues c:/windows/temp folder permissions, at least to give the Users group can read and write permission, or give everyone permission can also;
2, the file is too large C:/windows/temp folder full of disk, the file is not written, at this time, empty the Temp folder inside the data can be, or delete this file #sql_2250_0.myd (if you follow the steps of this file or must be deleted);

Note: But this is not a fundamental solution. If the server is installed McAfee must perform the following steps to resolve the problem

3, anti-virus software McAfee problem
3.1. McAfee Access Protection settings issues modify McAfee's access Protection to allow temp files to be writable;
3.2. McAfee's access scan issue open McAfee Press Access scan Properties-all processes-detections-scan files (when writing to disk) check out;

4, to resolve the MySQL appears Can ' t create/write to file ' c:/windows/temp/#sql_5c0_0. MyD '
Add a row to [mysqld] in My.ini
tmpdir= "d:/mysql/temp/"
Specifies that you create a directory for creating temporary files, which are used in a large number of queries
Restart the MySQL service to take effect.

Open the McAfee VirusScan console-> Press the Access Scanner-> property-> All Processes-> detections-> exclusions-> add d:/mysql/temp/
Exclude time Select write when reading.

Note: since MySQL defaults to the temporary directory is c:/windows/temp, the online spread of the saying is
Modify McAfee VirusScan Console-> Press Access Scanner-> property-> All process-> detections-> scan files to remove write files
My method is relatively safe.

As for the permissions, because the MySQL service defaults to system permissions, is generally fully controlled by the system, if necessary, can also give a startup user.