Link to home
Start Free TrialLog in
Avatar of infradatel
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=5A311F2B1FD87F4B9324FD51AB0ABE1B. 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.
 
Avatar of Cliff Galiher
Cliff Galiher
Flag of United States of America image

This can occur when an old Exchange server (such as one on an SBS 2003 server) was not properly uninstalled to clean up AD. The result is an orphaned object. The error is a transient one and can be ignored, or if you are daring, you can use ADSIEdit and try to prune the data. There are documented procedures on how to do so on technet, but it isn't for the feint of heart, and it isn't something I'm personally comfortable recommending or trying to assist someone do via EE. But at least this answer will hopefully give you an idea WHY you have the error and what your options are.

Good luck,

-Cliff
Avatar of infradatel
infradatel

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 MSEXCHANGEADTOPOLOGYSERVICE.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 MSEXCHANGEADTOPOLOGYSERVICE.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?
 
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
ASKER CERTIFIED SOLUTION
Avatar of infradatel
infradatel

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
IPv6 disabled