Event ID 1005 - Edge Sync Credential

-

We renewed the Certificate in our Exchange 2016 Edge server and subscribed them to the Exchange 2016 Mailbox Server, then we started noticing the below mentioned event ID's in Edge and Mailbox role servers. 

Event ID: 1005 in Exchange 2016 Edge Server

Could not decrypt EdgeSync credential cn=ESRA.EDGESERVERNAME.HUBSERVERNAME.1,CN=Services,CN=Configuration,CN={XXXXX} using Edge default certificate with thumbprint XXXXXXX, The exception is The parameter is incorrect. Please unsubscribe and resubscribe your Edge Transport server

Event ID: 2018 in Exchange 2016 Mailbox Server

Outbound direct trust authentication failed for certificate CN=New_Cert_Name,O=Org_Name,L=City,C=Country. The target IP address of the Exchange Server that Microsoft Exchange tried to authenticate to is [IP]. Make sure EdgeSync is running properly.

What we validated?

-Ensured the SMTP Service assigned to the certificate is Valid and not Expired

-Validated and Restarted the Active Directory Web Services, Microsoft Exchange Credential Service in Edge server

-Restarted Microsoft Exchange Transport service in Edge and Mailbox role server

What solved our issue?

We re-run the Edge Synchronization with the below cmdlet from Exchange 2016 Mailbox server, which stopped these event ID being re-occurred.

Start-EdgeSynchronization -ForceUpdateCookie -ForceFullSync

What other aspects could be done, if not solved?

Recreate the Edge Subscription by deleting the existing Edge Subscription and create it as a all new Subscription.

Remove-EdgeSubscription -Identity Server_Name 

Comments

Post a Comment

Popular posts from this blog

Fitbit Versa 2 - Data not cleared Sync & try again

-
Image
When your Fitbit Versa 2 with 'Data not cleared sync & try again' -Go to your Fitbit app and remove your Versa 2 device from app. -Go to your phone Settings > Bluetooth > Remove the pairing of the Versa 2 -Then you may re-configure your Versa 2 as a new device and enjoy 💖 -If your Versa 2 is locked and struck with error 'Unlock with your phone' -Go to the below URL for the solution, Fitbit Versa 2 - Unlock with your Phone
Read more

Fitbit Versa 2 - Unlock with your Phone

-
Image
When you Fitbit Versa 2 struck with 'Unlock with your Phone' Unlock via Fitbit App : -Go to the Fitbit App, click 'Today' > Your profile picture > Choose your Versa 2 device -Select 'Device Lock', unlock the device with your pin code Factory / Hard reset Fitbit Versa 2 : Note : All your Versa 2 data will be deleted by this and you have start setting it up from scratch.  -Hold the left button for about 10 seconds, until you see the Fitbit logo -Keep holding the button, until the Fitbit logo disappears  -Release the button for about 2 seconds and start holding the left button again -After 5 to 8 seconds, you will feel a vibration -Then you may try to re-configure your Versa 2 as a new device -There are chances where you get an error 'Data not cleared Sync & try again' -Go to the below URL for the solution, Fitbit Versa 2 - Data not cleared Sync & try again
Read more

Exchange - Mail.que utilizing more space - Exchange Drive - Out of Space

-
Image
The Mail.que database file in Exchange Servers increases drastically after a point of time is an expected behavior, below are the possible reasons for them. Data stored in Mail.que file : Email message live traffic Shadow queue Emails pending for delivery & Submission queue Use the below path to reach the mail.que database file, Note: It is highly advisable to exclude this path from AntiVirus scanning. %ExchangeInstallPath%\TransportRoles\data\Queue Mail.que utilizing high space : Emails in queue due to sudden flooding during peak business hours or unavailability of other Exchange server Increased message expiration time, nethold time. The cmdlets to re-configure these values are in below article Note: The mail.que database file will not shrink, however during the online maintenance WhiteSpace will be accumulated which could be used for future emails  How to re-create Mail.que database file? Re-creating the mail.que database file will not harm your Exchange server...
Read more