+ Post New Thread
Results 1 to 4 of 4
Windows Server 2000/2003 Thread, Exchange Services (Information Store) Failing to Start! in Technical; Good morning all. We had to shut down servers over the weekend due to a planned power outage, but unfortunately ...
  1. #1
    basicchannel's Avatar
    Join Date
    May 2010
    Location
    Norfolk, UK
    Posts
    279
    Thank Post
    36
    Thanked 22 Times in 14 Posts
    Blog Entries
    1
    Rep Power
    23

    Exchange Services (Information Store) Failing to Start!

    Good morning all.

    We had to shut down servers over the weekend due to a planned power outage, but unfortunately our Exchange 2003 server has not fared well. The shutdown was clean but on first boot this morning, some Exchange services weren't running. For example the Exchange Info Store is failing to start up giving me an error 1068. Checking the event logs, around every time I try to start up a failed service I get the following event:

    Code:
    Event Type:	Error
    Event Source:	MSExchangeDSAccess
    Event Category:	Topology 
    Event ID:	2114
    Date:		08/04/2013
    Time:		11:16:02
    User:		N/A
    Computer:	ExchangeServer
    Description:
    Process INETINFO.EXE (PID=1484). Topology Discovery failed, error 0x8007077f. 
    
    For more information, click http://www.microsoft.com/contentredirect.asp.
    So I'm using my really powerful Sherlock skills to guess this is related. Does anyone have any ideas? I've looked at a KB article that suggests using policytest.exe to check permissions, but I can't get hold of this.

    Thanks so much

  2. #2

    SYNACK's Avatar
    Join Date
    Oct 2007
    Posts
    11,039
    Thank Post
    852
    Thanked 2,666 Times in 2,263 Posts
    Blog Entries
    9
    Rep Power
    767
    Free Tech Answers: How to Resolve Event ID 2114 MSExchangeDSAccess Topology Discovery Failed
    Explanation:
    This problem occurs because the Exchange security groups do no have the appropriate user rights to enable the Directory Service Access (DSAccess) component to communicate with Active Directory.

    Resolution:
    Verify that the default domain policy or the default domain controllers policy is not blocked.

    Start the Active Directory Users and Computers snap-in.

    Right-click Your_Domain.Your_Root_Domain, and then click Properties.

    Click the Group Policy tab.

    In the Current Group Policy Object Links for Your_Domain window, click a Group Policy entry other than the Default Domain Group Policy entry.

    Click Options.

    Verify that the No Override: prevents other Group Policy objects from overriding policy set in this one check box is not selected. If it is selected, click to clear this check box after you make sure that the effective policy settings that you want are not changed when the default domain policy is applied.

    Click OK two times.

    Repeat steps for any other group policies that you have configured.
    Repeat steps for any organizational unit object that is located in your environment.

    Right-click Domain Controllers, and then click Properties.

    In the Current Group Policy Object Links Domain Controllers window, click a Group Policy entry other than the Default Domain Controllers Group Policy entry.

    Verify that the No Override: prevents other Group Policy objects from overriding policy set in this one check box is not selected. If it is selected, click to clear this check box after you make sure that the effective policy settings that you want
    are not changed when the default domain controllers policy is applied.

    Click OK two times.

    Exit the Active Directory Users and Computers snap-in.

    Wait for this change to replicate to all other domain controllers.

    Use the Policytest tool (Policytest.exe) to troubleshoot permissions. Policytest.exe is located on the Exchange Server 2003 or Exchange 2000 Server CD in the Support\Utils\I386 folder. Use Policytest.exe to determine whether the Manage auditing and security logs permission for the Exchange Enterprise Servers group is missing on any of the domain controllers.

    A successful result returns information that resembles the following:
    Local domain is"" (EXAMPLE) Account is"EXAMPLE\Exchange Enterprise Servers" ======================== DC ="" In site ="" Right found:"SeSecurityPrivilege"

    Note A successful result shows that the Manage auditing and security logs permission exists. You must have domain administrator rights to run Policytest.exe successfully. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
    281537 (XADM: Description of the Policytest.exe Utility ) Description of the Policytest.exe utility

    Reset the Exchange Enterprise Server default permissions at the domain level:
    Run the setup /domainprep command from the Exchange Server 2003 or Exchange 2000 Server CD or from a network installation point. This command adds the Exchange Enterprise Servers group to the domain together with default permissions. When you run this command, the permissions are immediately added to one domain controller. The change then replicates to the other domain controllers.

    Restore permissions inheritance to other organizational units. Then, wait for the domain controllers to replicate the changes throughout the domain.

    Run Policytest.exe, and then note which domain controllers return the following successful result:
    Right found:"SeSecurityPrivilege"

    If all the domain controllers have the correct permissions, restart the Exchange services.

    If no domain controllers have the appropriate permissions,
    Verify the default domain controllers policy:
    Start the Active Directory Users and Computers snap-in.

    Right-click the Domain Controllers container, and then click Properties.

    Click the Group Policy tab, and then make sure that Default Domain Controllers Policy is listed in the Current Group Policy Object Links for Your_Domain window. If it is not, click Add, click Default Domain Controllers Policy, and then click OK. Then, wait for this change to replicate to all other domain controllers.
    Run the setup /domainprep command from the Exchange Server 2003 or Exchange 2000 Server CD or from a network installation point. This command adds the Exchange Enterprise Servers group to the domain together with default permissions.
    Run Policytest.exe, and then note which domain controllers return the following successful result:
    Right found:"SeSecurityPrivilege"

    If all the domain controllers have the correct permissions, restart the Exchange services.

    If some domain controllers do not have the correct permissions,
    Manually add permissions to the domain controller.

    The File Replication service (FRS) may not replicate the updated security policy to one or more domain controllers after you run the setup /domainprep command. If this occurs, you must manually assign the correct permissions to the Exchange Enterprise Servers group. If some or all domain controllers do not have the correct permissions, assign the Exchange Enterprise Servers group the Manage auditing and security logs permission. Then, wait for the setting to replicate to the other domain controllers.

    Start the Active Directory Users and Computers snap-in.

    Right-click the Domain Controllers container, and then click Properties.

    Click the Group Policy tab, click Default Domain Controllers Policy in the Group Policy Object Links box, and then click Edit.

    Expand Computer Configuration, expand Windows Settings, expand Security Settings, expand Local Policies, and then click User Rights Assignment.

    In the right pane, double-click Manage auditing and security log, click Add, click Browse, and then add the Exchange Enterprise Servers group.

    In the Add user or group dialog box, click OK, and then click OK again.

    Exit the Group Policy snap-in, and then click OK in the Domain Controllers Properties dialog box.

    Note Sometimes, you may not be able to see the Exchange Enterprise Servers group when you click Browse in the Add user or group dialog box. If this occurs, add the Exchange Domain Servers group, and then run the setup /domainprep command again. This process makes the addition of the Exchange Enterprise Servers group by the setup /domainprep command persist across all domain controllers.

    Restart the Exchange services.
    Exchange services do not start, and event IDs 2114 and 2112 are logged in the Application log in Exchange Server 2003 or in Exchange 2000 Server
    Event ID: 2114 Source: MSExchangeDSAccess
    MSExchangeDSAccess Error: 2114 - Windows Events - Spiceworks

  3. #3
    basicchannel's Avatar
    Join Date
    May 2010
    Location
    Norfolk, UK
    Posts
    279
    Thank Post
    36
    Thanked 22 Times in 14 Posts
    Blog Entries
    1
    Rep Power
    23
    In the Current Group Policy Object Links for Your_Domain window, click a Group Policy entry other than the Default Domain Group Policy entry.
    We only have one entry in here - the Default Domain Group Policy entry, so we can't click on an entry other than this.

    Use the Policytest tool (Policytest.exe) to troubleshoot permissions. Policytest.exe is located on the Exchange Server 2003 or Exchange 2000 Server CD in the Support\Utils\I386 folder. Use Policytest.exe to determine whether the Manage auditing and security logs permission for the Exchange Enterprise Servers group is missing on any of the domain controllers.
    I haven't got an exchange 2000/2003 CD, so unless there's any other way I can get hold of policytest.exe then this isn't possible.

  4. #4
    basicchannel's Avatar
    Join Date
    May 2010
    Location
    Norfolk, UK
    Posts
    279
    Thank Post
    36
    Thanked 22 Times in 14 Posts
    Blog Entries
    1
    Rep Power
    23
    Seems like it was something to do with the exchange server trying to contact old instances of a domain controller. We removed them and it's all fine now. School boy error perhaps, but why it decided to manifest itself now I don't know. The quicker we upgrade the better.

SHARE:
+ Post New Thread

Similar Threads

  1. Netlogon service failed to start- invalid argument error 10022
    By Liam in forum Windows Server 2008 R2
    Replies: 0
    Last Post: 26th November 2012, 07:08 PM
  2. Replies: 0
    Last Post: 19th January 2012, 05:17 PM
  3. The MRMonitor service failed to start
    By bondbill2k2 in forum Windows Server 2000/2003
    Replies: 1
    Last Post: 11th October 2011, 01:36 PM
  4. WDS services fails to start
    By tomscaper in forum Windows Server 2008
    Replies: 17
    Last Post: 3rd August 2010, 10:40 AM
  5. MSI fails to start service
    By Lithium in forum Windows
    Replies: 3
    Last Post: 23rd June 2008, 03:36 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •