tgrizzel
asked on
MSExchangeSA Event ID:9186 Microsoft Exchange System attendant thinks that the server is not listed in the Exchange security group
Here is the error that I am getting about once an hour at this point:
Event ID:9186
Microsoft Exchange System Attendant has detected that the local computer is not a member of group /dc=local/dc=mydomain/ou=
We have always got this error about once a day, however recently is now showing almost once per our. I am also getting this error of MSExchangeSA Event ID: 9385 where it looks like the Exchange server is having issues at times contacting our GC. -I dont think this is related though, as this error just recently and we seem to be having a few networking issues on the server that it is pointing to here.
As far as the Event ID: 9186, we have never moved this server to a different OU, we have restarted the System Attendant services, restarted the server, removed the server from the group and re-added it, etc. and this still keeps coming back.
Any thoughts?
Event ID:9186
Microsoft Exchange System Attendant has detected that the local computer is not a member of group /dc=local/dc=mydomain/ou=
We have always got this error about once a day, however recently is now showing almost once per our. I am also getting this error of MSExchangeSA Event ID: 9385 where it looks like the Exchange server is having issues at times contacting our GC. -I dont think this is related though, as this error just recently and we seem to be having a few networking issues on the server that it is pointing to here.
As far as the Event ID: 9186, we have never moved this server to a different OU, we have restarted the System Attendant services, restarted the server, removed the server from the group and re-added it, etc. and this still keeps coming back.
Any thoughts?
ASKER
"Tags:
microsoft, Exchange 2007, sp1"
and
"As far as the Event ID: 9186, we have never moved this server to a different OU, we have restarted the System Attendant services, restarted the server, removed the server from the group and re-added it, etc. and this still keeps coming back."
Hello
I have the same, on a fresh installation in a new forest / domain.
Let you know if if find it out !
oh yeah.. i've installed Rollup 5 also.
I have the same, on a fresh installation in a new forest / domain.
Let you know if if find it out !
oh yeah.. i've installed Rollup 5 also.
ASKER
Exchange Server 2007
Microsoft Corporation
Version: 08.01.0263.000
I have also recently started getting Event ID: 5719 and Event ID:7
These started after we physically moved our Email server to a new location and pointed it to a new GC server. I think these are unrelated to the original thread here, but it would be interesting to see if you had any of the same errors.
What transport protocol are you using in Sites and Services? -this may have nothing to do with the issue at hand as well, but it would be interesting to compare things such as this... Overall topology?
-Mine is 3 DC's, all are GC's, 2 are in a different site, all should be using IP to communicate. FSMO holder is NOT the GC that Exchange is pointed at, therefore not looking at the PDC as it previously was. All 3 DC's are also DNS servers which is AD integrated.
Do you have any other DNS replication errors or anything? How about any general networking errors on the DC that Exchange is pointed to? -I have this DC's NIC's teamed and have seen some teaming errors recently, however the above mentioned error was happening before any of the moves or other errors.
Microsoft Corporation
Version: 08.01.0263.000
I have also recently started getting Event ID: 5719 and Event ID:7
These started after we physically moved our Email server to a new location and pointed it to a new GC server. I think these are unrelated to the original thread here, but it would be interesting to see if you had any of the same errors.
What transport protocol are you using in Sites and Services? -this may have nothing to do with the issue at hand as well, but it would be interesting to compare things such as this... Overall topology?
-Mine is 3 DC's, all are GC's, 2 are in a different site, all should be using IP to communicate. FSMO holder is NOT the GC that Exchange is pointed at, therefore not looking at the PDC as it previously was. All 3 DC's are also DNS servers which is AD integrated.
Do you have any other DNS replication errors or anything? How about any general networking errors on the DC that Exchange is pointed to? -I have this DC's NIC's teamed and have seen some teaming errors recently, however the above mentioned error was happening before any of the moves or other errors.
ASKER
I have a question for you here:
On Exchange 2007, if you run
Get-OrganizationConfig
is the first line, listed to match your AD?
For example, say our Domain name is "fake.com" and our AD is "ad.fake.com". I am wondering if the issue is that my "name" and "LegacyExchangeDN" are something different than the above all together.
Can you confirm this and let me know? -Can someone else confirm that the Name and LegacyExchangeDN should be the same as the AD, or at least an active OU within my domain?
On Exchange 2007, if you run
Get-OrganizationConfig
is the first line, listed to match your AD?
For example, say our Domain name is "fake.com" and our AD is "ad.fake.com". I am wondering if the issue is that my "name" and "LegacyExchangeDN" are something different than the above all together.
Can you confirm this and let me know? -Can someone else confirm that the Name and LegacyExchangeDN should be the same as the AD, or at least an active OU within my domain?
I will check that wednesday
ASKER CERTIFIED 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.
ASKER
it did the trick for me!
Hi
I checked this morning, but the error was gone
I checked the "member of" attribute, and it seems Ok, as it contains "Exchange Servers" and "Exchaneg Install domain Servers".
Strange.
No one touched the server since last time.
Sounds like it cured itself.
I checked this morning, but the error was gone
I checked the "member of" attribute, and it seems Ok, as it contains "Exchange Servers" and "Exchaneg Install domain Servers".
Strange.
No one touched the server since last time.
Sounds like it cured itself.
ASKER
FYI, it sounds as though you are still looking in ADUC as ADSI will only show 1 attribute in this line... That appears to have been the issue as it was reading the Domain Computers as the "main" attribute rather than the Exchange Server.
Either way, if your not seeing an error that is great... It might be possible that MS System Attendant burped and somehow restarted itself and is now reading the info correct, so you may still want to take a look at this.
Either way, if your not seeing an error that is great... It might be possible that MS System Attendant burped and somehow restarted itself and is now reading the info correct, so you may still want to take a look at this.
If your server is Exchange 2k --->As per Microsoft, the Exchange Domain Servers group is granted special rights throughout Active Directory. For any Exchange 2000 Server computer to work properly, the computer must be a member of the Exchange Domain Servers group. To prevent potential problems, if the system attendant detects that the computer name is not a member of this group, the system attendant adds the computer automatically." see http://support.microsoft.com/?id=271335