Thanks for your reply. I don't think the links you provided can resolve this issue.
1. I verified that my Exchange server is a member of the Exchange Servers group in the Microsoft Exchange Security Groups in Active Directory.
2. In my case, there is only one Domain Controller, so replication is not an issue.
3. Based on the difference between the GUID reported by Get-ExchangeServer | fl Guid and the GUID reported in the event text, I was thinking that the process (MSExchangeAL) that is trying to read the security descriptor on the Exchange Server object can't find the object becauise it not parsing the GUID correctly.
As suggested by the second link you cited, I ran the Exchange Best Practices Analyzer (ExBPA). It found the following issues:
a) Unrecognized Exchange signature.
Explanation: ExBPA is looking for objectVersion =10628, but it finds 12433; this in turn is because the version of ExBPA that ships with Exchange Server 2010 Beta does not update itself. In any case, I don't think Unrecognized Exchange signature is related to Event ID 8365.
b) Microsoft Exchange System Attendant 'textEncodedORAddress' is missing
Note: per http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/c2302cfa-ff9f-4d2a-993f-259bff4b7539 this has no bad effects, can be igored for now, and should be fixed in a ExBPA update. Once again, I don't think this issue is related to Event ID 8365.
1. I verified that my Exchange server is a member of the Exchange Servers group in the Microsoft Exchange Security Groups in Active Directory.
2. In my case, there is only one Domain Controller, so replication is not an issue.
3. Based on the difference between the GUID reported by Get-ExchangeServer | fl Guid and the GUID reported in the event text, I was thinking that the process (MSExchangeAL) that is trying to read the security descriptor on the Exchange Server object can't find the object becauise it not parsing the GUID correctly.
As suggested by the second link you cited, I ran the Exchange Best Practices Analyzer (ExBPA). It found the following issues:
a) Unrecognized Exchange signature.
Explanation: ExBPA is looking for objectVersion =10628, but it finds 12433; this in turn is because the version of ExBPA that ships with Exchange Server 2010 Beta does not update itself. In any case, I don't think Unrecognized Exchange signature is related to Event ID 8365.
b) Microsoft Exchange System Attendant 'textEncodedORAddress' is missing
Note: per http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/c2302cfa-ff9f-4d2a-993f-259bff4b7539 this has no bad effects, can be igored for now, and should be fixed in a ExBPA update. Once again, I don't think this issue is related to Event ID 8365.
