Announcement

Collapse
No announcement yet.

EdgeSync errors: Invalid Credentials

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

  • EdgeSync errors: Invalid Credentials

    Hello,

    I have one machine (64bit) that holds the following roles: Mailbox, Client Access, Hub Transport and Unified Messaging [it also is a domain controller] and a second machine (32bit) where I have ISA Server 2006 installed and the EdgeTransport role.
    I have done the preliminary steps before creating an edge subscription (install ADAM, check DNS Settings, ISA rules for allowing SMTP traffic and also for 50389 and 50636 ports), I create a new Edge Subscription, import it to the Hub Transport; when I run "Start-EdgeSynchronization", I get the following output:

    Result : Success
    Type : Recipients
    Name : CN=isa,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23
    SPDLT),CN=Administrative Groups,CN=EXREM,CN=Microsoft Exchange
    ,CN=Services,CN=Configuration,DC=domain,DC=local
    FailureDetails :
    StartUTC : 6/8/2008 12:15:18 PM
    EndUTC : 6/8/2008 12:15:18 PM
    Added : 0
    Deleted : 0
    Updated : 1
    Scanned : 53
    TargetScanned : 53

    Result : Success
    Type : Configuration
    Name : CN=isa,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23
    SPDLT),CN=Administrative Groups,CN=EXREM,CN=Microsoft Exchange
    ,CN=Services,CN=Configuration,DC=domain,DC=local
    FailureDetails :
    StartUTC : 6/8/2008 12:15:18 PM
    EndUTC : 6/8/2008 12:15:18 PM
    Added : 0
    Deleted : 0
    Updated : 194
    Scanned : 253
    TargetScanned : 253

    At a first glance, everything is working, I am able to send and receive emails.

    After this, I try "Test-EdgeSynchronization"

    Name : isa
    LeaseHolder : DC
    LeaseType : Option
    ConnectionResult : Succeeded
    FailureDetail :
    LeaseExpiry : 6/8/2008 4:15:18 PM
    LastSynchronized : 6/8/2008 3:15:18 PM
    CredentialStatus : NotSynchronized
    TransportServerStatus : Synchronized
    TransportConfigStatus : Synchronized
    AcceptedDomainStatus : Synchronized
    SendConnectorStatus : Synchronized
    MessageClassificationStatus : Synchronized
    RecipientStatus : Synchronized

    and I notice "CredentialStatus: NotSynchronized".

    After some time, when I try "Test-EdgeSynchronization" again, I get:

    Name : isa
    LeaseHolder :
    LeaseType : 0
    ConnectionResult : Failed
    FailureDetail : The supplied credential is invalid.
    LeaseExpiry : 1/1/0001 12:00:00 AM
    LastSynchronized : 1/1/0001 12:00:00 AM
    CredentialStatus : Skipped
    TransportServerStatus : Skipped
    TransportConfigStatus : Skipped
    AcceptedDomainStatus : Skipped
    SendConnectorStatus : Skipped
    MessageClassificationStatus : Skipped
    RecipientStatus : Skipped

    I have tried to delete this subscription and add it again for a few times in the last week (also restarting Exchange related services from both machines), but this beahaviour doesn't change.

    Can you help me?
    Thank you!

  • #2
    Re: EdgeSync errors: Invalid Credentials

    Is anything else using those credentials and locking the account maybe?
    cheers
    Andy

    Please read this before you post:


    Quis custodiet ipsos custodes?

    Comment


    • #3
      Re: EdgeSync errors: Invalid Credentials

      Hii


      Looking at the errors it seems to be a certificate problem since the passwords would be going over them.May be we are not able to decrypt ADAM credentials..Plenty of possibilities/..But before that r we getting any events in the eventvwr..1036/1022/1004 etc?

      My best bet would be to delete all the certificates on both servers and create new self signed ones for both servers.Incase you encounter a certificate that doesnot delete because it’s the “Default Certificate” then get it’s thumbprint and go remove it.After that configure for edge sync again.

      Incase we need to know the exact cause we would need some traces..

      *Need to goto \Exchsrvr\bin\extra.exe..MS troubleshooting agent pops up..update it..restart ur pc.
      *Go thru the welcome screen...select a task,select trace
      *Choose the “Trace Control" option
      * Set the “max trace size" to 400-500
      *click on “set manual trace tags.Under trace type select Fatal,Error,Warning,Info,debug.
      *Under components to trace select edge sync and MSexchange Sync...

      Repeat same steps on Edge server too
      Remove current subscription from command shell
      Now start the traces on both servers..Then try to sync..

      All Exchange debug traces would be in the bin folder for both servers..u may post them here...


      Regards

      Fazal
      Fazal Zaidi
      MCITP-Windows 2008,Exchange 2010,MCTS-Exchange 2007,2010,Lync 2010,MCSE-2000,2003,MCSA-2003,2008,2012,MCP,MCSE -Messaging 2013,ITIL

      Comment


      • #4
        Re: EdgeSync errors: Invalid Credentials

        I have generated an .etl file, what tool can I use to view its contents? Thank you!

        Comment


        • #5
          Re: EdgeSync errors: Invalid Credentials

          I have also raised LogLevel for EdgeSync, and in the "Event Viewer" I see now:
          Rejected credential isa.domain.local at 633491406612968750. Effective date is 633492075345468750. Best effective date found: 0. (Event 1031)
          and

          in Exchange Shell when I issue the command
          "Test-EdgeSynchronization -MonitoringContext:$true | fl" I get the following output:

          ID: 1007
          Type: Error
          Message: Credential objects are out of sync on the following Edge servers: isa., Source: MSExchangeMonitoring EdgeSynchronization.

          Comment


          • #6
            Re: EdgeSync errors: Invalid Credentials

            I have solved the problem. When I ran Get-ExchangeServer, the output showed the same version for my servers, but , in fact, Edge was Exchange SP1 and the other one wasn't.
            I have updated to SP1 and I have applied Update Rollup 2 and now EdgeSync works perfect.

            Comment


            • #7
              Re: EdgeSync errors: Invalid Credentials

              Very interesting. Thanks for letting us know.
              cheers
              Andy

              Please read this before you post:


              Quis custodiet ipsos custodes?

              Comment

              Working...
              X