quadraspleen
asked on
Exchange store will not start. Multiple log errors. Cannot check integrity or defrag
We have a serious Exchange server down situaation here.
It started when we installed a new AV solution, following the procedure exactly to exclude the correct folders from the Exchange AV monitor. The server has run file for two days, then tonight I get calls from users unable to log into OWA.
I am unable to start the Store. I get the following errors:
Event Log:
The Microsoft Exchange Information Store service terminated with service-specific error 0 (0x0).
Event ID7024
App Log:
Unable to initialize the Microsoft Exchange Information Store service. - Error 0x800703e6.
Event ID 5000
Error 0x800703e6 initializing the Microsoft Exchange Server Internet Conversion Library.
Event ID 1180
I have cheked the AV solution, and the folders we excluded ARE MISSING from the list now, in fact the list is EMPTY! I will take this up with ESET, but in the meantime, I thought I would try running ESEUTIL and ISINTEG to see what state the logs and database are in.
I am unable to run ANY of these commands! Help!
When i try to run ESEUTIL /D i get the following:
Operation terminated with error -550 (JET_errDatabaseDirtyShutd
not shutdown cleanly. Recovery must first be run to properly complete database
operations for the previous shutdown.) after 0.297 seconds.
And then ISINTEG crashes out with access denied messages as is the store was till mounted, which is is obviously not. I have tried to see in ESM if it still thinks the store is mounted, but it says the store is not running.
The database seems to still think it is mounted and is denying access to it and the logfiles. The following error is noted:
eseutil (216) An attempt to open the file "C:\Program Files\Exchsrvr\MDBDATA\e00
I am unable to log into companyweb either, nor can I open any webpages on the server, help!!
What can I do?
It started when we installed a new AV solution, following the procedure exactly to exclude the correct folders from the Exchange AV monitor. The server has run file for two days, then tonight I get calls from users unable to log into OWA.
I am unable to start the Store. I get the following errors:
Event Log:
The Microsoft Exchange Information Store service terminated with service-specific error 0 (0x0).
Event ID7024
App Log:
Unable to initialize the Microsoft Exchange Information Store service. - Error 0x800703e6.
Event ID 5000
Error 0x800703e6 initializing the Microsoft Exchange Server Internet Conversion Library.
Event ID 1180
I have cheked the AV solution, and the folders we excluded ARE MISSING from the list now, in fact the list is EMPTY! I will take this up with ESET, but in the meantime, I thought I would try running ESEUTIL and ISINTEG to see what state the logs and database are in.
I am unable to run ANY of these commands! Help!
When i try to run ESEUTIL /D i get the following:
Operation terminated with error -550 (JET_errDatabaseDirtyShutd
not shutdown cleanly. Recovery must first be run to properly complete database
operations for the previous shutdown.) after 0.297 seconds.
And then ISINTEG crashes out with access denied messages as is the store was till mounted, which is is obviously not. I have tried to see in ESM if it still thinks the store is mounted, but it says the store is not running.
The database seems to still think it is mounted and is denying access to it and the logfiles. The following error is noted:
eseutil (216) An attempt to open the file "C:\Program Files\Exchsrvr\MDBDATA\e00
I am unable to log into companyweb either, nor can I open any webpages on the server, help!!
What can I do?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I wouldn't even start to troubleshoot that sort of problem with you in this type of forum. There are a couple of chancers who lurk in here that might suggest something that would actually cause more problems than it fixes.
With a server down issue, this is a bad choice of site as you are reliant who who is around. I had a last sweep through before going to bed - it is gone midnight here.
Call Microsoft, pay the fee. They may well get you up very quickly because they can see and do things, rather than relying on KB articles and other links that you might get from a site like this.
Simon.
With a server down issue, this is a bad choice of site as you are reliant who who is around. I had a last sweep through before going to bed - it is gone midnight here.
Call Microsoft, pay the fee. They may well get you up very quickly because they can see and do things, rather than relying on KB articles and other links that you might get from a site like this.
Simon.
ASKER
It's gone midnight here, too. I am (was) on a router/firewall install tomorrow. I could have done without it and thought I might be able to get away with some ESEUTIL fix I was unaware of...
I have some unused incidents as part of my partner program..they will be called at 0900!
Thanks again,
jake
I have some unused incidents as part of my partner program..they will be called at 0900!
Thanks again,
jake
ASKER
Well, I thought I'd give you an update, as it is so bizarre.
Last night, before I went to bed, at around 0100. I set all of the Exchange services to manual, and stopped them all, so when I rebooted it, I could see what was going on without Exchange getting in the way; this mnorning, I called MS PSS and set up a case. Whilst waiting for the tech to get back to me, I reneabled the services and rebooted the server.
They all came back up. Store; web browsing the lot. All nice and clean, with no errors in the logs.
WTF?
Last night, before I went to bed, at around 0100. I set all of the Exchange services to manual, and stopped them all, so when I rebooted it, I could see what was going on without Exchange getting in the way; this mnorning, I called MS PSS and set up a case. Whilst waiting for the tech to get back to me, I reneabled the services and rebooted the server.
They all came back up. Store; web browsing the lot. All nice and clean, with no errors in the logs.
WTF?
Very odd.
The only thing I would suggest is rebooting the server again and see what happens. It could be an indication of trouble getting hold of the domain controllers at start up time.
Simon.
The only thing I would suggest is rebooting the server again and see what happens. It could be an indication of trouble getting hold of the domain controllers at start up time.
Simon.
ASKER
It's an SBS server. It is the DC!
It seems to have a few disk and dmio errors dotted around here and there. I can feel a swing migration coming on..
Thanks again
It seems to have a few disk and dmio errors dotted around here and there. I can feel a swing migration coming on..
Thanks again
ASKER