none
Exchange 2019 DAG - can only add one server RRS feed

  • Question

  • Hi

    Currently adding new Exchange 2019 servers in my test lab environment. Set up consists of 3 DAGs

    1 x Exchange 2013 DAG (2 2013 servers)

    1 x Exchange 2016 DAG (2 2016 servers)

    I've just created a new Exchange 2019 DAG...

    The problem is I'm only able to add one server to the DAG. If I attempt to add a second server then I get the following error:

    <label style="font-weight:bold;">ERROR</label>

    ScriptingAgent: Exception thrown while invoking scriptlet for Validate API: The network path was not found. .

    To clarify either server can be a member of the DAG on their own, just not both together.

    Server1 added, cannot add Server 2

    Server 2 added, cannot add Server1

    Can anyone shed any light on this as I've never seen this issue with other DAGs created in the past.?

    Thanks in advance


    Matt

    Thursday, September 19, 2019 7:01 PM

Answers

  • Update:

    I managed to fix this issue myself by running the following command in EWS:

    Disable-CmdletExtensionAgent "Scripting Agent"

    Folowing on from this, I was able to add the second server into the DAG successfully without errors.

    Not sut sure at this point if I had enabled Scripting Agent a while ago and forgotten about it, but as far as I'm aware the default state for the Scripitng Agent is disabled.

    If anyone can clarify the part the Scripting Agent plays in DAG server additions, and/or it's default status then that may be useful for all of us for future reference.


    Matt

    • Marked as answer by Matt_Pollock Tuesday, September 24, 2019 8:02 AM
    Tuesday, September 24, 2019 8:02 AM

All replies

  • Hi

    Are you getting that error in the EAC or using the EMS?


    Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Thursday, September 19, 2019 7:21 PM
    Moderator
  • Hi

    Are you getting that error in the EAC or using the EMS?


    Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Both EAC and EMS

    Matt

    Thursday, September 19, 2019 7:21 PM
  • Is this an IPLess DAG? Also, are you running 2013, 2016, and 2019 in the same Forest? Cause that would be a little wonky, I think.
    Thursday, September 19, 2019 7:37 PM
  • Is this an IPLess DAG? Also, are you running 2013, 2016, and 2019 in the same Forest? Cause that would be a little wonky, I think.

    Yep, IP-less DAG.

    All DAG s in Sam forest. The plan is to decommission the 2016 DAG once all mailboxes have been migrated to 2019.

    What is the issue with multiple DAGs in the same forest?


    Matt

    Thursday, September 19, 2019 7:53 PM
  • Hi Matt,

    Are Exchange 2019 servers on the same site?

    Use the following command to check your DAG configuration, make sure witness server is set correctly:

    Get-DatabaseAvailabilityGroup <DAG name> |fl 

    You can reproduce this issue and check if any related event log are generated for further analysis. Here is a similar thread, hope you can get some information from it: Error Adding Mailbox Server to DAG

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Friday, September 20, 2019 9:01 AM
    Moderator
  • Hi Matt,

    Are Exchange 2019 servers on the same site?

    Use the following command to check your DAG configuration, make sure witness server is set correctly:

    Get-DatabaseAvailabilityGroup <DAG name> |fl 

    You can reproduce this issue and check if any related event log are generated for further analysis. Here is a similar thread, hope you can get some information from it: Error Adding Mailbox Server to DAG

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Hello,

    I've tried several times to recreate the DAG and add the servers.

    Still no further forward.

    Here is the output from

    Get-DatabaseAvailabilityGroup <DAG name> |fl 

    RunspaceId                               : c95ce9b0-218a-49e3-aa3a-a7fc7688819d
    Name                                     : EXCH2019DAG01
    Servers                                  : {TESTLABEXCH05}
    WitnessServer                            : testlabdc01.testlab.local
    WitnessDirectory                         : C:\DAGFileShareWitnesses\EXCH2019DAG01.testlab.local
    AlternateWitnessServer                   :
    AlternateWitnessDirectory                :
    NetworkCompression                       : InterSubnetOnly
    NetworkEncryption                        : InterSubnetOnly
    ManualDagNetworkConfiguration            : False
    DatacenterActivationMode                 : Off
    StoppedMailboxServers                    : {}
    StartedMailboxServers                    : {}
    DatabaseAvailabilityGroupIpv4Addresses   : {0.0.0.0}
    DatabaseAvailabilityGroupIpAddresses     : {0.0.0.0}
    AllowCrossSiteRpcClientAccess            : False
    ActivityState                            :
    FileSystem                               : NTFS
    OperationalServers                       :
    PrimaryActiveManager                     :
    ServersInMaintenance                     :
    ServersInDeferredRecovery                :
    ThirdPartyReplication                    : Disabled
    ReplicationPort                          : 64327
    NetworkNames                             : {}
    WitnessShareInUse                        :
    DatabaseAvailabilityGroupConfiguration   :
    AutoDagSchemaVersion                     : 1.0
    AutoDagDatabaseCopiesPerDatabase         : 1
    AutoDagDatabaseCopiesPerVolume           : 1
    AutoDagTotalNumberOfDatabases            : 0
    AutoDagTotalNumberOfServers              : 0
    AutoDagDatabasesRootFolderPath           : C:\ExchangeDatabases
    AutoDagVolumesRootFolderPath             : C:\ExchangeVolumes
    AutoDagAllServersInstalled               : False
    AutoDagAutoReseedEnabled                 : True
    AutoDagDiskReclaimerEnabled              : True
    AutoDagBitlockerEnabled                  : False
    AutoDagFIPSCompliant                     : False
    AutoDagAutoRedistributeEnabled           : True
    AutoDagSIPEnabled                        : False
    ReplayLagManagerEnabled                  : True
    MailboxLoadBalanceSellableStorage        :
    MailboxLoadBalanceRelativeLoadCapacity   :
    MailboxLoadBalanceComputeCapacity        :
    MailboxLoadBalanceOverloadedThreshold    :
    MailboxLoadBalanceUnderloadedThreshold   :
    MailboxLoadBalanceEnabled                :
    SiloName                                 :
    DistributedStoreConfig                   :
    RequestedDistributedStoreConfig          :
    DxStoreWitnessServers                    :
    DistributedStoreMembershipConfig         :
    DistributedStoreMembershipConfigOverride :
    DxStoreSpareServers                      :
    PreferenceMoveFrequency                  : 01:00:00
    MetaCacheDatabaseVolumesPerServer        :
    AdminDisplayName                         :
    ExchangeVersion                          : 0.10 (14.0.100.0)
    DistinguishedName                        : CN=EXCH2019DAG01,CN=Database Availability Groups,CN=Exchange Administrative
                                               Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=TESTLAB,CN=Microsoft
                                               Exchange,CN=Services,CN=Configuration,DC=testlab,DC=local
    Identity                                 : EXCH2019DAG01
    Guid                                     : a42ff120-23c8-4634-a5de-76923e592686
    ObjectCategory                           : testlab.local/Configuration/Schema/ms-Exch-MDB-Availability-Group
    ObjectClass                              : {top, msExchMDBAvailabilityGroup}
    WhenChanged                              : 20/09/2019 15:51:53
    WhenCreated                              : 20/09/2019 15:51:53
    WhenChangedUTC                           : 20/09/2019 14:51:53
    WhenCreatedUTC                           : 20/09/2019 14:51:53
    OrganizationId                           :
    Id                                       : EXCH2019DAG01
    OriginatingServer                        : TESTLABDC01.testlab.local
    IsValid                                  : True
    ObjectState                              : Unchanged

    The only error I can see in the event log so far relating to the adding servers to the DAG operation is as follows>

    AppLogEventID: 4082

    AppLogEventMessage:
    The replication network manager encountered an error while monitoring events. Error: Microsoft.Exchange.Cluster.Shared.ClusterApiException: An error occurred while attempting a cluster operation. Error: Cluster API failed: "OpenCluster(TESTLABEXCH06.testlab.local) failed with 0x6d9. Error: There are no more endpoints available from the endpoint mapper" ---> System.ComponentModel.Win32Exception: There are no more endpoints available from the endpoint mapper
       --- End of inner exception stack trace ---
       at Microsoft.Exchange.Cluster.Replay.NetworkManager.DriveMapRefreshInternal()
       at Microsoft.Exchange.Cluster.Replay.NetworkManager.DriveMapRefresh()
       at Microsoft.Exchange.Cluster.Replay.NetworkManager.TryDriveMapRefresh()

    I've check the firewall service on both servers, both services started.

    It looks like all rules for Failover clustering have been automatically created and enbled in the advanced view of each servers firewall.


    Matt


    • Edited by Matt_Pollock Friday, September 20, 2019 3:27 PM typo
    Friday, September 20, 2019 3:26 PM
  • Update:

    I managed to fix this issue myself by running the following command in EWS:

    Disable-CmdletExtensionAgent "Scripting Agent"

    Folowing on from this, I was able to add the second server into the DAG successfully without errors.

    Not sut sure at this point if I had enabled Scripting Agent a while ago and forgotten about it, but as far as I'm aware the default state for the Scripitng Agent is disabled.

    If anyone can clarify the part the Scripting Agent plays in DAG server additions, and/or it's default status then that may be useful for all of us for future reference.


    Matt

    • Marked as answer by Matt_Pollock Tuesday, September 24, 2019 8:02 AM
    Tuesday, September 24, 2019 8:02 AM
  • Hi Matt,

    It's great that you have solved this issue. "Scripting Agent" should be disabled by default.

    Maybe some processes are executed by Scripting Agent, and leads to the failure of adding DAG members. I found a similar issue here: Error: "The network path was not found" when adding second DAG member

    Thanks for your sharing. More people should pay attention to this "Scripting Agent", if they have issues about adding DAG members as well.

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Wednesday, September 25, 2019 2:01 AM
    Moderator
  • Hi Matt,

    Since the issue about adding DAG members is figured out, here I will provide a brief summary of this post for your information.

    Issue Symptom

    ====================

    Cannot add the second server to an Exchange 2019 DAG, and get the following error "ScriptingAgent: Exception thrown while invoking scriptlet for Validate API: The network path was not found."

    Cause

    ====================

    The CmdletExtensionAgent "Scripting Agent" is enabled. Some processes are executed by it, and this may lead to the failure of adding DAG members. 

    "Scripting Agent" should be disabled by default.

    Solution

    ====================

    Use the following command to disable "Scripting Agent":

    Disable-CmdletExtensionAgent "Scripting Agent"

    Reference Link

    ====================

    Error: "The network path was not found" when adding second DAG member

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Friday, September 27, 2019 5:26 AM
    Moderator