Partner and Community Forums
Windows Cache Extension for PHP
WinCache with Joomla and PHP 7.2
Last post Feb 10, 2018 04:42 PM by lextm
Feb 10, 2018 07:42 AM|RenniePet|LINK
I have two Joomla websites on IIS 8.5 on Windows 2012 R2. After the server has been running for some days I start getting errors like this:
[10-Feb-2018 07:04:49 Europe/Copenhagen] PHP Warning: require_once(E:\Websites\My Tech Blog\plugins\system\regularlabs\regu): failed to open stream: No such file or directory in E:\Websites\My Tech Blog\libraries\src\Plugin\PluginHelper.php on line 253
[10-Feb-2018 07:04:49 Europe/Copenhagen] PHP Fatal error: require_once(): Failed opening required 'E:\Websites\My Tech Blog\plugins/system/regularlabs/regularlabs.php' (include_path='.') in E:\Websites\My Tech Blog\libraries\src\Plugin\PluginHelper.php on
The file being referenced does exist.
I am also seeing errors like this in the event viewer:
Faulting application name: php-cgi.exe, version: 18.104.22.168, time stamp: 0x5a7219e5
Faulting module name: VCRUNTIME140.dll, version: 14.11.25325.0, time stamp: 0x59273894
Exception code: 0xc0000005
Fault offset: 0x000000000000c560
Faulting process id: 0x12e0
Faulting application start time: 0x01d3a1694e3e35cd
Faulting application path: C:\Program Files\PHP\v7.2.2\php-cgi.exe
Faulting module path: C:\Windows\SYSTEM32\VCRUNTIME140.dll
Report Id: 2e608f15-0d5e-11e8-80ed-000d3ab649dc
Faulting package full name:
Faulting package-relative application ID:
I'm not sure if there is any relation between the event viewer error and the PHP error log errors. The event viewer error occurs much less frequently, maybe once a day.
Because the PHP errors first happen after several days I suspect that WinCache is at fault. Is this a valid assumption?
The only way to fix the problem is to reboot the web server. (Restarting the website isn't enough.)
Any advice would be appreciated.
Feb 10, 2018 04:42 PM|lextm|LINK
It is interesting that you don't think PHP itself, or Joomla can be the cause.
Unfortunately, all components you use are open source, so if you cannot troubleshoot it yourself or buy support from a certain vendor (Microsoft won't support you on open source components they don't own), then rebooting the web server is your only resort.