Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1195
  • Last Modified:

ESE Event ID 459 error on Exchange 2003

I have an Exchange 2003 box running on Server 2003 STD and i am getting this error when i rum backups of my exchange server.

Event Type:      Error
Event Source:      ESE
Event Category:      Logging/Recovery
Event ID:      459
Date:            8/23/2010
Time:            11:48:56 PM
User:            N/A
Computer:      EXCHANGE1
Description:
Information Store (4128) First Storage Group: The file F:\Program Files\Exchsrvr\mdbdata\E0010841.log is missing and could not be backed-up.

For more information, click http://www.microsoft.com/contentredirect.asp.
0
victordr
Asked:
victordr
  • 6
  • 6
1 Solution
 
sunnyc7Commented:
Check this kb which describes the problem, and look at the resolution steps below.
http://support.microsoft.com/kb/935634
0
 
victordrAuthor Commented:
What can cause this to happen?
0
 
sunnyc7Commented:
From the KB

This issue may occur if the following conditions are true:
The backup operation is completed successfully.
The backup operation does not truncate the Exchange Server log files successfully.

My guess is - backup didnt flush logs.
What backup software are you using ?
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
victordrAuthor Commented:
Ca Arcserve
0
 
sunnyc7Commented:
what antivirus software are you running ?
Did you exclude the exchange directories from scanning ?
0
 
victordrAuthor Commented:
Symantec. yes some of them are. This has only been happening the past couple of weeks. Nothing on the server was changed.
0
 
sunnyc7Commented:
exclude the whole exchsrvr\ folder
that will exclude mdbdata / logs etc.

i am in a ABS Club (Anything But Symantec). The number of issues created by Symantec Endpoint Protection far outnumbers the number of issues solved by it.
Most of the time it doesnt even block spam / viruses properly.
0
 
victordrAuthor Commented:
okay. Does this error hurt the exchange server at all?
0
 
sunnyc7Commented:
its missing log files.
All emails in those log may not  be accessible.

When exchange receives emails, it writes it first to log files and then commits it to database.

You can try taking a full backup after shutting off symantec mail scan / AV and see if you get the error after that.
0
 
victordrAuthor Commented:

This is what is excluded from file system auto-protect.

symantec.JPG
0
 
sunnyc7Commented:
Go one level above and exclude the whole folder.
0
 
victordrAuthor Commented:
Ran another backup last night. same error.
0

Featured Post

Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

  • 6
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now