• Resolved Eric Malalel

    (@teachlynx)


    I run a WordPress 6.4.3 domain based multisite install on a Windows 2019 server running IIS 10 web server configured with FastCGI for PHP scripts.

    I have recently updated WP Mail SMTP to version 4.0.1 and I get the following problem.

    If I configure FastCGI to use PHP 7.4, everything works fine.

    If I configure FastCGI to use PHP 8.2, I get a 500 error as soon as I want to network activate the plugin, and any request to the server gets a 500 error.

    Here is the error in IIS log file (I have only hidden the IP and the domain):

    2024-03-25 18:47:24 XXX.XXX.XXX.XXX GET /wp-admin/plugins.php action=activate&plugin=wp-mail-smtp%2Fwp_mail_smtp.php&plugin_status=all&paged=1&s&_wpnonce=14cad7aa19 443 – 81.220.53.30 Mozilla/5.0+(Windows+NT+10.0;+Win64;+x64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/123.0.0.0+Safari/537.36 https://www.example.com/wp-admin/plugins.php 500 0 3221225477 1253

    The error code 3221225477 is 0xC0000005 in hex, which on Windows is: define STATUS_ACCESS_VIOLATION ((NTSTATUS)0xC0000005L).

    I think this is a regression as I did not have the issue with previous versions of your plugin.

    This is very annoying as I have customers who require me to use PHP 8.2, so please explain how to fix this, or even better, provide a fix.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Victoria Sakal

    (@sakalvictoria)

    Hi, @teachlynx!

    Please check the WordPress debug log to see if there are some errors and share them with us.

    Also, please, install WP Mail SMTP v3.11.1 on PHP 8.2 and see if the issue is present.

    Thank you.

    Plugin Support Victoria Sakal

    (@sakalvictoria)

    Hi, @teachlynx!

    We haven’t heard from you for a while so I’m going to close this thread for now. But please feel welcome to reopen it when you can provide the additional details.

    Thank you.

    Thread Starter Eric Malalel

    (@teachlynx)

    Hi @sakalvictoria,

    There was no error in PHP log but the Windows Event Viewer finally give me a hint. The 500 error was due to a memory exception in the OPCache PHP optimization module.

    I stopped IIS, cleared the OPCache cache directory, adjusted some OPCache settings, and everything is back on track, including your plugin.

    • This reply was modified 7 months, 3 weeks ago by Eric Malalel.
Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘error 500 when activating plugin’ is closed to new replies.