Announcement

Collapse
No announcement yet.

Ex2010: Edge Sync / SynStatus Inconclusive?

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

  • Ex2010: Edge Sync / SynStatus Inconclusive?

    This is quite random. I tried to re-subscribe, re-create etc. etc. and I can't see what this is happening. Here on the HubTransport server

    Code:
    [PS] C:\Windows\system32>Start-EdgeSynchronization
    
    
    RunspaceId     : c6286489-790b-44d5-ace5-61a364a5bf6b
    Result         : Success
    Type           : Recipients
    Name           : edge
    FailureDetails :
    StartUTC       : 08/12/2010 01:22:36
    EndUTC         : 08/12/2010 01:22:39
    Added          : 0
    Deleted        : 0
    Updated        : 0
    Scanned        : 0
    TargetScanned  : 0
    
    RunspaceId     : c6286489-790b-44d5-ace5-61a364a5bf6b
    Result         : Success
    Type           : Configuration
    Name           : edge
    FailureDetails :
    StartUTC       : 08/12/2010 01:22:36
    EndUTC         : 08/12/2010 01:22:39
    Added          : 0
    Deleted        : 0
    Updated        : 0
    Scanned        : 0
    TargetScanned  : 0
    Looks good. Now a normal test

    Code:
    [PS] C:\Windows\system32>Test-EdgeSynchronization
    
    
    RunspaceId                  : c6286489-790b-44d5-ace5-61a364a5bf6b
    SyncStatus                  : Normal
    UtcNow                      : 08/12/2010 01:24:46
    Name                        : edge
    LeaseHolder                 : CN=MAIL,CN=Servers,CN=Exchange Admin
    LeaseType                   : Option
    FailureDetail               :
    LeaseExpiryUtc              : 08/12/2010 01:52:39
    LastSynchronizedUtc         : 08/12/2010 01:22:39
    TransportServerStatus       : Skipped
    TransportConfigStatus       : Skipped
    AcceptedDomainStatus        : Skipped
    RemoteDomainStatus          : Skipped
    SendConnectorStatus         : Skipped
    MessageClassificationStatus : Skipped
    RecipientStatus             : Skipped
    CredentialRecords           : Number of credentials 3
    CookieRecords               : Number of cookies 2
    Looks good too. But testing a specific mailbox gives me the 'inconclusive' error

    Code:
    [PS] C:\Windows\system32>Test-EdgeSynchronization -VerifyRecipient [email protected]
    
    RunspaceId                  : c6286489-790b-44d5-ace5-61a364a5bf6b
    SyncStatus                  : Inconclusive
    UtcNow                      : 08/12/2010 01:25:37
    Name                        : edge
    LeaseHolder                 : CN=MAIL,CN=Servers,CN=Exchange Administrative Group 
    LeaseType                   : Option
    FailureDetail               :
    LeaseExpiryUtc              : 08/12/2010 01:52:39
    LastSynchronizedUtc         : 08/12/2010 01:22:39
    TransportServerStatus       : Skipped
    TransportConfigStatus       : Skipped
    AcceptedDomainStatus        : Skipped
    RemoteDomainStatus          : Skipped
    SendConnectorStatus         : Skipped
    MessageClassificationStatus : Skipped
    RecipientStatus             : Synchronized
    CredentialRecords           : Number of credentials 3
    CookieRecords               : Number of cookies 2
    Either the full compare mode is fine

    Code:
    [PS] C:\Windows\system32>Test-EdgeSynchronization -FullCompareMode
    
    
    RunspaceId                  : 4eb04597-f551-47a0-a5c2-865b7cf59dc0
    SyncStatus                  : Normal
    UtcNow                      : 08/12/2010 15:09:18
    Name                        : edge
    LeaseHolder                 : CN=MAIL,CN=Servers,CN=Exchange Administrat
    LeaseType                   : Option
    FailureDetail               :
    LeaseExpiryUtc              : 08/12/2010 15:38:47
    LastSynchronizedUtc         : 08/12/2010 15:08:47
    TransportServerStatus       : Synchronized
    TransportConfigStatus       : Synchronized
    AcceptedDomainStatus        : Synchronized
    RemoteDomainStatus          : Synchronized
    SendConnectorStatus         : Synchronized
    MessageClassificationStatus : Synchronized
    RecipientStatus             : Synchronized
    CredentialRecords           : Number of credentials 3
    CookieRecords               : Number of cookies 2
    The only two hits on google was to either re-subscribe (done that) and also missing product keys (all fully licensed). Even the Eventlog is as clean as you want it to be

    (LeaseHolder lines have been shortened on purpose)

  • #2
    Re: Ex2010: Edge Sync / SynStatus Inconclusive?

    This is driving me mad .. no one ?

    Comment


    • #3
      Re: Ex2010: Edge Sync / SynStatus Inconclusive?

      Do you have a actual problem while this result message is shown or is it just that it makes you mad?

      Since if you don't have a problem I would not spend to much time with this issue.

      Comment


      • #4
        Re: Ex2010: Edge Sync / SynStatus Inconclusive?

        Originally posted by FischFra View Post
        Do you have a actual problem while this result message is shown or is it just that it makes you mad?

        Since if you don't have a problem I would not spend to much time with this issue.
        I can't say whether this is a problem or not. Basically this is the first Exchange 2010 infrastructure I am about to deploy for a customer (last one I did was 5.5).

        For now it is not in production. I want to be 100% certain that the infrastructure is working 100% before putting it into production. Last thing I want is ignoring the errors just to find out that there is an issue weeks down the line ..

        Comment


        • #5
          Re: Ex2010: Edge Sync / SynStatus Inconclusive?

          Having a lot free tickets left with Microshaft I just had them checking it out.

          Apparently this can be ignored as the Edgesync runs every 5 minutes and will always be inconclusive until such time it JUST syncronizes the changes.

          Why it was "normal" on most videos I have seen ? No idea ... Do other people see 'inconclusive' ? No idea .. but the guy from Microshaft did a few tests and all seems fine so I shall accept that.

          Edit: just got an answer from a moderator on the msdn forums and he had the same result ... so I am happy now

          Comment

          Working...
          X