SLINK::EcUpdate Error: 0x8004010f

Event Source: MSExchangeIS Mailbox
Type: Warning
Category: General
Event ID: 1025

An error occurred on database "First Storage Group\Mailbox Store".
 Function name or description of problem: SLINK::EcUpdate
Error: 0x8004010f

The above error popped up once this morning on my Exchange 2K Server, didn't notice it at all until the end of the day. I took a look at the MS KB on the issue and did the following:

1) Ran an eseutil /g which reported NO curruption
2) Ran the offline defrag anyway to recreate the db
3) Ran some diags on my HD's to check for any I/O problems, no issues here
4) Ran a Full backup of the information store

Question is, if my database wasn't currupt and the eseutil /g came up clean, why did I get this message? Also, if curruption DID come up, the MS instructions say to simply run the defrag. Does running the defrag actually repair the database? I thought you had to use the repair switch to do that.

Thanks.
LVL 4
jschwegAsked:
Who is Participating?
 
marc_nivensCommented:
Question 1:

There are different types of corruption in Exchange.  Running an eseutil /g will only show corruption at the Jet level (page damage, checksum errors, etc...).  The error you are seeing is most likely an indication of logical corruption (missing pointers and such).  You need to use isinteg to clear up logical corruption.  However, if its only happened once its probably not worth the down time.

Question 2:

While a defrag doesn't do a repair in the eseutil /p sense of the term, it will give you a new database file.  What could be percieved as corruption can sometimes be fixed by simply running a defrag.
0
 
munichpostmanCommented:
I suspect that the corruption may have been a soft one, which means that no data was damaged and it was probably resolved during store maintenance. You have followed all of the correct troubleshooting steps and should not be worried.

Such quirks in Exchange do happen from time to time.
0
 
jschwegAuthor Commented:
Thanks. I may run the isinteg anyway just to see if it comes up with anything interesting. If it reports problems, it is relativley safe to run isinteg in fix mode to repair the problems?
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
marc_nivensCommented:
Actually, I never run isinteg in read only mode.  If you're going to take the time to run it, you may as well run it in fix mode.  I have yet to see (after literally thousands of times) isinteg cause problems.
0
 
jschwegAuthor Commented:
Rockin. Thanks.

Judging by your answer, I'm guessing it takes signifigantly longer than an eseutil /g?
0
 
marc_nivensCommented:
It should take longer than the /g, yes.  How long really depends on several things such as DB size, amount of corruption, and hardware specifications.
0
 
basheera04Commented:
thanks for support
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.