none
Error Codes 2601, 2604, and 2501 RRS feed

  • Question

  • My company has just migrated a new exchange server, and we are currently having the error codes  2601, 2604, and 2501. See below the full error details. I have read microsofts facts about it not seeing the correct forest, however, it does. Any help?

     

    ERRORS:

    Process MSEXCHANGEADTOPOLOGY (PID=1280). When initializing a remote procedure call (RPC) to the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the SID for account <WKGUID=DC1301662F547445B9C490A52961F8FC,CN=Microsoft Exchange,CN=Services,CN=Configuration,...> - Error code=8007077f. 

    Process MSEXCHANGEADTOPOLOGY (PID=1280). When updating security for a remote procedure call (RPC) access for the Exchange Active Directory Topology service, Exchange could not retrieve the security descriptor for Exchange server object APEXC01 - Error code=8007077f.  The Exchange Active Directory Topology service will continue with limited permissions.

    Process MSEXCHANGEADTOPOLOGY (PID=1280). The site monitor API was unable to verify the site name for this Exchange computer - Call=DsctxGetContext Error code=8007077f. Make sure that Exchange server is correctly registered on the DNS server.

     

     

    Wednesday, November 16, 2011 7:30 PM

All replies

  • Hi,

     

    Please run  NLTest /DSGetSite to verify that the proper Active Directory Site is being returned by Windows. Once that has been verified, and then restart the MSExchange ADTopology service.

     

    I also suggest Running ExBPA to do a health check for your exchange server, if you get related information, please paste in your next post.

    http://www.microsoft.com/downloads/details.aspx?familyid=dbab201f-4bee-4943-ac22-e2ddbd258df3&displaylang=en

                     

     Best Regards,

    Lisa

    Thursday, November 17, 2011 6:42 AM
    Moderator
  • Yes the proper site name is being returned. I ran ExBPA and the only error it comes back with is database backup errors, which are nonrlevant. If it may be of help, our Exchange Server's primary dns is set to point to a BIND9 implementation.
    Sunday, November 20, 2011 10:53 PM
  • Are all the AD Sites are associated to atleast one subnet. Even that could cause this issue.
    Jasjit Singh Dhindsa | ITIL v3 | IASA Foundation Certified | MCITP: EMA 2010/2007 | MCTS: MES 2010/2007, OCS 2007 | MCSA: M+S | MCSE: M+S
    Monday, November 21, 2011 1:36 AM
  • Yes all AD/Exchange Servers are on the same subnet.
    Monday, November 21, 2011 2:52 PM
  • How many AD Sites you got and how many subnets is the AD Site and Subnet association done correctly. The Subnet to which the Exchange belong is associated to AD site ?
    Jasjit Singh Dhindsa | ITIL v3 | IASA Foundation Certified | MCITP: EMA 2010/2007 | MCTS: MES 2010/2007, OCS 2007 | MCSA: M+S | MCSE: M+S
    Monday, November 28, 2011 5:47 PM
  • We have one AD Site called "corp" and we have 3 subnets that are associated with the site, and exchange does live within one of the subnets that is associated with the site.
    Monday, November 28, 2011 7:51 PM