Thousands of .log files in Exchange 2007 Server folder

exchange-2007

I'm a bit of an Exchange admin noob so I don't know if this is normal, but on our Exchange 2007 server under C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\ there are 30,000 1MB .log files. I don't know if those should be there or not, but they keep multiplying like little jackrabbits. I've so far resisted deleting them as I'm sure something would break, but it's come to the point now where our 80GB disk is completely full up and Exchange has stopped receiving messages.

My best guess is that these are transaction logs and would be useful in rebuilding the database should something go awry, but 30GB of transaction logging seems a bit excessive. Is there a way to limit it or is that even a good idea?

And of course did I completely miss the point?

Best Answer

Those logs are transaction files. Do not delete them.

I'm curious here, did you install this Exchange server on your own? Placing the storage group on the same disk volume as your OS, swap file etc is absolutely not the recommended configuration for Exchange server.

You should ASAP add more storage to your server, and place the Exchange storage on it.

Please read the following article: Exchange log disk is full, Prevention and Remedies

Related Solutions

Exchange 2010 says it cannot coexists with 2007, but I don’t have 2007

If you really don't have any Exchange server in your domain, your best bet would be to fire up your trusty ADSIEdit and remove the Exchange Organization object. It should be in Configuration\Services\Microsoft Exchange\OrganizationName. If you remove "Microsoft Exchange" under "Services", all Exchange-related informations should go away.

You should also remove the computer object for the old Exchange 2007 server(s).

If even after this cleanup the installer keeps complaining, try manually running setup /PrepareSchema; this should take care of schema version mismatches, if there is any.

Oh, and it would also be useful to check if your domain controllers are properly replicating; maybe they aren't, and one or more of them still have Exchange-related objects lingering around even if you removed them.

Deleted and Re-Added Exchange User Failure to Send

The legacyExchangeDN may have changed. This is the address that outlook is holding on to in the old emails, as well as the cached address book entries that are autofilled when they try to email the person. You can add the old value which looks like this:

/o=Organisation/ou=Administrative Group/cn= Recipients/cn=Username

back to their account as another x500 address (some of that is shown here):

http://www.simple-talk.com/sysadmin/exchange/exchange-e-mail-addresses-and-the-outlook-address-cache/

You'll have to get the old legacyExchangeDN (x500) address, which I think comes back to you in the bounceback you get when someone replies to the old account. It should say something like "couldn't find "/o=Organisation/ou=Administrative Group/cn= Recipients/cn=Username" ... Just add that to their account. Maybe the new mailbox is in a different group or something so the legacyExchangeDN changed...

Best Answer

Related Solutions

Exchange 2010 says it cannot coexists with 2007, but I don’t have 2007

Deleted and Re-Added Exchange User Failure to Send

Related Topic