0x80040115 when attempting to Send email from Outlook 2003 client

[Guest]

Hi there,

I have a Windows XP SP2 laptop that is running Outlook 2003. The user of
this laptop is unable to send emails. He receives a message saying:

"Task Microsoft Exchnage Server reported eror (0x80040115): The conection to
the Microsoft Exchange Server is unavailable. Outlook must be online or
conected to complete this action"

Even though the status of Outlook 2003 is "Connected" and the user can
receive emails fine.

I have tried the following troubleshooting:
- Rebooted the computer; the problem still exists
- Opening and closing Outlook; the problem still exists
- Removed his Outlook Profile and Re-created it going through the wizard
again; the problem still exists
- The user can log in to OWA and everything works fine there; the problem
must be something to do with his Outlook program
- No other user connecting to the same Exchange server (Exchange 2003 on SBS
2003 Server) has this issue.

Is there any other troubleshooting tips that someone could suggest?
Thanks in Advance!

 

[Guest]

Does this apply?

support.microsoft.com/default.aspx?scid=kb;en-us;897716

Please let me know.

 

[Guest]

I don't believe this to apply for the following reasons:

1. The client is not running Windows Server 2003 SP1 or a 64 bit version of
Windows XP
2. We do run ISA Server 2004 but it is already up to date with SP3.
3. If it was a problem with our ISA server, then why aren't there more
clients with this issue?

Do you have any other suggestions?

 

[Guest]

A further update on this issue:

I have done some more troubleshooting and what seems to have solved this
issue is running a repair of the office installation. I don't know what has
caused this issue in the first place, but the user is now working fine after
the repair.

If the problem returns, so will I to this forum!

Thanks!
Phil

 

[Guest]

I make a repair on Office 2003, but the problem still exist.
I have the same problem..

 

[Guest]

Ok, well I ended up calling MS for some help on this one. This is what we did
to resolve the issue:

- Restart the Microsoft Exchange Server Information Store service
- Ran eseutil /d to perform an offline defrag of the database
- Ran isinteg

Initially the restart of the Information Store service seemed to resolve the
issue immediately. The other two items were more to make sure no other issues
were going to make the problem return.