Exchange 2003 An unexpected MAPI error occurred. Error returned was (0x80004005)

After a reboot of Exchange server, error msg An unexpected MAPI error occurred. Error returned was (0x80004005). This started, when Exchange was not receiving email from off site. Internal email worked fine, sending out worked fine. Now all is not working.
LVL 1
rojiruAsked:
Who is Participating?

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

x
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.

Exchange_GeekCommented:
Did you get this as a popup?
Can you open Exchange System Manager?
Can you see the Exchange services started - any one stopped - if started any errors?
Do you see errors / warnings in event viewer - can you post them?
Can you access / view Queues in ESM?

Regards,
Exchange_Geek
0
AmitIT ArchitectCommented:
Can you check this kb
http://support.microsoft.com/kb/867641

Also post the errors you are seeing in app logs after reboot
0
rojiruAuthor Commented:
This msg is in Event Viewer. Exchange Event service starts then stops with the error. All other services for Exchg have started fine. Checked the kb. I am not an Exchg admin, trying to fix an issue, as no one else is around.
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

AmitIT ArchitectCommented:
Normally it is stopped, i don't think any production users are impacted. I say ignore it.
0
Exchange_GeekCommented:
Still unable to understand where are you facing issues, dig around more and you can provide us results

Did you get this as a popup?
Can you open Exchange System Manager?
Can you see the Exchange services started - any one stopped - if started any errors?
Do you see errors / warnings in event viewer - can you post them?
Can you access / view Queues in ESM?

Regards,
Exchange_Geek
0
rojiruAuthor Commented:
Most everything that I have read so far point to the same. In ESM Tools > Monitoring & Status > Status > (server) Properties > Default Microsoft Exchange Services shows Stopped, though none of the services are stopped save ES.

The big problem is that no email is coming into the server. An email sent from a user using external email states

This message was created automatically by the mail system (ecelerity).

A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:

>>> xxxx@xxxxx.com (after RCPT TO): 554 Service unavailable; Client
>>> host [smtp.quartz.synacor.com] blocked by www.dsbl.org;
>>> 205.169.121.111

Thanks!
0
Exchange_GeekCommented:
I've cross verified that your IP 205.169.121.111 OR Host Name quartz.synacor.com isn't on any Blacklisted vendors.

So, can you try to send using your personal account and verify if the emails are going through.

ALSO please check if relevant Exchange services (including Simple mail Transport Protocol) is running.

Regards,
Exchange_Geek
0
Exchange_GeekCommented:
BTW anyone following http://www.dsbl.org/ is stupid - here is what the site states

DSBL is GONE and highly unlikely to return. Please remove it from your mail server configuration.

DSBL was a blocklist specialized in listing open relays and open proxies. To put it simply, DSBL listed IP addresses of computers that could be tricked into sending spam by anybody. This was a very successful strategy. Nowadays open relays and open proxies are rare, spammers hardly ever use them any more and no software seems to come with an open-by-default policy any more.

Regards,
Exchange_Geek
0

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
rojiruAuthor Commented:
Well, I do believe that it is fixed. The barracuda was set to use dsbl.org. I deleted it from the list, and it seems to be working. Will monitor for awhile to verify. The only Exchg services not running are imap, pop, and ES. I am not sure, if any scripts are being run. So ES is not really needed except for this purpose?

Thanks much for the help!
0
Exchange_GeekCommented:
Great, glad to have helped you.

Regards,
Exchange_Geek
0
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
Exchange

From novice to tech pro — start learning today.