Exchange server shows event id 9186 & 9187 here lately

[reynolwi]

Ok I have been seeing event id 9186 & 9187 here recently.

Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 9187
Date: 8/25/2009
Time: 6:51:45 PM
User: N/A
Computer: TXCS-EXCH
Description:
Microsoft Exchange System Attendant failed to add the local computer as a member of the DS group object 'cn=Exchange Domain Servers,cn=Users,dc=domain,dc=net'.

Please stop all the Microsoft Exchange services, add the local computer into the group manually and restart all the services.


Event Type: Warning
Event Source: MSExchangeSA
Event Category: General
Event ID: 9186
Date: 8/25/2009
Time: 6:51:45 PM
User: N/A
Computer: TXCS-EXCH
Description:
Microsoft Exchange System Attendant has detected that the local computer is not a member of group 'cn=Exchange Domain Servers,cn=Users,dc=rrwds,dc=net'. System Attendant is going to add the local computer into the group.

The current members of the group are 'CN=EXCH-SRV,OU=Member Servers,DC=domain,DC=net; '.


I'm sure everyone knows what these events are. Ive googled it, looked on here, looked thru TechNet but everything Ive done it just seems to repeat itself randomly. Ive followed

http://support.microsoft.com/kb/271335

Ive removed it from the group and re-added it, restarted services, rebooted, danced around the server but those events just come back. The server is in that group its even set as the primary group for that server, but it seems exchange has gone stupid.

Is there anything else I can check? Exchange is still running and I havent seen any other problems come up yet, and BES is still sync'd up with exchange and working.

Wm. Reynolds
Senior VP - Information Technology and Fleet Operations
Texas Public Safety Solutions | PremCOM

- - - - - - - - - - - - -

Network Error:
Hit any user to continue

 

[Zelandakh]

On the properties for each server in active directory, are the primary groups both set to domain computers?

Have you renamed the computer at all?

Is the server still in its original OU?

 

[reynolwi]

The exchange server primary group is set to exchange domain servers and does not have domain computers even listed on the member or list. It was moved into a new OU called member servers last year and never had these event ids popup until just recently.

Ive gone thru all the domain settings in exchange to ensure it wasnt pointing to an old domain controller because within the past 8 months two domain controllers were replaced with new ones running windows server 2008. In fact 2 weeks ago is when I replaced that second domain controller with a windows server 2008 domain controller. Maybe when I replaced the second domain controller and demoted the one it replaced 2 days later shook the active directory up and caused exchange to have a hiccup.

Wm. Reynolds
Senior VP - Information Technology and Fleet Operations
Texas Public Safety Solutions | PremCOM

- - - - - - - - - - - - -

Network Error:
Hit any user to continue

 

[Zelandakh]

Ah, I vaguely recall an issue with 2008 DCs and Exchange 07. Are you running Windows 2008 SP2 and Exchange 2007 SP1 with latest roll up?

Is your domain 2003 native or 2008 native?

 

[reynolwi]

ok domain functional level and forest functional level is still at windows 2003. I never changed it when i replaced and upgraded to windows server 2008 but I will probably go ahead and upgrade the functional level to windows 2008.

The exchange server is still running on a windows 2003 r2 standard server with all the current service packs and rollups and is exchange 2003 with the current service packs and rollups.

The domain controllers are 2 windows 2008 server and 2 windows 2003 r2 server both 2008 and 2003 are standard edition. Exhange is connecting to the 2008 domain controllers since they are both here at the moment in the head office and the 2003 dcs are out at 2 different sites.

Wm. Reynolds
Senior VP - Information Technology and Fleet Operations
Texas Public Safety Solutions | PremCOM

- - - - - - - - - - - - -

Network Error:
Hit any user to continue

 

[Zelandakh]

OK, there's no need to lift the domain functional level. Your setup sounds fine so I am not sure why you are getting these issues.

 

[reynolwi]

Its got me stumped because I can not see where the problem is. Ive checked RUS to see if it was pointing to an old DC, checked DNS, IPs, ADUC, checked the 2 2008 DCs for errors, reset the exchange server services even rebooted the server.

It still responds and none of the users have complained about it not working so Im just thinking maybe with this last 2008 promotion and 2003 demotion it shook up active directory and caused the exchange server to have a hiccup.

Wm. Reynolds
Senior VP - Information Technology and Fleet Operations
Texas Public Safety Solutions | PremCOM

- - - - - - - - - - - - -

Network Error:
Hit any user to continue

 

[Zelandakh]

The users see no issue and the only actual issue is events thrown to the event log. Well, you've had worse days.

 

[mattgg]

Check your Exchange Domain Servers member attribute in adsiedit. I noticed that an incorrect Exchange implementation led to these errors before. Inside adsiedit, the actual cluster nodes / physical servers themselves had to be placed in the member attribute and not the evs's. This kept throwing the listed 9187/9186's. Hope this helps.

 

[Zelandakh]

Even if it doesn't help, that's a really useful piece of information - thanks for sharing.