If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.
Microsoft Exchange Address Book Service will not start after migration from exchange 2007 to Exchange 2010
Published on
19,175 Points
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.
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.microsoft.com/wiki/contents/articles/configure-static-rpc-ports-on-an-exchange-2010-client-access-server.aspx
Recommended reading : http://technet.microsoft.com/en-us/library/ee332317.aspx
Regards
Maen Abu-Tabanjeh
IT Manager.
Amman - Jordan
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.microsoft.com/wiki/contents/articles/configure-static-rpc-ports-on-an-exchange-2010-client-access-server.aspx
Recommended reading : http://technet.microsoft.com/en-us/library/ee332317.aspx
Regards
Maen Abu-Tabanjeh
IT Manager.
Amman - Jordan
-
7
4
12 Comments
The solution offered by this article, in my opinion is purely coincidental.
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.
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.
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.
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.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.
@demazter :
the Ironically that happened when i found this solution that firewall already stopped and disabled and i disabled it , note that i think creating these ports even will not affect on exchange if this was not solution if any user want to try my solution if registry port definition was not useful exchange will continue working so he can delete the ports if he wish , this what make me gonna crazy , the ports was not exist from the beginning , i doubt that the problem was communicating with address book services , before i tried to start the service again (Address book service ) , i stopped windows firewall service and disable it , tried to start address book service again , it does not started.. this really strange but possible to be happened with some users.
the Ironically that happened when i found this solution that firewall already stopped and disabled and i disabled it , note that i think creating these ports even will not affect on exchange if this was not solution if any user want to try my solution if registry port definition was not useful exchange will continue working so he can delete the ports if he wish , this what make me gonna crazy , the ports was not exist from the beginning , i doubt that the problem was communicating with address book services , before i tried to start the service again (Address book service ) , i stopped windows firewall service and disable it , tried to start address book service again , it does not started.. this really strange but possible to be happened with some users.
Active 3 days ago
Did you look at the following KB Article and check the services were configured to start using the correct accounts ?:
http://support.microsoft.com/kb/314357
If you stopped the firewall, then it would very much surprise me if it was a port issue as the firewall would have allowed Exchange to communicate unhindered, thus it sounds very much like a completely different problem and the registry tweak seems unnecessary.
http://support.microsoft.com/kb/314357
If you stopped the firewall, then it would very much surprise me if it was a port issue as the firewall would have allowed Exchange to communicate unhindered, thus it sounds very much like a completely different problem and the registry tweak seems unnecessary.
Active 3 days ago
You may also want to consider looking at the following article:
http://www.itexperience.net/event-id-7009-timeout-30000-milliseconds-waiting-for-the-microsoft-exchange-service-host-service-to-connect/
Extract:
The cause of these error events is the lack of internet access. It seems that both services try to download a revoked certificate list from http://crl.microsoft.com, and time out if they don’t have access to this.
There are a couple of options to solve this problem:
If you have a proxy server, you may have to set the correct proxy settings. Use ProxyCfg.exe to set the ip address and port.
If you have a firewall, Internet traffic may be blocked by it. In that case, open HTTP traffic from the server to the internet
If you have installed .NET Framework 2.0 only, you may need a hotfix for .NET Framework 2. Microsoft has a KB article which desribes the same problem, and from where you can request a hotfix: Exchange 2007 managed code services do not start after you install an update rollup for Exchange 2007
http://www.itexperience.net/event-id-7009-timeout-30000-milliseconds-waiting-for-the-microsoft-exchange-service-host-service-to-connect/
Extract:
The cause of these error events is the lack of internet access. It seems that both services try to download a revoked certificate list from http://crl.microsoft.com, and time out if they don’t have access to this.
There are a couple of options to solve this problem:
If you have a proxy server, you may have to set the correct proxy settings. Use ProxyCfg.exe to set the ip address and port.
If you have a firewall, Internet traffic may be blocked by it. In that case, open HTTP traffic from the server to the internet
If you have installed .NET Framework 2.0 only, you may need a hotfix for .NET Framework 2. Microsoft has a KB article which desribes the same problem, and from where you can request a hotfix: Exchange 2007 managed code services do not start after you install an update rollup for Exchange 2007
hey alan ,
i tried many solutions , i check the service account , which was correct , i tried to start the service when firewall is running the service will not work , i stopped the firewall and start the service will not start , other workaround , i set the service to "Automatic (Delay on the start) , also its not working , after these tries , the definition of the ports on the registry was last solution which its work , also want to tell you that i searched for 2 days on internet , many people have the same of my issue and same Event ID , and they did not find any proper solution for this case.
i tried many solutions , i check the service account , which was correct , i tried to start the service when firewall is running the service will not work , i stopped the firewall and start the service will not start , other workaround , i set the service to "Automatic (Delay on the start) , also its not working , after these tries , the definition of the ports on the registry was last solution which its work , also want to tell you that i searched for 2 days on internet , many people have the same of my issue and same Event ID , and they did not find any proper solution for this case.
alan i made some investigation with user he said its stopped suddenly i checked event viewer nothing was clear... am sure that even users tries to define ports on registry it will not affect on the service if this solution was not success.
actually the solution found after following the article that i mentioned above :
http://social.technet.microsoft.com/wiki/contents/articles/configure-static-rpc-ports-on-an-exchange-2010-client-access-server.aspx
which is microsoft article , i doubt that there is problem with communicating address book distribution with RPC , but since many users and experts told me the definition of the ports will not affect on the service if created or deleted , so why Microsoft need to publish such article above?
big confusion.
http://social.technet.microsoft.com/wiki/contents/articles/configure-static-rpc-ports-on-an-exchange-2010-client-access-server.aspx
which is microsoft article , i doubt that there is problem with communicating address book distribution with RPC , but since many users and experts told me the definition of the ports will not affect on the service if created or deleted , so why Microsoft need to publish such article above?
big confusion.
the problem it was Exchange 2007 SP3 .. this the fun.
i tried every bit of solution..but was no luck before this solution.
i tried every bit of solution..but was no luck before this solution.
Active 3 days ago
I would have been interested to see what Microsoft's solution would have been.
After a few hours of searching fruitlessly, I would have been straight on the phone.
After a few hours of searching fruitlessly, I would have been straight on the phone.
Featured Post
R is considered the predominant language for data scientist and statisticians. Learn how to use R for your own data science projects.
Suggested Articles
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync.
To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…
