Announcement

Collapse
No announcement yet.

edgesync delays and forced edge reboot

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • edgesync delays and forced edge reboot

    Hello,

    my deployment consists in a single exchange cas/hub/mailbox and a dmz edge server, on a two DCs/GCs AD domain with 400 users and about 350 computers.

    when I create a new mailbox, I think by design the user isn't replicated immediately to the edge, so I force an edge synchronization to the dmz edge. The task exits as OK, and so the test-edgesync, unfortunately mail for that mailbox still generates NDRs with a 5.1.1 User unknown even 30 minutes AFTER the forced edge-sync.

    what fixes the problem so far is an edge reboot. both exchanges servers are fully updated with latest rollups.

    thank you

  • #2
    Re: edgesync delays and forced edge reboot

    Left the below in but now read yout post properly.

    You could perhaps try importing and exporting the subscription file again after checking the first pararaph of my recommendation.

    Also, have you tried using the -VerifyRecipient [email protected] parameter for Test-EdgeSynchronization


    I know that you need to export an edge subscription file on the Edge server and then import it in to the Hub transport server for synchronisation.

    It will be worth checking the Edge subscriptions listed at the following.

    Exchange Managment Console, Organisation Configuration, Hub Transport, Edge Subscriptions tab.

    Type the following in to the Exchange powershell.

    Test-EdgeSynchronization

    You can force a sync, by using this.

    start-edgesynchronization
    Last edited by Virtual; 14th February 2009, 10:29.

    Comment


    • #3
      Re: edgesync delays and forced edge reboot

      I was going to flame your reply

      I already tried to remove the subscription and recreate it, but still no joy.
      By your reply I suppose 30 minutes are way too many to allow replication?

      Comment


      • #4
        Re: edgesync delays and forced edge reboot

        Originally posted by Virtual View Post
        Also, have you tried using the -VerifyRecipient [email protected] parameter for Test-EdgeSynchronization
        nice one, didn't know of that option. will try asap

        thanks

        Comment


        • #5
          Re: edgesync delays and forced edge reboot

          error is still:

          Code:
          Technical details of permanent failure:
          Google tried to deliver your message, but it was rejected by the recipient domain.
          We recommend contacting the other email provider for further information about the cause of this error. 
          The error that the other server returned was: 
          550 550 5.1.1 User unknown (state 14).
          Test-EdgeSynchronization -VerifyRecipient recipient

          Code:
          Name                        : edge
          LeaseHolder                 : EXCHANGE
          LeaseType                   : Option
          ConnectionResult            : Succeeded
          FailureDetail               :
          LeaseExpiry                 : 17/02/2009 12.18.41
          LastSynchronized            : 17/02/2009 11.18.41
          CredentialStatus            : Skipped
          TransportServerStatus       : Skipped
          TransportConfigStatus       : Skipped
          AcceptedDomainStatus        : Skipped
          SendConnectorStatus         : Skipped
          MessageClassificationStatus : Skipped
          RecipientStatus             : NotSynchronized
          CredentialRecords           : Number of credentials 3
          this was the output BEFORE start-edgesynchronization.

          then I issued a start-edgesynchronization:

          Code:
          Result         : Success
          Type           : Configuration
          FailureDetails :
          StartUTC       : 17/02/2009 10.48.10
          EndUTC         : 17/02/2009 10.48.11
          Added          : 0
          Deleted        : 0
          Updated        : 0
          Scanned        : 354
          TargetScanned  : 0
          
          Result         : Success
          Type           : Recipients
          FailureDetails :
          StartUTC       : 17/02/2009 10.48.10
          EndUTC         : 17/02/2009 10.48.11
          Added          : 1
          Deleted        : 0
          Updated        : 0
          Scanned        : 107
          TargetScanned  : 0

          then again Test-EdgeSynchronization -VerifyRecipient [email protected]

          Code:
          Name                        : edge
          LeaseHolder                 : EXCHANGE
          LeaseType                   : Option
          ConnectionResult            : Succeeded
          FailureDetail               :
          LeaseExpiry                 : 17/02/2009 12.48.11
          LastSynchronized            : 17/02/2009 11.48.11
          CredentialStatus            : Skipped
          TransportServerStatus       : Skipped
          TransportConfigStatus       : Skipped
          AcceptedDomainStatus        : Skipped
          SendConnectorStatus         : Skipped
          MessageClassificationStatus : Skipped
          RecipientStatus             : Synchronized
          CredentialRecords           : Number of credentials 3
          this time RecipientStatus is Synchronized, but still 5.1.1 User unknown on mail flowing thru the edge.

          anything else I could try?

          thanks

          Comment

          Working...
          X