Another option is to use SSL to provide security, this may help reset and correct the problem.
http://www.msexchange.org/
Main Topics
Browse All TopicsI had a bunch of problems with an Active Directory corruption and have since fixed them, but I am having trouble with my exchange server... It accepts mail and users can log into their OWA boxes, but when they click on any newer messages it comes up with the dreaded "HTTP/1.1 500 Internal Server Error" in the message body window. All older messages (before the AD issue) are readable.
I did an eseutil /p on the store and it checked out fine (though it seems that the edb file is smaller than it should be, the stm is about normal).
I also get some error messages in the event viewer:
Event Type: Error
Event Source: MSExchangeSA
Event Category: Monitoring
Event ID: 1005
Date: 11/16/2005
Time: 3:12:53 PM
User: N/A
Computer: GOODSERV
Description:
Unexpected error <<0xc1050000 - The client operation failed. The MAPI call failed. Microsoft Exchange Server Information Store ID no: 80004005-0501-c0090081>> occurred.
and
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10016
Date: 11/16/2005
Time: 3:19:15 PM
User: NT AUTHORITY\NETWORK SERVICE
Computer: GOODSERV
Description:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{0C0A3666-30C9-11D0-8F20-0
to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security permission can be modified using the Component Services administrative tool.
(I looked up that CLSID and I am pretty sure it is MDM (debugger)
Any suggestions?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Another option is to use SSL to provide security, this may help reset and correct the problem.
http://www.msexchange.org/
Are you running any Exchange service packs?
Have you reinstalled Exchange since restoring the AD?
Things to try (in order):
1. Run an Exchange domainprep again.
2. Reinstall Exchange with original CD (you'll get an error about previous service packs and so, just click OK)
3. Reinstall Exchange service pack to the same level.
If that doesn't work, a more drastic step would be:
1. Restore your Exchange IIS metabase to it's orginal state, i.e. no Exchange, ExchWeb folders etc.
2. Exchange domainprep.
3. Reinstall Exchange
4. Reinstall Exchange service packs.
Let me know how it goes.
Cheers!!!
You might want to take a look at the common causes of the 500 Internal Server Error.
http://support.microsoft.c
The mail is being delivered if you can read the subject.
http://support.microsoft.c
Again your problem is permission based. It may be in the store, but since it is happening to the Outlook client itself, then it is a DCOM permission issue. You need to fix your permissions which may mean starting over again with a new server install like eclipse007 mentioned. Backup backup backup.
"I was able to fix the issue when I installed Trend Micro Virus scanner. I recomend that the points get awarded to the expert who knows why this would have fixed it... "
Could have been some sort of virus. I think the virus is called "Symantec". The mail was getting delivered to SMTP, but it wasn't making it to the Inbox, I think there is a transport in there where AV scanning goes on, and Symantec was previously installed.
Really though, I don't know.
I have had lots of problems with symantec on Exchange 2003 escpecially because they like to proxy everything under the sun which often suxors. Trend has always been a steadfast and problem free solution. I recommend that product to everyone. I do like the Antivirus of Symantec, just not their exchange or internet filtering software.
Business Accounts
Answer for Membership
by: eatmeimadanishPosted on 2005-11-16 at 12:51:29ID: 15306623
This sounds like a permission issue. You may need to manually check each individual account and reset all the permissions.