none
Exchange 2013SP1+2012R2 - DAG: Seeding Failed!

    Question

  • Hi to all,

    i have a problem activating database copy on DAG cluster:

    System: Windows Server 2012R2 + Exchange Server 2012SP1

    - Dag create:

    New-DatabaseAvailabilityGroup -Name FirstDag -WitnessServer srv01 -DatabaseAvailabilityGroupIPAddresses ([System.Net.IPAddress])::None

    - Adding members:

    Add-DatabaseAvailabilityGroupServer -Identity FirstDag -MailboxServer EX01

    Add-DatabaseAvailabilityGroupServer -Identity FirstDag -MailboxServer EX02

    - No errors, all ok.

    Name             Member Servers
    ----             --------------
    FirstDag         {EX02, EX01

    - Adding copy of database:

    Add-MailboxDatabaseCopy -Identity SpecialUsers -MailboxServer EX02 -ActivationPreference 2

    ERROR!:

    The seeding operation failed. Error: An error occurred while performing the seed operation. Error: A timeout occurred
    while communicating with server 'EX01'. Error: "A connection could not be completed within 15 seconds." [Database:
    SpecialUsers, Server: EX02]

    No network problem between cluster nodes, but the copy remain in "Failed and Suspended"

    - Forcing reseed:

    Update-MailboxDatabaseCopy SpecialUsers\EX02 -CatalogOnly

    ERROR!:

    WARNING: Seeding of content index catalog for database 'SpecialUsers' failed. Please verify that the Microsoft Search
    (Exchange) and the Host Controller service for Exchange services are running and try the operation again. Error: There
    was no endpoint listening at
    net.tcp://localhost:3863/Management/SeedingAgent-17BDDA50-B2EE-4410-A53B-4AD967CAA2DA12/Single that could accept the
    message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more

    local and remote port 3863 is open.

    Pls, i need help about this issue!

    Thanks!

    Thursday, April 10, 2014 7:55 PM

Answers

  • Hi Belinda,

    i have solved the problem :)

    The issue was about the loopback adapter (!), disabling it solved the problem.

    Thanks for your message!

    • Marked as answer by UgoCat Friday, April 11, 2014 9:13 AM
    Friday, April 11, 2014 9:12 AM

All replies

  • Hi,

    How many NIC did you have for DAG members? It is recommended to have two NICs.

    For this issue, please make sure the Microsoft Exchange Search service, the Microsoft Exchange Search Host Controller service and the Microsoft Exchange Replication service are running.

    The error mentioned that a timeout occurred while communicating with server, please try to ping each other in DAG to check the result.

    Best regards,
    Belinda


    Belinda Ma
    TechNet Community Support


    Friday, April 11, 2014 7:15 AM
    Moderator
  • Hi Belinda,

    i have solved the problem :)

    The issue was about the loopback adapter (!), disabling it solved the problem.

    Thanks for your message!

    • Marked as answer by UgoCat Friday, April 11, 2014 9:13 AM
    Friday, April 11, 2014 9:12 AM
  • Hi,

    It's glade to hear the good news. Thanks for your update.

    Best regards,


    Belinda Ma
    TechNet Community Support

    Friday, April 11, 2014 9:16 AM
    Moderator
  • Hi

    Please help me, i have the same issue, detail me the solution please?

    Tuesday, June 5, 2018 9:42 PM