Orderly shut down of exchange 5.5

[Adminman]

Something is causing our exchange server to fail to shut down properly. When you shut down the system for any reason (maintenance, latiency, etc.) the priv.edb and public.edb are inconsistent when the system is brought back on line. (The files are consistent prior to shut down.) I've tried closing the exchange services prior to shutting down the WinNT 4.0 server. IS there a specific order the services should be stopped?? Any ideas?

Thanks,

Exchange Newbie in MD

 

[Zelandakh]

No, it should be fine. There is a more fundamental problem here.

Can you stop all the services and then restart them and have everything ok?

 

[FilthPig]

Is there a specific error you're getting? What do your event logs say? <Generalization> Perhaps a service pack update is in order </Generalization>. Marc Creviere

 

[Adminman]

Zelandakh,
I'll check it out this evening. I have maintenance to do n the system. I'll shut down the exchange services and then check consistency and let you know the results. The last time I did it, I think everything was consistent. I can't recall with any level of certainty.

FilthPig,
The errors I get are on the re-boot. event ID: 7024, source: Service Control Manager, Type: Error, Category: none, Description: The Microsoft Exchange Information Store service terminated with a service specific error 4294966264.
event ID:7001, source: Service Control Manager, Type: Error, Category: none, Description:The Microsoft Exchange Event Service service depends on the Microsoft Exchange Information Store service which failed to start because of the following error: The service has returned a service specific error code. I will post additional info after I do maintenance tonight.

Thanks in advance.

Newbie in MD

 

[FilthPig]

Well according to the MS knowledge base (If you're not familiar with it, you will want to become so, it's at support.microsoft.com ) articles Q177761 and Q245058, that's a file access error. What do you do to get it running again? Do you start the service or do you run it from a command line? If the service is failing mayhaps the account it's using does not have the correct permissions. Maybe for some strange reason the edb files are being marked read-only. Marc Creviere

 

[Adminman]

Filthpig-
To get it runnign again, I have to run eseutil /p on both the pub and priv.edb. Then reboot. I stopped the services manually last evening (via service panel) and tried to restart (via service panel). No dice. The event viewer lists the following error IDs on the restart (the ones I think are important I've included the details) 5000, 100, 108, 109, 158, 0 <-- source: ese97, type: error,category: logging/recovery. 1120 <-- error 0xfffffbf8 intializing the ESInfoStore,5000<--unable to intialize ESInfoStore service.

You stated that the edbs shouldn't be read only. Is that correct? Everytime I've been to the edbs they have been read only...

As far as the permissions for the services they are appropriate. (The exchange admin with correct password).

Dave Firestone

 

[FilthPig]

*Dealing with the frustration of having recently changed jobs and not having an Exchange Server on-site to go look at(yet).*

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q245058

According to this MS Knowledge Base article, it should not be read-only. Might also want to check out this article:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q185577

Marc Creviere

 

[Adminman]

Marc-
Thanks.

Dave