mta and information store services won't start on front end server

I applied the latest windows patches to our windows infrastructure (domain controllers, exchange front end, bridge heads and Mailbox servers). Our exchange system failed even before any re-boots to apply the updates.  I was able to bring up the Mailbox servers (2) and bridgeheads (2) with a couple of re-boots but two services on the Front End Servers refuse to run. The MTA service and information store.  I need to get these service up. We are a small shop and I don't know much about exchange. I ran the best practices analyzer against the front end 1  and it only gave one critical error: "Paging file larger than physical memory" I changed is virtural memory settings to "system managed size" but this had no affect
wisehymerAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
wisehymerConnect With a Mentor Author Commented:
Turns out our exchange mail is working.  Aparently our system is configured to leave the MTA Stacks and Information Store Services Stopped on bouth Exchange Front End Servers?
0
 
leegclystvaleCommented:
What about event logs? This may help if events are the same http://forums.msexchange.org/m_1800395242/mpage_1/key_/tm.htm#1800395242
0
 
wisehymerAuthor Commented:
Every re-boot of the front end server generates these errors:

An unexpected error has occurred which may casue the MTA to terminate Error: Init Routing API returned error -2147219168. [BASE MAIN BASE1] (16)

A fatal directory error occurred. Change to the maximum logging level for more details.

Error 0x8004010f starting the Microsoft Exhcange Information Store. Failed to load Storage Group data.


0
Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

 
leegclystvaleCommented:
Was this a 2000 exchange box upgarded to 2003?
0
 
wisehymerAuthor Commented:
No, a brand new installation of exchange 2003.
0
 
leegclystvaleCommented:
Have you tried removing the updates?
0
 
wisehymerAuthor Commented:
I thought of that but from what server?  It looks like 13 or 14 updates were installed on 8 servers, 2 each of  DC's, Mailbox, Front Ends, and BridgeHeads. I guess I could start at the FrontEnds since they are the problem? is that what you suggest?
0
 
leegclystvaleConnect With a Mentor Commented:
I'd start there yes. And then any exchange-based servers after that. Then I'd look at DC's and global catalogues.
I know you won't want to hear this but were these updates tested? "I" would certainly be reluctant to run so many updates on servers but that's just me. I got caught once similar to this and had to rebuild, so I perhaps run the gauntlet a bit with updates but they can cause problems half the time!
0
 
wisehymerAuthor Commented:
Looks like I'm getting closer My first unistall (KB950159 Security Update for Exchange Server 2003)  temporaily has  "start"  "FE01" Front End Server. although it shows running from status the services didn't start. On with the next uninstall. I'll re-post if I find the removal that fixes it.
0
 
leegclystvaleCommented:
Cool :o) Be interested to know
0
All Courses

From novice to tech pro — start learning today.