How do I fix an SMTP server that is returning a metabase key error?

I have MS Exchange 2000 running on Server 2000. This system has been running perfectly for about a year.  Suddenly, yesterday I started getting delay notices.  I checked the queues and noticed that all my sent messages were stuck in queue with a "retry" message. (screen shots attached) I then checked the event log and there were 2 messages from smtpsvc.  1) Virtual Server 2: SMTP server cannot read metabase key MailPickupDir  2) Virtual Server 2: SMTP server cannot read metabase key MailQueueDir (screen shots attached)  These errors are recorded each time I restart smtp so I assume this is part of the problem.
How can I resolve this problem so I can send email from this server again?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

TG TranIT guyCommented:
jbasiliere67Author Commented:
Thanks.  I tried the solutions mentioned in the article and it did resolve the error messages in the event log, but the emails continue to be hung up in queue.
jbasiliere67Author Commented:
When I click on one of the queue's on look at properties at the bottom there is a mesage that there is an internal DNS error caused a failure to find the remote server.  Can this be the issue?  DNS reports it is working.  Again, this system was working fine and then suddenly these problems started without any intervention from me.  


Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

TG TranIT guyCommented:
Check out this article:

You said DNS is working fine - have you checked it using NSLOOKUP?

You can specify which DNS server that Exchange will use (the link above will show you how to configure that).  Please try to specify another DNS server and see if messages still hung

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
TG TranIT guyCommented:
Oh, one more thing - have you reboot the box?  At the very least, have you restarted the IISadmin?  SMTP service?
jbasiliere67Author Commented:
Adding an external DNS server did the trick!  Thanks so much for the help.  Now that I'm up and running again I can try and figure out why this happened.  Thanks again!

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
Email Protocols

From novice to tech pro — start learning today.