Title: Scan doesn't complete Last modified: August 31, 2016 --- # Scan doesn't complete * Resolved [saxoflora](https://wordpress.org/support/users/saxoflora/) * (@saxoflora) * [10 years ago](https://wordpress.org/support/topic/scan-doesnt-complete-2/) * Hello * My scan doesn’t complete as it hits the following problem: * Error finishing writing value for wfsd_engine (error: The size of BLOB/TEXT data inserted in one transaction is greater than 10% of redo log size. Increase the redo log size using innodb_log_file_size.) * I’ve stopped the scan manually and restarted it and the error persists. * The hosting environement is Azure with windows and I am using CPanel. * My site url: [https://voila.eu.com](https://voila.eu.com) * Thank you for this amazing plugin! * [https://wordpress.org/plugins/wordfence/](https://wordpress.org/plugins/wordfence/) Viewing 12 replies - 1 through 12 (of 12 total) * [wfasa](https://wordpress.org/support/users/wfasa/) * (@wfasa) * [10 years ago](https://wordpress.org/support/topic/scan-doesnt-complete-2/#post-7443950) * Hello saxoflora, could you check yourself or verify with your host to see if the setting `innodb_log_file_size` needs to be increased? * Thread Starter [saxoflora](https://wordpress.org/support/users/saxoflora/) * (@saxoflora) * [10 years ago](https://wordpress.org/support/topic/scan-doesnt-complete-2/#post-7443952) * Hi wfasa * Thanks for replying. I will check with my host. * saxoflora * Thread Starter [saxoflora](https://wordpress.org/support/users/saxoflora/) * (@saxoflora) * [9 years, 11 months ago](https://wordpress.org/support/topic/scan-doesnt-complete-2/#post-7444045) * Hello * My host doubled the size of innodb_log_file_size and the scan is still hanging. * I’ve done a little more investigation and notice the following: * I have one main WordPress installation in the root folder and the scan completes successfully. * I have 4 other installations in subfolders of the root installation and none of these complete, all hitting the same error decribed above. * On the option screen, the “Scan files outside your WordPress installation” is unchecked. * Thanks for your help. * [wfasa](https://wordpress.org/support/users/wfasa/) * (@wfasa) * [9 years, 11 months ago](https://wordpress.org/support/topic/scan-doesnt-complete-2/#post-7444046) * Hello again! I’m afraid we haven’t seen this error on any sites before and the way you describe it makes it seem like it’s probably some setting on your site that needs to be changed. * All these installs are running against their own separate databases, is that correct? * [GregMcAbee](https://wordpress.org/support/users/gregmcabee/) * (@gregmcabee) * [9 years, 11 months ago](https://wordpress.org/support/topic/scan-doesnt-complete-2/#post-7444057) * I spent almost a month on this prior and I fixed it by excluding graphic files from the scan. It was excluding the .jpg and .png files that fixed it for me and allowed me to complete a scan. * In the options Menu – “Exclude files from scan that match these wildcard patterns.( One per line).” * *.sql *.mp3 *.pdf *.jpg *.png * Thread Starter [saxoflora](https://wordpress.org/support/users/saxoflora/) * (@saxoflora) * [9 years, 11 months ago](https://wordpress.org/support/topic/scan-doesnt-complete-2/#post-7444058) * Thanks Greg. I’ll try this! * [wfasa](https://wordpress.org/support/users/wfasa/) * (@wfasa) * [9 years, 8 months ago](https://wordpress.org/support/topic/scan-doesnt-complete-2/#post-8220959) * Hey saxoflora, just wanted to check in here to see if the fix suggested by Greg worked? Also curious if you would consider sending me a diagnostics report. I could use it to have a closer look at this issue. Go to Wordfence “Diagnostics” page and at the bottom click the button that says “Send Report by Email”. Change the prefilled address to [asa@wordfence.com](https://wordpress.org/support/topic/scan-doesnt-complete-2/asa@wordfence.com?output_format=md) and please provide your username so I know who the mail is coming from. Please let me know when you have sent it so I can go grab it and file it in the correct location. Thanks in advance. * Thread Starter [saxoflora](https://wordpress.org/support/users/saxoflora/) * (@saxoflora) * [9 years, 8 months ago](https://wordpress.org/support/topic/scan-doesnt-complete-2/#post-8221156) * wfasa, thanks for checking. The fix suggested by Greg did not work. * I just sent you the Diagnostics (along with the result of the scan). * The site has its own database but sits as a subdirectory of another site. * When I run a scan on the “umbrella” site with the option “Scan files outside your WordPress installation” checked, the scan completes. So I assume it’s keeping me safe. However, it would be good if the scan worked on the subsites. * Thank you so much for reaching out! * [Brack29](https://wordpress.org/support/users/brack29/) * (@brack29) * [9 years, 2 months ago](https://wordpress.org/support/topic/scan-doesnt-complete-2/#post-8953241) * Hi wfasa, * I have the latest version of WordPress (4.7.3) and the latest Wordfence installed( 6.3.5), and I’m still getting the following error when I perform a scan: * Error finishing writing value for wfsd_engine (MySQLi error: [1105] Parameter of prepared statement which is set through mysql_send_long_data() is longer than‘ max_long_data_size’ bytes) * I’ve just sent you a diagnostic report, as per your instructions above. Hope that’s okay. * Thanks in advance for your help! * [MBV](https://wordpress.org/support/users/mbv/) * (@mbv) * [9 years, 1 month ago](https://wordpress.org/support/topic/scan-doesnt-complete-2/#post-9033626) * Following…I’m getting this as well on a website. * [MBV](https://wordpress.org/support/users/mbv/) * (@mbv) * [9 years, 1 month ago](https://wordpress.org/support/topic/scan-doesnt-complete-2/#post-9033628) * Similar anyway, this is my error message: * > Error finishing writing value for wfsd_engine (MySQLi error: [1118] The size > of BLOB/TEXT data inserted in one transaction is greater than 10% of redo log > size. Increase the redo log size using innodb_log_file_size.) * [GregMcAbee](https://wordpress.org/support/users/gregmcabee/) * (@gregmcabee) * [9 years ago](https://wordpress.org/support/topic/scan-doesnt-complete-2/#post-9129101) * I fixed this today finally. The error is dead correct. There is not enough room for the REDO logs to hold all of the changes. I had to log into my MYSQL server and execute a command to see how big the redo logs were. * Open your MySQLin linux shell and execute this command * show variables like ‘innodb_log%’; * The size returned is in Byres. Mine was 1048576 which = 1MB * I needed to bump the number to 6 MB or 6291456 and restart mysql to get the change to take effect. My host had a place to change InnoDB Log File Size and if you don’t. Call tech support and tell them to set InnoDB Log File Size to 6 MB and try another scan. If you see the error again keep bumping it up in small increments. * **Warning.** My host told me if you set the number too high. You can’t recover and your database won’t allow you to shrink that number. So please, bump the InnoDB Log File Size in small 1 MB increments until your scan finishes. 🙂 * I hope this works for everyone. Viewing 12 replies - 1 through 12 (of 12 total) The topic ‘Scan doesn't complete’ is closed to new replies. * ![](https://ps.w.org/wordfence/assets/icon.svg?rev=2070865) * [Wordfence Security - Firewall, Malware Scan, and Login Security](https://wordpress.org/plugins/wordfence/) * [Frequently Asked Questions](https://wordpress.org/plugins/wordfence/#faq) * [Support Threads](https://wordpress.org/support/plugin/wordfence/) * [Active Topics](https://wordpress.org/support/plugin/wordfence/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/wordfence/unresolved/) * [Reviews](https://wordpress.org/support/plugin/wordfence/reviews/) ## Tags * [scan](https://wordpress.org/support/topic-tag/scan/) * 12 replies * 5 participants * Last reply from: [GregMcAbee](https://wordpress.org/support/users/gregmcabee/) * Last activity: [9 years ago](https://wordpress.org/support/topic/scan-doesnt-complete-2/#post-9129101) * Status: resolved