• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 348
  • Last Modified:

MY MTAdatabse became corrupted in Exchange Server 5.5 SP4.0.

I replaced most of the DB.... .dat files in /MTADATA with the DB....dat files from the Exchange server 5.5 CD, including the db000001.dat file. Microsoft support KB article said not to replace this file. So, I lost that original file.
When I do a MTACHECK, I get the message "Error in queue-desc-object (ID1) initialization. Database has serious errors.
What should I do to fix the MTA database. The registry entries for MTAdata are all fine.
Thanks for your help.
Could you call me at 973 244 1470.
0
toonsix
Asked:
toonsix
  • 3
  • 2
1 Solution
 
Cptn_TripsCommented:
What version of Exchange 5.5 do you have on CD? You need to the mtacheck.exe from the first Exchange 5.5 CD or Service Pack 1. The versions that come on later versions don't recreate the work que if it's been corrupted. If you're using mtacheck from SP2 or later, rename it and replace it with the one from SP1. Try to run the older version of mtacheck a couple of times, then try to start MTA again.
0
 
toonsixAuthor Commented:
Thanks. I think that the 5.5. CD has no SP yet, since it is dated Dec. 1997. Could I just reinstall Exchange server 5.5? Then I will lose SP4.0 and the roll-up version.

Or, should I copy the metacheck.exe file of the CD to the mtadata folder on my server?
PLease help.
0
 
toonsixAuthor Commented:
I copied the metacheck.exe file of the CD to the mtadata folder on my server, and ran mtacheck. The error "Error in Queue-Desc-Object (ID1) initialization" appeared. What should I do to fix this? This appeared after I replaced the DB00001.dat file. Before the file replacement,  I had only the error "checking queue XAPIWRKQ ID 0100020). Some objects missing from the Boot environment".
0
 
Cptn_TripsCommented:
If that fix was going to work, all you really needed to do was rename your current mtacheck.exe, copy that one into the same directory, run it a couple or three times then try to retsart the MTA service. You would only replace one file, NOT reinstall the whole thing. In re-reading your post though, I don't think this alone would work for you.

You have probably corrupted your queue. If you've already copied over the db000001.dat file, you will have to go to your last backup that has your CURRENT mtadata directory on it. Sometimes there is more than one mtadata directory. Look in the registry to see what the path is if you have more than 1 directory. (HKEY_LOCAL_MACHINE\System\ CurrentControlSet\Services\MSExchangeMTA\Parameters key). How old is your last full backup of the server? At worst, you should only lose messages that were in the queue that had not been delivered yet. If you don't have it on tape, copy db000001.dat through db000026.dat to the mtadata folder. If you have it on tape, copy everything EXCEPT db000001.dat from the CD (db000002.dat through db000026.dat) and restore db000001.dat from tape. THEN, run the mtacheck a couple of times. If it says there are still errors, use the mtacheck.exe from the disk or SP1. The disk will say what service pack it is if it has one.

An important thing to remember is that if you copy those files from CD, they will be READ ONLY. Remove the Read Only attribute from them or it won't work. Also, run the mtacheck more than once. If the files are good, you'll get a message that they are ok and that no errors were detected. If you see the number of errors decreasing, run it more until they stop or it says no errors.
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.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

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