Error on Outlook 2003 SP3 / Exchange 2010 0x80040115

Hi,

I am receiving the following error on all my computers running XP SP3 & Outlook 2003 SP3.

"Task 'Microsoft Exchange' reported error (0x80040115) : 'The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.' "

This happens only when I click on Send/Receive.

We just migrated from Exchange 2003 SBS to Exchange 2010 (new domain). I guess there is something to configure on the Exchange server to fix this behaviour.

Does anyone has an idea on how to fix this?
David
David_PazosAsked:
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.

Glen KnightCommented:
As you are using Outlook 2003 make sure you offline address book is set to public folder distribution.

Then on the properties of the mailbox database, also make sure you have the default address book selected under client settings.

You might also want to make sure RPC encryption is either enabled at the client level or disabled at the server level.  See here for how: http://support.microsoft.com/kb/2006508

If you used the Exchange 2010 SP1 to do the original install RPC Ebcryption will be off by default.
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
JVFLY23Commented:
Demazter is most likely 100 percent right. OAB is usually the reason for that error.
After you try his solution. If problem persist, you can also try the small things like
 ipconfig/flushdns on the server side.
Also try on one client pc ipconfig/flushdns and restart outlook see if it works.
or the service Microsoft Exchange System Attendant was stopped so you might want to check that.
0
David_PazosAuthor Commented:
Thanks, it worked ))

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