locked
Edge Sync with TMG server returning error. RRS feed

  • Question

  • Hello,

    I have a tmg server on which I have installed and Edge Server.  I used the TMGServer's Email Policy To Enable Dege Sync Traffic and to Generate Edge Subscription Files.  I imported the edge subscription file on my Hub Transport Server.  

    The TMG Server setup both the send and receive connectors. However when I use the Start-EdgeSynchronization commandlet I receive the following output. Any ideas on what I may be doing wrong?

    Thanks

    Bill

     

    [PS] C:\Windows\system32>Start-EdgeSynchronization -ForceFullSync


    RunspaceId     : 448a16e9-472d-4484-8b50-eaeadefe8d79
    Result         : CouldNotConnect
    Type           : Recipients
    Name           : TMGSERVER
    FailureDetails :
    StartUTC       : 10/4/2011 10:51:45 PM
    EndUTC         : 10/4/2011 10:51:45 PM
    Added          : 0
    Deleted        : 0
    Updated        : 0
    Scanned        : 0
    TargetScanned  : 0

    RunspaceId     : 448a16e9-472d-4484-8b50-eaeadefe8d79
    Result         : CouldNotConnect
    Type           : Configuration
    Name           : TMGSERVER
    FailureDetails :
    StartUTC       : 10/4/2011 10:51:45 PM
    EndUTC         : 10/4/2011 10:51:45 PM
    Added          : 0
    Deleted        : 0
    Updated        : 0
    Scanned        : 0
    TargetScanned  : 0

    Tuesday, October 4, 2011 11:04 PM

Answers

  • Hello,

     

    Please do the following tests to see if the necessary ports are opened:

     

    1. Telnet from the hub server to edge on port 25

    2. Then try on port 50636.

    3. Go to edge server and tried telnet localhost 50389

     

    Please let me know the result. If any port is block, please open it and check if the issue persists.

     

     

    Simon Wu

    Exchange Forum Support

     

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, October 6, 2011 9:38 AM
    Moderator

All replies

  • On Tue, 4 Oct 2011 23:04:15 +0000, williamtholmes wrote:
     
    >
    >
    >Hello,
    >
    >I have a tmg server on which I have installed and Edge Server. I used the TMGServer's Email Policy To Enable Dege Sync Traffic and to Generate Edge Subscription Files. I imported the edge subscription file on my Hub Transport Server.
    >
    >The TMG Server setup both the send and receive connectors. However when I use the Start-EdgeSynchronization commandlet I receive the following output. Any ideas on what I may be doing wrong?
     
    Every time I've had a problem with getting things to work this seems
    to get it going.
     
    1. On the Hub, Remove the Subscription
    2. On the Edge, Remove the cert used by ADAM to establish secure
    connections. You can do this by following the following steps:
    a. Open up an empty mmc console (Run -> mmc)
    b. Select File -> Add / Remove Snap-in
    c. Hit Add
    d. Select "Certificates" from the List of Snap-Ins available, and
    hit Add.
    e. Select "Service Account" on the "Certificates Snap-In" page,
    click next.
    f. Select "Local Computer" on the "Select Computer" page, click
    next.
    g. Select "Microsoft Exchange ADAM" from the list of services,
    click Finish.
    h. Close the "Add Snap-in" dialog.
    i. Navigate to "Certifcates – Service" ->
    "ADAM_MSExchange\Personal" -> Certificates
    j. You should see a single certificate here. Remove it.
     
    3. On the Edge, Unsubscribe, then create a new subscription file
    (you should see a new certificate show up at this point on the ADAM
    cert container from the step above) by calling new-edgesubscription
    4. Re-start the "Microsoft Exchange ADAM" service.
    5. Bring the file in and re-subscribe (new-edgesubscription on the
    hub.)
     
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    Wednesday, October 5, 2011 2:58 AM
  • Hello,

     

    Please do the following tests to see if the necessary ports are opened:

     

    1. Telnet from the hub server to edge on port 25

    2. Then try on port 50636.

    3. Go to edge server and tried telnet localhost 50389

     

    Please let me know the result. If any port is block, please open it and check if the issue persists.

     

     

    Simon Wu

    Exchange Forum Support

     

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, October 6, 2011 9:38 AM
    Moderator
  • Hello,

     

    Is there any update on this thread?

     

    Thanks,

    Simon

    Wednesday, October 12, 2011 2:27 AM
    Moderator