Exchange 2003 Ops...



Hi all,

Well, I did a dummy... I installed a brand new SBS 2003 Standard server
at a clients office. I also installed Norton AV Corporate 9.0. The system
didn't even make it a week before the AV quarantined the e00.log file and a
couple of pop3 e-mails that had come in Symantec showed they had the Netsky
virus. Another problem, is their is no backup for the machine. The backup
tapes arrived today. <Lucky me> I went into Symantic, excluded the
directories. Then went and shut down the exchange information store and all
other exchange processes, went back to symantec and "Restored" the virus
infected files. Tried restarting exchange. It seemed to start, but I
couldn't connect, so, checked in the System Manager, and the "Mailbox Store
and Public Folder Store" won't start. So, now I have been working with the
eseutil, and have had no luck there. I get this error which I hope someone
can tell me how to get around it:

eseutil /k "c:\program files\exechsrvr\mdbdata\pub1.edb

File: c:\program files\exchsrvr\mdbdata\pub1.STM
ERROR: database was not shutdown cleanly (dirty shutdown)

Operation terminated with error -550 (JET_errDatabaseDirtyShutdown,
Database was
not shutdown cleanly. Recovery must first be run to properly complete
database
operations for the previous shutdown.) after 4.281 seconds.

eseutil /k "c:\program files\exchsrvr\mdbdata\priv1.edb

File: c:\program files\exchsrvr\mdbdata\priv1.STM
ERROR: database was not shutdown cleanly (dirty shutdown)


Operation terminated with error -550 (JET_errDatabaseDirtyShutdown,
Database was
not shutdown cleanly. Recovery must first be run to properly complete
database
operations for the previous shutdown.) after 16.422 seconds.

So, my question is... how do I shut down the database? I've shut down the
information store, and tried running this and get the same errors... What
else is using it?
Whats this "Dirty Shutdown" and how can I cleanly shut it down if I can't
start it? How can I clear this error and get the database working again?

I also ran the utility on the e00.log file and get this back:

C:\Program Files\Exchsrvr\bin>eseutil /k "c:\program
files\exchsrvr\mdbdata\e00.log

Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating CHECKSUM mode...
Log File: c:\program files\exchsrvr\mdbdata\e00.log

Integrity check passed for log file: c:\program
files\exchsrvr\mdbdata\e00.log


Operation completed successfully in 2.0 seconds.

Now, my real question. If I'm not able to "Restore" this exchange server
and get it working again... what steps should I take to say, dump it and
restart it from scratch? I mean, can I delete it and start over. The
server is less than a week old, I still have the users .pst files I could
import their mail again... I don't mean the whole server, just the exchange
portion of it.

I was thinking that if I stopped the services, ran System Manager, and
deleted the 2 items under the first storage group, create the Mailbox store
and the Public Folder store... This is all conjecture... but, if someone out
there has any information... would be nice. :)


Thanks for your time!






.



Relevant Pages

  • Re: Exchange 2003 Private Store Corruption
    ... Information Store First Storage Group: The database page read from ... Online Diagnostic Utility says "Correctable Memory Threshold Exceeded" ... the server back up and running without the faulty memory installed. ...
    (microsoft.public.exchange.admin)
  • RE: Test-MapiConnectivity failure on Exchange 2007 in coexistence
    ... the default store location caused the database store failed to mount. ... built-in Exchange server 2007 Database Troubleshooter and Eseutil tool (/mh ...
    (microsoft.public.exchange.setup)
  • File Fun
    ... Ok, I'm mulling over different techniques to solve a problem, and ... I'm weighing and experimenting with storing data in a MySQL database ... server somewhere, and just store the path to the file in the DB. ...
    (comp.lang.php)
  • Re: force clean database shutdown
    ... I've configured the server to use the dbstart/dbshut scripts, provided by Oracle, to automatically startup/shutdown the database at when starting/shutting down the server. ... I've noticed that the dbshut script will sometime take forever to bring down the db when shutting down the server, it will just hang there ... ... How can I force a clean shutdown for the database when the server needs to be rebooted? ...
    (comp.databases.oracle.server)
  • Re: store will not mount
    ... of the database not being at the same service pack level of the server. ... "TOM WELLS" wrote in message ... >>until the store has been mounted at least once. ...
    (microsoft.public.exchange2000.information.store)