Event ID - 5064

Event Id5064
SourceMicrosoft-Windows-WAS
DescriptionThe Windows Process Activation Service encountered a failure requesting IIS configuration store change notifications during recovery from inetinfo terminating unexpectedly. While the Windows Process Activation Service will continue to run, it is highly probable that it is no longer using current metabase data. Please restart the Windows Process Activation Service to correct this condition. The data field contains the error number.
Event Information According to Microsoft :

Cause :

This event is logged when Windows Process Activation Service encountered a failure requesting IIS configuration store change notifications during recovery from inetinfo terminating unexpectedly.

Resolution :

Stop and restart WAS

Stopping the WAS service will also stop the World Wide Web Publishing Service (W3SVC) if W3SVC is running. Thus, you may also have to start W3SVC.

To perform this procedure, you must have membership in Administrators , or you must have been delegated the appropriate authority.

To stop and restart WAS:
  1. Open an elevated Command Prompt window. Click Start , point to All Programs , click Accessories , right-click Command Prompt , and then click Run as administrator .
  2. At the command prompt, type net stop was /y .
  3. At the command prompt, type net start was .
  4. To restart W3SVC, from the command prompt, type net start w3svc . Also, start any other services that were stopped when WAS was shut down.
Verify :

If the Windows Process Activation Service (WAS) is configured correctly, IIS will serve pages successfully.

To confirm that WAS is executing successfully, perform the follow these steps:
  1. Open Internet Explorer.
  2. Browse to http://localhost or your Web site's default home page.
  3. Confirm that the expected page is displayed.
  4. Open the logs for the Web site and make sure 200 OK (request succeeded) is logged for the previous request. By default, Web site logs are located in the %SystemDrive%\inetpub\logs\LogFiles directory.
Note : If logging is set to centralized, the log file size will grow over time. The minimum possible (and configurable) log file size is 1 MB.
Reference LinksEvent ID 5064 from Microsoft-Windows-WAS

Catch threats immediately

We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.

See what we caught

Did this information help you to resolve the problem?

Yes: My problem was resolved.
No: The information was not helpful / Partially helpful.
 Refresh