Link to home
Start Free TrialLog in
Avatar of brian_vt_hokie
brian_vt_hokieFlag for United States of America

asked on

Exchange Information Store Not Starting Automatically

I have restarted our Exchange 2003 server twice the past two days - and each time, the Information Store service fails to start automatically.  It is *set* to start automatically, but it does not some of the time.  Furthermore, when I start it and the System Attendant manually, everything appears to work for most people.  Most of our clients use Exchange native, and they are all able to connect.  Our webmail users work fine.  SMTP works fine.  However, one of our clients is using IMAP - and he has been unable to connect since the first reboot.  Yesterday I attempted to restart the IMAP4 service (which was running).  When I restarted it, it hung up with error code 1053.  I did some research, but wasn't able to find much regarding the IMAP service hanging in 2003.  So again last night I rebooted the server...and again the Information Store failed to start automatically.  The relevant contents of the event log are posted below.  And again, IMAP says it is running...but no IMAP clients can connect.  And this time I tried stopping the IMAP service...it stopped fine.  But when I tried starting it...again it hung with error code 1053.

A.) Do you think these two problems are related?

B.) Any idea what might be causing either of the two?

Thanks in advance...


EVENT LOG AFTER REBOOT

The Microsoft Exchange MTA Stacks service depends on the Microsoft Exchange System Attendant service which failed to start because of the following error:
The operation completed successfully.
The Microsoft Exchange MTA Stacks service depends on the Microsoft Exchange System Attendant service which failed to start because of the following error:
The operation completed successfully.
The Kerberos Key Distribution Center service terminated with the following error:
The local machine must be a Kerberos KDC (domain controller) and it is not.
The Network Load Balancing service failed to start due to the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

An unexpected error is forcing EXPS to close the SMTP connection to "barracuda.mathtechinc.com".  "CEhlo::OnSmtpInCommand" called "HrAppendEhloResponse" which failed with error code 0x80040a01 ( f:\tisp2\transmt\src\smtpsink\exps\sink\ehlo.cpp@147 ).

An unexpected error is forcing EXPS to close the SMTP connection to "unknown".  "CEhlo::HrAppendEhloResponse" called "HrGetVServerInfo" which failed with error code 0x80040a01 ( f:\tisp2\transmt\src\smtpsink\exps\sink\ehlo.cpp@852 ).

Failed to initialize directory access. The error code is in the data portion of this event.
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.
Windows cannot find the machine account, The clocks on the client and server machines are skewed. .

Process INETINFO.EXE (PID=1852). Topology Discovery failed, error 0x80040952.
Avatar of CMaster-11
CMaster-11

I have a question for you:
Do you have SP2 installed on exchange server,also what Antivirus program do you use?
also what is status of of Active directory and DC are they working fine.
before I can answer exactly I need to know the above as the solution may vary from very simple fix to rebuilt for exchange server.
Avatar of brian_vt_hokie

ASKER

-I have not installed SP2 yet.  I am hesitant to do so for a while...any known problems?
-AD is working fine
-this box is not a DC, but all of our DC's are functioning normally, as far as I can tell
-We use Symantec Anti-Virus
You are hesitant to install Exchange 2003 SP2? Any reason why?
It has been out for almost two years, is considered rock solid.
Do you have the same attitude to Windows Updates?
I installed Exchange 2003 SP2 on all of my server days after release.

The server is having problems querying the domain. If it cannot see the domain then Exchange will not start.
Ensure that you do not have any external DNS servers in the network configuration of the server.

Simon.
Sembee...I apologize, I thought we were talking Win2K3 service pack 2.  That I have not installed just yet.  Exchange SP2 is definitely on this box.
ASKER CERTIFIED SOLUTION
Avatar of Sembee
Sembee
Flag of United Kingdom of Great Britain and Northern Ireland image

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
Well,is symantec is installed,what edition is it,Symantec mail security product should be installed,Symantec corporate client can be installed but without enabling Internet E-mail Auto protect scanning,also the predefined exclusion should be in place.
As Simon stated SP2 for Exchange would be highly recomanded to be installed,wait on SP2 for Servers,as I heard and experianced alot of situations that left services crashed or not responding due to W2K3 SP2.

Prviously,as my Network is similar to yours I faced few problems with exchange that looks alike yours,Symantec Mail security (Install version 4.6 and above) was the cause.

Also,it is important that you over look your event viewer on both Exchange server and DCs.

Good luck