%1: Failed to start or stop the protocol instance. Possible causes are failure to open the metabase; failure to set the start or stop command; or failure to start or stop protocol instance in a timely fashion.

Details
Product: Exchange
Event ID: 1008
Source: MSExchangeCluster
Version: 6.5.0000.0
Message: %1: Failed to start or stop the protocol instance. Possible causes are failure to open the metabase; failure to set the start or stop command; or failure to start or stop protocol instance in a timely fashion.
   
Explanation
You will receive the following phrase in the Event Description:

%1 : Failed to set the start bit in the metabase in order to start the protocol;

check if any process in the system is dead.

NOTE: %1: will be replaced with one of the following:

Exchange IMAP4 Virtual Server Instance – (VIRTUAL SERVER NAME):

[Storage Group Name] Exchange Virtual HTTP Server:

Exchange SMTP Virtual Server Instance – (VIRTUAL SERVER NAME):

Exchange POP3 Virtual Server Instance – (VIRTUAL SERVER NAME):

Exchange NNTP Virtual Server Instance – (VIRTUAL SERVER NAME):

The causes for this error are many.  Some of the common causes and their

resolutions are listed below.

  • Cause 1 – The following setting in the metabase is set to 0 (data==0): 

    Id: ClusterEnabled.

  • Cause 2 – When updating Exchange to a new service pack, you receive this

    message because you have configured too many storage groups.

  • Cause 3 – The specific protocol container is missing in the Active

    Directory under CN=Protocols.

  • Cause 4 – Networking issues such as DSaccess topology, DNS configuration,

    and Global Catalog availability have been found to cause this issue.

  • Cause 5 – There may be more than one virtual server for a protocol on a

    particular node that will not start. This can sometimes be caused by metabase
    corruption on that node.

   
User Action
  • Resolution 1 – Use MetaEdit to change the “Id: ClusterEnabled” setting on

    the cluster nodes that this issue occurs on.

  • Resolution 2 – In an Active/Passive Cluster, configure up to four storage

    groups with a maximum of five mailbox stores or groups for each Exchange

    virtual server. In an Active/Active Cluster, configure up to four storage

    groups with a maximum of five mailbox stores or groups for each cluster.

  • Resolution 3 – Restore the specific protocol container from backup.

    Alternatively you can move all users and public folders from this server and

    remove and recreate the cluster Exchange System Attendant.

  • Resolution 4 – Check DSaccess topology, DNS configuration, and Global

    Catalog availability.

  • Resolution 5 – Create a new functioning virtual server for the protocol on

    that node and remove the virtual server for the node that will not start. 

    If creating a new virtual server does not work, and metabase corruption is

    suspected, it may be necessary to delete the System Attendant resource, and then

    recreate all the resources.  If all else fails, you may have to reinstall Internet Information Server and Exchange on that node.

Related:

Leave a Reply