Get 0x80040115 error while sending email from Outlook 2003 client

[Sam05]

I have a Windows XP SP2 laptop that is running Outlook 2003. When pressing Send/Receive in Outlook 2003, the error message below is returned: "Task Microsoft Exchange Server reported error (0x80040115): The connection to the Microsoft Exchange Server is unavailable. The connection to the Microsoft Exchange Server is unavailable. Outlook must be online or connected to complete this action? Can anyone tell me that why does Outlook gives out 0x80040115 error message while sending an email? Does any body knows about it? Kindly help me out to resolve the above issue. Any help you can provide would be greatly appreciated.

[Eric B]

Outlook Express Error 0x80040115 occurs when there is a problem with Microsoft Outlook Express. RPC data may be blocked, and Outlook may not start in Windows Server. The Error are often critical system errors caused by corrupt and missing registry data. This error must be fixed immediately to prevent further damage to the Outlook Express, such email lost, can't sends email.

[Glenny]

You can correct the problem by enabling the Use Cached Exchange Mode feature in Outlook. For that you need to follow the below steps mention.

1. First of all you need to Start your Outlook.
2. Then on the Tools menu, you need to click on Account Settings.
3. After that you need to click on the e-mail account that you use, and then you need to click on Change.
4. Afterwards you need to click to select the Use Cached Exchange Mode check box, and then need to click on Next.
5. After that you need to click on Finish.
6. And then need to finally click on Close.

[JonathanD]

The log file will either be in deleted items or sync issues folders within Outlook. When Client occured issue,there is no anything information in event log, OS, Windows Server 2003 R2 std ,there is no install Services packet. For that you need to restart your Microsoft Exchange Server Information Store service. Then you need to run eseutil /d to perform an offline defrag of the database. After that you need to run isinteg on your machine. Initially the restart of the Information Store service seemed to resolve the issue immediately.