Event ID 4209: Could not obtain the service entry identifier for this service is generated when starting the Enterprise Vault services.

book

Article ID: 100018716

calendar_today

Updated On:

Description

Error Message

Type: Error
Event: 4209
Source: Enterprise Vault
Category: Storage Server
Description:
Could not obtain the service entry identifier for this service
Service name:

 

Resolution

This error has been seen to occur for the following reasons
 
Scenario 1:
 
When attempting to move the 'EnterpriseVaultDirectory' Database to a SQL Server Instance where another Enterprise Vault Site is using the Default SQL Instance of the SQL Server. When running the configuration wizard the SQL Server is specified without the SQL Instance Name. Attempting to revert the Enterprise Vault Server to the old SQL Server, or to the new SQL Instance, causes the Event ID 4209 to occur when the Enterprise Vault Services are started.  This occurs because the Site ID on the Enterprise Vault Server has changed to the other Enterprise Vault Site's ID.
 
Scenario 2:

When Enterprise Vault is configured as a Cluster, and the ComputerNameAlternate value in the EnterpriseVaultDirectory Database ComputerEntry table contains the name of the node and not the virtual cluster name, this causes the cluster resources to be in a Failed state. This can also be seen in the Vault Admin Console (VAC) by expanding 'Enterprise Vault Servers' and next to the name of the EV server it displays the ComputerNameAlternate of the server, i.e EVServer1 (SERVER1).

Scenario 3:

When Enterprise Vault is configured as a Cluster, and the Failover node is being shared by two virtual servers, each having a separate EV site running but using the same EnterpriseVaultDirectory Database. When one of the virtual clusters fails over the SiteID in the registry contains the SiteID for the EV site running on the other virtual cluster. This occurs when the registry from the primary node is not being replicated to the failover node successfully.
 

 
Solution for scenario 1:
  1. Open the 'SiteEntry' table of the 'EnterpriseVaultDirectory' database of the first EV Server, copy the 'SiteEntryID'.
  2. Open 'Regedit' on the first EV Server and go to 'HKLM\Software\KVS\Enterprise Vault\' edit the 'SiteID' value and paste the correct 'SiteID'.
    • Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.
  3. Restart the 'EnterpriseVaultAdmin' Service.
Solution for scenario 2:
  1. Open the VAC while logged in as the Vault Service Account
  2. Right Click on 'Enterprise Vault Servers' and select 'Update Service Locations'
  3. Once complete the summary will confirm the ComputerAlternateName has been changed
  4. Bring the failed services online
Solution for scenario 3:
 
  1. 1. Follow step 1 in scenario 1 to obtain the SiteID for each EV site
  2. On one of the nodes type the following command in a command prompt, changing EVserver1 to the name of the virtual cluster name running EV, run this for each virtual name
    • cluster resource EVserver1-EnterpriseVaultAdminService /check
      If the results for Registry Checkpoint have a value other than none run the following command to remove the checkpoint then go to step 3, if the value is none go straight to step 3
    • On 32-bit Windows systems:
      • cluster resource EVserver1-EnterpriseVaultAdminService /removecheck:"Software\KVS\Enterprise Vault"
    • On 64-bit Windows systems:
      • cluster resource EVserver1-EnterpriseVaultAdminService /removecheck:"Software\Wow6432Node\KVS\Enterprise Vault"
  3. On one of the nodes type the following command in a command prompt, changing EVserver1 to the name of the virtual cluster name running EV, run this for each virtual name
    • cluster resource EVserver1-EnterpriseVaultServerInstance /check
  4. If the results for the Registry Checkpoint have a value of the registry path seen at the commands below, you may need to log a call with Microsoft to determine why the registry is not being replicated, if the value is none, run the command below to create a Registry Checkpoint, again changing EVserver, and run for each virtual name
    • On 32-bit Windows systems:
      • cluster resource EVserver1-EnterpriseVaultServerInstance /addcheck:"Software\KVS\Enterprise Vault"
    • On 64-bit Windows systems:​​​​​​​
      • cluster resource EVserver1-EnterpriseVaultServerInstance /addcheck:"Software\Wow6432Node\KVS\Enterprise Vault"
  5. Now perform a failover and confirm the SiteID in the registry contains the correct SiteID and the services come online, if the registry is not replicating correctly you may need to contact Microsoft

    ​​​​​​​Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

Issue/Introduction

Event ID 4209: Could not obtain the service entry identifier for this service is generated when starting the Enterprise Vault services.
Powered by Wolken Software