In my case, Exchange is running on a domain controller (I know it's not best practice). I recently added another domain controller on the local subnet (Exchange still running on the first domain controller), and since then Event 8365 has not recurred;
it's been about 3 weeks. Given the prior details in this thread, I don't see why adding the second domain controller should stop Event 8365, so this may just be a coincidence.
Event 8365 from MSExchangeAL - Could not read the Security Descriptor
↧
↧
Event 8365 from MSExchangeAL - Could not read the Security Descriptor
I can confirm, it is not fixed in RU6 either. This is the first time I have seen the error.
↧
Event 8365 from MSExchangeAL - Could not read the Security Descriptor
This issue is not fixed in RU6
↧
Event 8365 from MSExchangeAL - Could not read the Security Descriptor
The URL above refers to a different issue, the issue this thread refers to is not solved even in RU5 - too bad really.
↧
Event 8365 from MSExchangeAL - Could not read the Security Descriptor
Thanks for keeping this issue alive.
↧
↧
Event 8365 from MSExchangeAL - Could not read the Security Descriptor
WILL THIS EVER BE FIXED, now on SP1 and RU4 still the same!!!
↧
Event 8365 from MSExchangeAL - Could not read the Security Descriptor
SBS 2011 has the error (on my system). I have RAM issues because it is running on an underpowered box. Saw the reference to the RAM and wondered.
R, J
↧
Event 8365 from MSExchangeAL - Could not read the Security Descriptor
Exchange 2010 SP1 has not fixed this issue! Pity.
↧
Event 8365 from MSExchangeAL - Could not read the Security Descriptor
Please be advised that I have the exact same issue with Exchange 2010 on Server 2009 R2 (single server single domain), the results are always after MSExchangeIS activity as follows:
Exchange Server GUID per Get-ExchangeServer | fl Guid:
24eb06e9-4a9b-4f14-b5f6-5b9528b8ce65
GUID as per the event 8365 text:
E906EB249B4A144FB5F65B9528B8CE65
this must be a "bug", no losss of funtion perceived!!!
.......but needs fixing.
↧
↧
Event 8365 from MSExchangeAL - Could not read the Security Descriptor
cab you guys try to run setup.com /preparedomain and see how it works
Regards, Mahmoud Magdy Watch Arabic Level 300 Videos about Exchange 2010 here: http://vimeo.com/user3271816 Read pretty advanced Exchange stuff I and other MVPs post here: http://www.enowconsulting.com/ese/blog.asp Or follow my blog: http://busbar.blogspot.com or our corp blog: http://ingazat.wordpress.com and if you Liked my post please mark it as helpful and accept it as an asnwer
Regards, Mahmoud Magdy Watch Arabic Level 300 Videos about Exchange 2010 here: http://vimeo.com/user3271816 Read pretty advanced Exchange stuff I and other MVPs post here: http://www.enowconsulting.com/ese/blog.asp Or follow my blog: http://busbar.blogspot.com or our corp blog: http://ingazat.wordpress.com and if you Liked my post please mark it as helpful and accept it as an asnwer
↧
Event 8365 from MSExchangeAL - Could not read the Security Descriptor
Same problem here.
But I have two servers and the error shows on one only, the other one have no MSExchangeAL evets at all, no errors or informational events.
↧
Event 8365 from MSExchangeAL - Could not read the Security Descriptor
After adding more RAM (and thus a reboot) I had Event 9661 without Event 8365, but after 2 days Event 8365 came back. And i see the same on further freshly installed systems on different hardware. so, i think for now there is no solution.
↧
Event 8365 from MSExchangeAL - Could not read the Security Descriptor
Thanks for pointing out the association of Event 8365 and MSExchangeIS activity. In my case, the last two instances of Event 8365 were followed 1 or 2 seconds later by Event 9661 from MSExchangeIS "The Unsolicited Commercial Email default filter level has been updated. The new value is 4".
My installation is on a 2008R2 DC.
Your previous post mentioned the possibility that Event 8365 is associated with a server running out of RAM. I doubt it - I have seen Event 8365 on a new OS installation on a server with 16GB RAM, with just one logged on user and no applications except for Exchange 2010 running.
I still suspect this is a bug, because the source of Event 8365 is MSExchangeAL, but MSExchangeAL does not appear in a list of services.
↧
↧
Event 8365 from MSExchangeAL - Could not read the Security Descriptor
As I noticed, it occurs every time, but not always after the same IS maintenance task (maintaining the antispam lists or something like this). but if it is a general problem, i am wondering that only a few posts can be found on the internet.
your install is also on a 2008R2 DC?
↧
Event 8365 from MSExchangeAL - Could not read the Security Descriptor
I have not found a way to eliminate this event. Since I have not noticed any lack of functionality, and since it occurs infrequently, I have been ignoring it.
↧
Event 8365 from MSExchangeAL - Could not read the Security Descriptor
Hello! Did you finally find a sollution to this event 8365 from MSExchangeAL? May it be just a server running out of RAM? Rene
↧
Event 8365 from MSExchangeAL - Could not read the Security Descriptor
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.
↧
↧
Event 8365 from MSExchangeAL - Could not read the Security Descriptor
Hello Sejong,
Please read below why this error always coming on Exchange Server and then you can resolve this issue...
This error is usually encountered when the Exchange server is not a member of the Exchange Servers group in the Microsoft Exchange Security Groups in Active Directory or Active Directory replication latency is causing the discrepancy in group membership.
To resolve the above error please go through the below link and try to resolve actually below link is for Exchange 2007 but you can try to resolve it on same Exchange 2010...
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_23002440.html
http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=8.0&EvtID=8365&EvtSrc=MSExchangeAL&LCID=1033
http://forums.msexchange.org/m_1800475415/printable.htm
Kindly go through the above link and let me know the status..
Cheers,
Subhash Tiwari |MCA|MCSE|MCSA|MCDBA|MCTS | Blog-> http://subhashtiwari.spaces.live.com
Please read below why this error always coming on Exchange Server and then you can resolve this issue...
This error is usually encountered when the Exchange server is not a member of the Exchange Servers group in the Microsoft Exchange Security Groups in Active Directory or Active Directory replication latency is causing the discrepancy in group membership.
To resolve the above error please go through the below link and try to resolve actually below link is for Exchange 2007 but you can try to resolve it on same Exchange 2010...
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_23002440.html
http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=8.0&EvtID=8365&EvtSrc=MSExchangeAL&LCID=1033
http://forums.msexchange.org/m_1800475415/printable.htm
Kindly go through the above link and let me know the status..
Cheers,
Subhash Tiwari |MCA|MCSE|MCSA|MCDBA|MCTS | Blog-> http://subhashtiwari.spaces.live.com
↧
Event 8365 from MSExchangeAL - Could not read the Security Descriptor
About 18 hours after installing Exchange Server 2010, one instance of Event ID 8365 from MSExchangeAL appeared in the Application log.
The event text is "Could not read the Security Descriptor from the Exchange Server object with guid={guid}. As a result the Proxy Address Calculation RPC interface will not be available on the local Exchange Server."
MSExchangeAL does not appear in Services UI, or in the list of services generated by the get-service PowerShell command.
I haven't noticed any loss of function. Could the appearance of this event be a bug?
Update 2009-06-25 14:49 UTC -- The guid noted in the event text is a scrambled version of the Exchange Server guid, as color-coded in the example below
Exchange Server GUID per Get-ExchangeServer | fl Guid:
bed7d488-3c0c-4773-b807-3216ebdbbce1
GUID per event text:
88D4D7BE0C3C7347B8073216EBDBBCE1↧
Event 8365 from MSExchangeAL - Could not read the Security Descriptor
It had been stopped after restart Microsoft Exchange System Attendant services.
Hope this will help someone in same shoes here.
Or
Try to wait AD sync and then restart Microsoft Exchange Active Directory Topology services.
It will restart Microsoft Exchange System Attendant services as well.
↧
More Pages to Explore .....
