Microsoft Exchange Address Book Service will not start after migration from exchange 2007 to Exchange 2001.
Introduction :
one of EE users have question that after migration from exchange 2007 to exchange 2010 found that outlook users will not work fine , after investigations i found that he need to reconfigure client access and auto discover , it was working fine after reconfigure steps but an strange problem appears that Microsoft Address Book Services will not start , the user said that he spent 2 days searching on internet but no solution found , i found the solution and here is steps and descriptions :
Problem:
This problem is one of rare problems that maybe occurred after migrating from Exchange 2007 to Exchange 2010 , the user may need to re-configure auto discover and Outlook anywhere , however for unknown case the “Exchange Address Book Service “ stop working and following events are found on Event Viewer :
Event ID: 7000
Description:
The Microsoft Exchange Address Book Service Failed to start due to the following Error:
The service did not respond to the start or control request in a timely fashion.
Introduction :
one of EE users have question that after migration from exchange 2007 to exchange 2010 found that outlook users will not work fine , after investigations i found that he need to reconfigure client access and auto discover , it was working fine after reconfigure steps but an strange problem appears that Microsoft Address Book Services will not start , the user said that he spent 2 days searching on internet but no solution found , i found the solution and here is steps and descriptions :
Problem:
This problem is one of rare problems that maybe occurred after migrating from Exchange 2007 to Exchange 2010 , the user may need to re-configure auto discover and Outlook anywhere , however for unknown case the “Exchange Address Book Service “ stop working and following events are found on Event Viewer :
Event ID: 7000
Description:
The Microsoft Exchange Address Book Service Failed to start due to the following Error:
The service did not respond to the start or control request in a timely fashion.
And
Event ID 7009
Description:
A timeout was reached (3000 milliseconds) while waiting for Microsoft Exchange Address Book Service to Connect.
Symptoms:
The user side will connect to exchange server but updating take very long time which is result on failed on Outlook connection.
Resolution:
After long search on internet there is no solution found for this case , I have found by myself that address book service required ports to be defined on registry after reviewing the registry values required for ports to be defined , I found that these values were absent , this was the reason that why service stop responding and no longer able to start.
Here we are :
Start -> run regedit.exe
Follow these registry key:
HKEY_LOCAL_MACHINE\SYSTEM\
create new REG_DWORD
name "TCP/IP Port"
assigned value : 59532 (Decimal)
then follow this key :
HKEY_LOCAL_MACHINE\SYSTEM\
created new String Value REG_SZ
Name "RpcTcpPort" (without quotation)
value : 59533
then close regedit …start Microsoft Address Book Services , it works fine...
Disclaimer: This article came about because of a question that the author was able to assist with. Setting the port number should not be a requirement to resolve this issue, and perhaps it was coincidence that it worked, but it is presented as a possible work-around if more traditional fixes have failed.
here is additional useful resources related to this article :
http://social.technet.micr
Recommended reading : http://technet.microsoft.c
Regards
Maen Abu-Tabanjeh
IT Manager.
Amman - Jordan
by: demazter on 2012-01-03 at 11:45:10ID: 34114
The only reason you would configure the RPC ports to be static were if you were trying to allow these ports through a firewall and therefore need to specify which ones is used rather than the randomly assigned port from a pool associated with the services.
However, one would argue that if this is the case then you would use RPC-HTTPS or Outlook Anywhere as it is known in the later versions of Exchange Server, which would negate the need to do this.
Those registry entries do not exist on a standard Exchange Server installation.
This is correct, that's how they should be, they are missing because that is the default configuration and should therefore not have been the cause of the errors that were being received.
My guess is if these settings were now removed from the registry the service would still continue to run. This would point to something else causing the problem.
The configuation outlined in this article would need to be applied to every Exchange Server in the organisation, and if it wasn't, you would experience connectivity issues.
This could also cause problems when trying to migrate at a later stage to a new version of Exchange.
I would urge any potential readers to avoid making these types of configuration changes and instead identify where the problem actually lies and resolve it.