Event ID 7011 "SERVER1.MYDOMAIN.COM A timeout (30000 milliseconds) was reached while waiting for a transaction response from the LanmanServer service" is reported by the System Log

book

Article ID: 100005026

calendar_today

Updated On:

Description

Error Message

 

### System Event Log

01/18/2011        12:55:56 PM        ERROR     7011(0xc0001b63)         Service Control Manager                SERVER1.MYDOMAIN.COM A timeout (30000 milliseconds) was reached while waiting for a transaction response from the LanmanServer service.

01/18/2011        12:56:26 PM        ERROR     7011(0xc0001b63)         Service Control Manager                SERVER1.MYDOMAIN.COM A timeout (30000 milliseconds) was reached while waiting for a transaction response from the ShellHWDetection service.

 

###  Cluster Log

000017fc.00001f28::2011/01/18-00:51:08.382 ERR   [RES] Volume Manager Disk Group : LDM_RESResourceControl: CLUSCTL_RESOURCE_STORAGE_IS_PATH_VALID Status = 3, BytesReturned = 0

000017fc.00001f28::2011/01/18-00:51:08.382 INFO  [RES] Volume Manager Disk Group : LDM_RESResourceControl: *** CLUSCTL_RESOURCE_STORAGE_IS_PATH_VALID error.  Unable to get majority reservation

Cause

The issue is caused as Enterprise Vault's Convert to Cluster wizard does not remove ethe existing LanmanServer Shares.

The LanmanServer Share registry entry is created by windows when share a folder before configuring a cluster. LanmanServer service uses these to maintain the share. 

Once a FileShare resource is configured in cluster these keys are not required as shares will be maintained by FileShare resource configured. Also creating a share after configuring the FileShare resource will not create these registry entries.

 

 

Resolution

Remove the existing LanmanServer Shares before running Enterprise Vault's Conver to Cluster wizard.

If the wizard is already run then the issue can be resolved by removing the stale LanmanServer Shares:

- net stop clussvc

- net stop lanmanserver

- Open registry editor (regedit)

- Take backup of following registry key (export to a registry file)
   HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Shares

- Remove all values from this key HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Shares for example (B$, F$, EVPartition01cbad4f7c914d30$, EVPartition01cbad527af87d60$, EVPartition01cbb085e28977f0$, EVPartition01cbb0860def1670$, EVPartition01cbb08635baec60$)

- net start lanmanserver

net stop clussvc

 

 

Applies To

  • Windows Server 2008 R2 Failover Cluster
  • Storage Foundation for Window 5.1 SP2
  • Enterprise Vault 8.0 SP5

-  An existing Enterprise Vault installation has been converted to Windows Server 2008 R2 Failover Cluster using Enterprise Vault's Conver to Cluster wizard.

- The LanmanServer Shares exist in the registry for example:

HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Shares (B$, F$, EVPartition01cbad4f7c914d30$, EVPartition01cbad527af87d60$, EVPartition01cbb085e28977f0$, EVPartition01cbb0860def1670$, EVPartition01cbb08635baec60$)

Issue/Introduction

When an existing Enterprise Vault server is converted to Windows 2008 R2 Failover Cluster using Enterprise Vault's Convert to Cluster wizard, the wizard does not remove the existing LanmanServer Shares and causes Volume Manager Diskgroup (VMDG) resource fails to online and times out.