dwink1984
asked on
MSExchangeSA Error
We just installed a new Exchange 2003 server and we keep getting the error MSExchangeSA Event ID:9074 in the event log. Which results in email not working. It is the only exchange server on the network, and we also have a 2003 domain controller.
The server worked fine for the first two days it was online, then today we started having problems. The exchange server also says that it can't communicate with the domain controller. If I reboot the server for a short time email will work, then we start getting these errors. The 2003 domain controller has been online for 3 months and no user has had any trouble logging onto the domain.
The server worked fine for the first two days it was online, then today we started having problems. The exchange server also says that it can't communicate with the domain controller. If I reboot the server for a short time email will work, then we start getting these errors. The 2003 domain controller has been online for 3 months and no user has had any trouble logging onto the domain.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The Q314294 suggests that this error may occur if the "Manage Auditing and Security Log" right (SeSecurityPrivilege) was removed for the Exchange Enterprise Servers domain local group on some or all of the domain controllers.
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q314294
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q314294
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If your Exchange servers are showing DSAccess errors and you see EventID 9074 errors, this refers to a stale GC referral entry in the DNS. E.g., a GC once existed in the DNS but when it was removed from the environment, the DNS never flushed it out completely. Therefore, Exchange servers still get a referral back to this GC.
Though this has been fixed in the DNS if you see any servers depicting this behavior do a “ipconfig /flushdns” on the Exchange box to force it to reload the DNS cache. You might also want to do a “nbtstat –R” to purge and reload the remote cache name table.
For information in this issue, refer to Q300114.
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q300114