infradatel
asked on
SBS 2011 Exchange Error - Could not read the Security Descriptor from the Exchange Server object with
Hello we have an SBS 2011 server that was migrated frm an SBS 2003 server. W are getting the following error in the event logs.
Could not read the Security Descriptor from the Exchange Server object with guid=5A311F2B1FD87F4B9324F D51AB0ABE1 B. As a result the Proxy Address Calculation RPC interface will not be available on the local Exchange Server.
Any ideas?
I can confirm the following the SBS server is defintely a member of the Exchange Servers group. And when I run Get-ExchangeServer |fl name,guid the guid is not the same as what appears in the error above.
Could not read the Security Descriptor from the Exchange Server object with guid=5A311F2B1FD87F4B9324F
Any ideas?
I can confirm the following the SBS server is defintely a member of the Exchange Servers group. And when I run Get-ExchangeServer |fl name,guid the guid is not the same as what appears in the error above.
ASKER
THanks for the response I thought it might be something like that, however I am also seeing some other worrying alerts in the event viewer
Process MSEXCHANGEADTOPOLOGYSERVIC E.EXE (PID=1800). No Domain Controller server is up in the local site sitename. Exchange Active Directory Provider will use the following out of site Domain Controller servers:
DC name in another site
Process MSEXCHANGEADTOPOLOGYSERVIC E.EXE (PID=1800). No Domain Controller server is up in the local site sitename. Exchange Active Directory Provider will use the following out of site Domain Controller servers:
DC name in another site
Do you think these are related?
Process MSEXCHANGEADTOPOLOGYSERVIC
DC name in another site
Process MSEXCHANGEADTOPOLOGYSERVIC
DC name in another site
Do you think these are related?
Possibly. It also sounds like perhaps your sites and their IP ranges are incorrectly defined in "Active Directory Sites and Services" ....but those errors are again, not particularly significant. Exchange is letting you know that it thinks it is contacting a server at another site (which if you pay for WAN links per megabit would be a big deal) so it throws the warning. If the machines are in fact local then the warning is inaccurate, but not an indication of a component failing.
-Cliff
-Cliff
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
IPv6 disabled
Good luck,
-Cliff