KnowledgeBase Event Repository

This site is the central interface to the Adiscon Event Repository

  • Event ID
    Items count
    Access count
  • 7000
    The %1 service failed to start due to the following error: %n%2
    1
    6890 Views
  • 7001
    The %1 service depends on the %2 service which failed to start because of the following error: %n%3
    1
    1690 Views
  • 7002
    The %1 service depends on the %2 group and no member of this group started.
    1
    956 Views
  • 7003
    The %1 service depends on the following nonexistent service: %2
    1
    1222 Views
  • 7005
    The %1 call failed with the following error: %n%2
    1
    1365 Views
  • 7006
    The %1 call failed for %2 with the following error: %n%3
    1
    1160 Views
  • 7007
    The system reverted to its last known good configuration. The system is restarting....
    1
    927 Views
  • 7008
    No backslash is in the account name.
    1
    711 Views
  • 7009
    Timeout (%1 milliseconds) waiting for the %2 service to connect.
    1
    3682 Views
  • 7010
    Timeout (%1 milliseconds) waiting for ReadFile.
    1
    813 Views
  • 7011
    Timeout (%1 milliseconds) waiting for a transaction response from the %2 service.
    2
    2663 Views
  • 7012
    Message returned in transaction has incorrect size.
    1
    820 Views
  • 7013
    Logon attempt with current password failed with the following error: %n%1
    1
    919 Views
  • 7014
    Second logon attempt with old password also failed with the following error: %n%1
    1
    688 Views
  • 7015
    Boot-start or system-start driver (%1) must not depend on a service.
    1
    754 Views
  • 7016
    The %1 service has reported an invalid current state %2.
    1
    1081 Views
  • 7017
    Detected circular dependencies demand starting %1.
    1
    1122 Views
  • 7018
    Detected circular dependencies auto-starting services.
    1
    1185 Views
  • 7019
    Circular dependency: The %1 service depends on a service in a group which starts later.
    1
    753 Views
  • 7020
    Circular dependency: The %1 service depends on a group which starts later.
    1
    708 Views
  • 7021
    About to revert to the last known good configuration because the %1 service failed to start.
    1
    796 Views
  • 7022
    The %1 service hung on starting.
    1
    2050 Views
  • 7023
    The %1 service terminated with the following error: %n%2
    1
    1690 Views
  • 7024
    The %1 service terminated with service-specific error %2.
    1
    5889 Views
  • 7025
    At least one service or driver failed during system startup. Use Event Viewer to examine the event ...
    1
    1075 Views
  • 7026
    The following boot-start or system-start driver(s) failed to load: %1
    1
    49143 Views
  • 7027
    Windows 2000 could not be started as configured. A previous working configuration was used instead.
    1
    937 Views
  • 7028
    The %1 Registry key denied access to SYSTEM account programs so the Service Control Manager took own ...
    1
    1878 Views
  • 7029
    Service Control Manager %0
    1
    816 Views
  • 7030
    The %1 service is marked as an interactive service. However, the system is configured to not allow ...
    1
    3897 Views
  • 7031
    The %1 service terminated unexpectedly. It has done this %2 time(s). The following corrective acti ...
    1
    1744 Views
  • 7032
    The Service Control Manager tried to take a corrective action (%2) after the unexpected termination ...
    1
    3474 Views
  • 7033
    The Service Control Manager is not initialized successfully therefore thesystem is shutting down. Se ...
    1
    808 Views

About the KnowledgeBase Event Repository

This is a repository of known Windows Events, hopefully together with a description of what it means, when it appears and how to troubleshoot it. The event repository was initially provided as a tool for parser creation but has since evolved. It is now part of the overall knowledgebase in the hope that it provides a useful service to the community. Please add your comments and questions (which we try to answer), as this increases the event repository usefulness for all of us.
cron