[Webinar] Streamline your web hosting managementRegister Today

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 403
  • Last Modified:

Changing the time threshold before Windows reports event ID 7022

We have just installed an e-mail continuity system that is causing Windows Server 2003 to report event ID 7022 "Service hung on starting" for three of its services whenever the server is restarted.  The services are starting fine, but they take so long that Windows reports them hung.

We have tried creating a service group for the services, adding the services to the group, and specifying the group to start last (all registry edits), but Windows still reports the event.

Two questions:
A) Is there anything more to creating a service group than specifying the group name in each service's registry key by creating a REG_SZ value named Group with the name of the group in the data?

B) Is there any ability to change the time threshold that Windows will wait before reporting event ID 7022 for a particular service, or collectively for all services?
1 Solution
Justin OwensITIL Problem ManagerCommented:
A) You have done what you can.
B) Not that I am aware of.  
It is just an informational error.  It is safe to ignore if you know it is an expected entry.
Dimarc67Author Commented:
However mitigated, errors in the event logs and on the console demand support technicians to investigate unless they have first-hand knowledge of the mitigating factors.  Suggesting an error can be ignored is not an option in a large enterprise environment with multiple support personnel and environments.

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now