Exchange 2003, log files deleted, messages getting stuck in queue

Exchange 2003 server running on Windows Server 2003.

While I was away from the office, there was a problem with disc space on the server and some of the log files from:

C:\WINDOWS\system32\LogFiles\W3SVC1 and C:\WINDOWS\system32\LogFiles\SMTPSVC1

have been deleted (Anything older that September is gone) and I don't really have a backup of the C:\ drive on that box, only the Exchange data.

Since the log files were deleted about once a day the server needs a restart otherwise we can't send/receive mail. When i go into System Manager and look in the Queues, there are just loads of messages stuck in there and the state is 'retry' but the queues never go down until the server is restarted, then it seems to work fine again for a few hours to a day until it happens again.

I'm assuming the 2 things have to be related and reading up on those log files they obviously shouldn't have been deleted. Is there anything I can do to get the server running properly again without the old log files?



EDIT: Couple of things from the event log:

Unexpected error <<0xc1050000 - Unknown Error. The logon to the Microsoft Exchange Server computer failed. Microsoft Exchange Server Information Store ID no: 80040111-03ee-80040111>> occurred.

AND:

The MAPI call 'OpenMsgStore' failed with the following error:
The attempt to log on to the Microsoft Exchange Server computer has failed.
The MAPI provider failed.
Microsoft Exchange Server Information Store
ID no: 8004011d-0512-00000000

AND:

Unexpected Exchange mailbox Server error: Server: [ukmx1.stottgroup.local] User: [******@******.com] HTTP status code: [503]. Verify that the Exchange mailbox Server is working correctly.
mce-man-itAsked:
Who is Participating?
 
mce-man-itConnect With a Mentor Author Commented:
Well problem solved - was the size of the database

Guess a move to Exchange 2007 is in order
0
 
ChrisCommented:
you will need to take the server offline for a while to sort out the logs, never good if they have been manually deleted.

you can use these two good guide to have a look through and see what state your DB is and how much work you need to do to recover it
http://www.msexchange.org/tutorials/exchange-isinteg-eseutil.html

http://technet.microsoft.com/en-us/library/aa998074%28EXCHG.65%29.aspx
0
 
mce-man-itAuthor Commented:
I figured that was the case but eseutil doesn't seem to have a switch to specifically fix log file issues...

What do I actually need to run here?
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
ChrisCommented:
firstly run this one ESEUTIL /G which will tell you what state the DB is in

then use that to figure out what to do next - post it up and i am sure me and some others will be able to help
0
 
mce-man-itAuthor Commented:
Ok thanks - any idea how long roughly that may take (the DB is about 90gb I think)

Wondering whether I can run it while people are out for lunch or if I should wait til tonight to take it offline
0
 
mce-man-itAuthor Commented:
Just been on to Microsoft and they will not help, just because Exchange is running on VMWare, even though the problem is clearly the issue with missing log files and nothing to do with VM.

I'm going to run ESEUTIL /G tonight after hours, but does anyone have any further ideas in the meantime?

thanks
0
 
ChrisCommented:
are the log files permanently deleted - if you can put them back then it will be easier to do a recovery

on 90GB's it may take a while - dependant on your hardware if you can isolate that host so that there is nothing else on that host and preferably that lun just to make sure its uncontended
0
 
mce-man-itAuthor Commented:
Yeah the C:\ drive isn't backed up, only the Exchange data

Will just have to run it tonight and see how it goes on

thanks
0
 
mce-man-itAuthor Commented:
Wasn't able to bring the database offline last night as one of the foreign offices was working late

Seems to be more stable today for some reason though
0
 
mce-man-itAuthor Commented:
Happened again in the evening - the Queues just get stuck in 'retry' state and have to restart the server to get things going again

Does anyone know any way to stop this happening? Is there anyway to start afresh with the log files or something? Getting desperate now
0
 
mce-man-itAuthor Commented:
Wow ok - I've found a different error message this time... at the exact time it went down:

Exchange store 'First Storage Group\Mailbox Store (UKMX1)': The logical size of this database (the logical size equals the physical size of the .edb file and the .stm file minus the logical free space in each) is 77 GB. This database size has exceeded the size limit of 75 GB.

This database will be dismounted immediately.


0
 
mce-man-itAuthor Commented:
Does this just mean I need to get people to archive/delete mails to bring the size down or is there another step I need to take after this to ensure the database size is under 75gb?
0
 
mce-man-itAuthor Commented:
Also after I've done my archiving is there any way to see the actual size of these files to check they are under 75gb

the sizes now are 62gb + 27gb but obviously that isn't the logical size..
0
 
mce-man-itAuthor Commented:
Found the problem, the size of the database - need to upgrade to Exchange 2007
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.