Zendoptimizer.memorybase@network Service Problem Solving method _win Server

Log hints

The description of the event ID (2) (in the resource (Zend Optimizer)) cannot be found. The local computer may not have the necessary registration information or a message DLL file to display messages from a remote computer. You may be able to use the/auxsource= identity to retrieve word descriptions, and to view Help and support for more information. The following information is part of the event: C:\windows\temp\zendoptimizer.memorybase@network service@262916123, the system could not find the specified file.
.
The description of the event ID (487) (in the resource (Zend Optimizer)) cannot be found. The local computer may not have the necessary registration information or a message DLL file to display messages from a remote computer. You may be able to use the/auxsource= identity to retrieve word descriptions, and to view Help and support for more information. The following information is part of the event: Unable to view file mapping, attempting to access an invalid address.

n Possibilities and solutions for searching from the Internet

Solution One:

1. Modify the access rights of the C:\WINDOWS\Temp\ directory so that Zend can modify the directory
General add IIS_WPG and Network Service write permission is enough
2. It is possible that the file could not be found in the C:\WINDOWS\temp\ directory by creating a new file named Zendoptimizer.memorybase@system and Zendoptimizer.memorybase@network SERVICE (if not) empty file
Set upload_tmp_dir = "C:\windows\temp\" in 3.php.ini file (note = spaces on both sides)
4. It is also possible that IIS does not have permission to read the Zend directory, C:\Program files\zendoptimizer-2.6.2\lib\optimizer-2.6.2 directory and C:\Program files\ Zendoptimizer-2.6.2\lib\zendextensionmanager.dll file to add IIS_WPG Read permission (note that different versions may also vary)

There are three ways to solve this problem:

One is to remove the eaccelerator in the php.ini, and then restart IIS and MySQL services;
The second is to add a "extension=php_yaz.dll" extension in php.ini, you must enable him, and then restart IIS and MySQL services, OK problem resolution ...
The third is to modify the access rights of the C:\WINDOWS\temp\ directory, so that Zend can modify the directory, the third situation is generally rare.

Solution:

1. Modify the access rights of the C:\WINDOWS\Temp\ directory so that Zend can modify the directory
General add IIS_WPG and Network Service write permission is enough
2. It is possible that the file could not be found in the C:\WINDOWS\temp\ directory by creating a new file named Zendoptimizer.memorybase@system and Zendoptimizer.memorybase@network SERVICE (if not) empty file
Set upload_tmp_dir = "C:\windows\temp\" in 3.php.ini file (note = spaces on both sides)
4. It is also possible that IIS does not have permission to read the Zend directory, C:\Program files\zendoptimizer-2.6.2\lib\optimizer-2.6.2 directory and C:\Program files\ Zendoptimizer-2.6.2\lib\zendextensionmanager.dll file to add IIS_WPG Read permission (note that different versions may also vary)

Copy Code code as follows:

C:\Program Files\zend
Administrators complete control
System Complete Control
Service Complete Control
Users read and run, List folder directories, read
C:\Windows\Temp
Administrator All rights
System Full Permissions
Users All rights

Extension=php_yaz.dll
Extension=php_zip.dll
Extension=php_sockets.dll

Another way of saying that

Has nothing to do with extensions. This error indicates that Zendoptimizer cannot set up shared memory, usually due to permissions issues. It is recommended that you comment out the Zendoptimizer section to see which paths the TEMP and TMP of the output environment in phpinfo () are, and confirm that two directories are writable to everyone (especially the TMP directory, because Zendoptimizer The TMP directory is used instead of the TEMP directory.
Alternatively, you might want to use a PHP script to create a new Zendoptimizer.sharedmemoryarea@username file in the TMP directory to test that the TMP directory is actually writable.

The result from the experiment is

An error in the event ID (2) did not appear again, but the error in the event ID (2487) is still there, I do not know that there is a possibility, I hope there is a solution to the friend also told me.