Well...apparently one of our DC/GC servers messed all over itself yesterday...I pointed out the error messages I was seeing in the DC's event logs to the server admin responsible...when he tried to log in he couldn't. He rebooted the system (it's a virtual machine, he used virtual tools to force the reboot) and it did not come back up.
We've been having issues with this DC for weeks, and I wasn't always informed! I don't know why it causes the Attendant service to stop working...only thing I can think of is that since all of our monitoring tools think the DC is up...but stops authenticating...Exchange must also think it is "up"...and that's why it doesn't switch to another GC. I have forced our Exchange system to pull data from a "good" (as in real) DC/GC until they figure out what to do with the virtual DC. Oh...and in the middle of this RIM decided to have their issues...and we were really going nuts yesterday afternoon. The attendant service stopped authenticating again yesterday...we restarted it...restarted the BES services...and the system did not start working like it usually does. Little did we know that about the same time we restarted the BES services our system lost contact with the Mother Ship! AUGH!!! Concerning Virtual servers/DC/GC...does anyone have experience with virtual DC's? Is it a bad idea? Good idea? From: Brown, Larry [mailto:[EMAIL PROTECTED] Sent: Monday, February 11, 2008 1:23 PM To: MS-Exchange Admin Issues Subject: RE: Exchange Attendant Service No...we aren't allowed to install it until we test in our lab...and the lab servers are, uh...still on order... From: Andy David [mailto:[EMAIL PROTECTED] Sent: Monday, February 11, 2008 12:56 PM To: MS-Exchange Admin Issues Cc: McCready, Robert Subject: RE: Exchange Attendant Service Running SP1 yet? From: Brown, Larry [mailto:[EMAIL PROTECTED] Sent: Monday, February 11, 2008 12:44 PM To: MS-Exchange Admin Issues Cc: McCready, Robert Subject: Exchange Attendant Service Occasionally we are having to restart the Exchange Attendant Service. The first clue is usually some of our Multifunction Devices lose the ability to scan to email, getting an Unable to Connect to Exchange Server error. Setting up new Mail profiles also stops working. And today about 10% of our Blackberry users lost their ability to send/receive messages. Restarting the Exchange Attendant Service, then rebooting the MFD's and restarting BES services fixed all of our problems. We are using Exchange 2007, with Edge servers, Hub transports and CCR. We restart the Attendant service on the Active node of the CCR servers. The only error messages I'm finding for the last few days are listed below. The errors repeat about every 70 minutes until 8:10 and then stopped...since I restarted the Attendant service around 8:45 this seems to be the relevant issue. Research indicates that the Exchange server has lost the ability to open a SYSVOL file on one of the DC's. However, since I had already fixed the problem by starting the Attendant service I couldn't check this out. I really don't want to wait until the problem comes back to verify that this is the problem. As far as I have been able to determine, no one has done anything with any of our domain controllers today. One DC was rebooted last Wednesday, but the errors didn't start (this time) until Saturday morning. I did find 1925 & 1079 errors in the Directory Service log on one DC...but shouldn't Exchange connect to a different DC if it is having trouble communicating with a particular DC? Can someone give me ideas on what else I should be looking at? Event Type: Error Event Source: Userenv Event Category: None Event ID: 1030 Date: 2/11/2008 Time: 8:10:19 AM User: NT AUTHORITY\SYSTEM Computer: <location>EXCCCR02 Description: Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: Error Event Source: Userenv Event Category: None Event ID: 1058 Date: 2/11/2008 Time: 8:10:19 AM User: NT AUTHORITY\SYSTEM Computer: <location>EXCCCR02 Description: Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=dplinc,DC=com. The file must be present at the location <\\<domainname>.com\sysvol\<domainname>.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (Not enough server storage is available to process this command. ). Group Policy processing aborted. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Larry C. Brown LAN/WAN CS Support Dayton Power & Light (937)-331-4922 ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
