Saturday, September 14, 2013

Unable to register the MSExchangeAB RPC interface. Failed with the error code The endpoint is a duplicate (1740) and The Microsoft Exchange RPC service can't be started because the EMSMDB interface is already registered by another process.

Issue: -

Microsoft Exchange Address Book and Microsoft RPC Client Access Service are not started after setup Static Ports.

Error Message: -

Address Book Service: -

Unable to register the MSExchangeAB RPC interface. Failed with the error code The endpoint is a duplicate (1740)

Microsoft RPC Client Access Service: -

The Microsoft Exchange RPC service can't be started because the EMSMDB interface is already registered by another process.

Error Statement: -

When you Setup Static Ports for Microsoft Exchange Address Book and Microsoft RPC Client Access Services and if the same Port is already used by another service which can result service start fail.
You can follow the below steps to configure the static ports,

UDP/TCP 59531-65535; set static ports

To set a static port for the RPC Client Access service on an Exchange 2010 Client Access server, you need to open the registry on the respective server and navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MSExchangeRPC


Here, you need to create a new key named ParametersSystem, and under this key create a REG_DWORD named TCP/IP Port. The Value for the DWORD should be the port number you want to use.


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MSExchangeRPC\ParametersSystem]
"TCP/IP Port"=dword:0000e88c

To set a static RPC port for the Exchange Address Book Service, create a new REG_SZ registry key named “RpcTcpPort” under:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MSExchangeAB\Parameters]
"RpcTcpPort"="59533"

Resolution: -

   1.  Find whether same port used by another process by using NETSTAT command.
  TCP    10.250.172.59:59499    10.250.172.58:55163    ESTABLISHED
  TCP    10.250.172.59:59519    10.250.172.41:135      ESTABLISHED
  TCP    10.250.172.59:59520    10.250.172.41:36553    ESTABLISHED
  TCP    10.250.172.59:59521    10.250.172.41:36553    ESTABLISHED
  TCP    10.250.172.59:59532    10.250.172.62:135      ESTABLISHED
  TCP    10.250.172.59:59533    10.250.172.62:14417    ESTABLISHED
  TCP    10.250.172.59:59534    10.250.172.62:14417    ESTABLISHED
  TCP    10.250.172.59:59545    10.250.172.49:37827    ESTABLISHED
  TCP    10.250.172.59:59546    10.250.172.49:37827    ESTABLISHED
  TCP    10.250.172.59:59723    10.250.172.62:135      ESTABLISHED
  TCP    10.250.172.59:59724    10.250.172.62:14417    ESTABLISHED
  TCP    10.250.172.59:59725    10.250.172.62:14417    ESTABLISHED
  TCP    10.250.172.59:59847    10.250.172.48:9747     ESTABLISHED
  TCP    10.250.172.59:60179    10.250.172.52:21192    ESTABLISHED
  TCP    10.250.172.59:60535    10.250.32.17:389       ESTABLISHED

   2.  Restart Microsoft Information Store service which will release if the same port used.
   3.  Check which service is using that ports using NETSTAT /autob
[w3wp.exe]
  TCP    10.250.172.59:59520    10.250.172.41:36553    ESTABLISHED     19184
 [w3wp.exe]
  TCP    10.250.172.59:59521    10.250.172.41:36553    ESTABLISHED     19184
 [w3wp.exe]
  TCP    10.250.172.59:59532    10.250.172.62:135      ESTABLISHED     19184
 [w3wp.exe]
  TCP    10.250.172.59:59533    10.250.172.62:14417    ESTABLISHED     19184
 [w3wp.exe]
  TCP    10.250.172.59:59534    10.250.172.62:14417    ESTABLISHED     19184
 [w3wp.exe]
  TCP    10.250.172.59:59545    10.250.172.49:37827    ESTABLISHED     19184
 [w3wp.exe]
  TCP    10.250.172.59:59546    10.250.172.49:37827    ESTABLISHED     19184

   4.  After found which service using (In my cause w3wp.exe service) restart it.
   5.   If above steps is not resolved your issue, Please restart your server    by setup services in automatic mode.

Thanks
Keep Visiting