The consistency check of the snapshot for the Microsoft Exchange transaction log has failed - 0xe000032d

When I run a backup of my Exchange 2007 system I get the following error:

Final error: 0xe000032d - The consistency check of the snapshot for the Microsoft Exchange transaction log has failed.  You should check for possible data corruption in the transaction log that is online.

However it still backs up all of the data it seems. I have tryed the article suggested by Symantec but no difference. I have also tryed an "ISINTEG -S DISRUPTIVEMAIL -FIX -TEST ALLTESTS". All the tests were passed and it didn't help the backup job. I have also done all the symantec and windows updates and tried recreating the job with no luck.

Any ideas im really stuck?

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Hi TriumphLTD,

You can use these utils: isinteg\eseutil

They can check your Exchange database for you. It should solve the issue.

TriumphLTDAuthor Commented:
I did already use the ISINTEG command as I put in my post. I ran "ISINTEG -S DISRUPTIVEMAIL -FIX -TEST ALLTESTS" and it didn't work. What other ISINTEG command or ESEUTIL command do you reccomend. I don;t want to run the ESEUTIL -r as thsi could remove corrupt parts of the database.

LOL! Sorry, didn't realise I put in the ISINTEG command.

I would first run the eseutil -g to check for integrity.
Then eseutil -p to repair if errors were found.
Then eseutil -d to defrag the database.

I would strongly suggest that you take the database offline, make a copy and run these utilities on the copy that you made. If you are happy, override the original with the copy that you changed with the utility.

Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

TriumphLTDAuthor Commented:
Hehe thats OK. I can certainly try this. One point to make though is in the error it says that the consistancy check for the "Transaction Log" failed. Is there a check I can run on the transaction logs becuase as I understand it these are not part of the database. Correct me if im wrong!

No, you're right, but do it anyway.


ESEUTIL /ML xxx (Where xxx is the first 3 characters of the log file's name)

This command will scan all transaction log files and verify that they are all in sequence, that they all match each other, and that none of them are damaged.
TriumphLTDAuthor Commented:
Thanks for this information, I have actually found the fix on another post. The problem was casued by Exchange 2007 rollup 4. Uninstalling this fixed the problem.

Thanks for all your help though.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Storage Software

From novice to tech pro — start learning today.