[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now


Office Communicator 2007 R2 prompts an Outlook integration error message

Posted on 2009-04-27
Medium Priority
Last Modified: 2013-11-29
After signing in to office communicator, an exclamation mark appears on the missed notifications folder icon. The error message reads "There was a problem connecting to Microsoft Office Outlook. Your Outlook profile is not configured correctly. Contact your system administrator with this information".

I have tried to install the office2007-kb936864-fullfile-x86-en-us.exe hotfix, and also remove and recreate the profile with no success.

I am running clients in a virtual environment on two separate Windows 2003 servers.
Question by:Sagiv

Expert Comment

ID: 24252194
Do you have Exchange System Manager installed on the boxes that are having the error?  This has been fairly commom issue.  Run the fixmapi.exe on the system, reopen MOC and you should be good to go.  If there is no ESM installed, are you doing any logging on the client?

Expert Comment

ID: 24319750
Mapifix did not work for me however, In my case I had Exchange 5.5 and Exchange 2007 Management Consoles. I did not need Exchange 5.5, upon removalof Exchange 5.5 Console  the error went away.

Expert Comment

ID: 24320614
Makes sense, they do not coexist well.
Good Luck
[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.


Author Comment

ID: 24324230
Thanks for your comments, however it happens on both environments, where the Exchange 2003 console is installed on one of them only. Any other ideas?

Expert Comment

ID: 24327802
On the one box with ESM...uninstall>run fixmapi.exe>reinstall...client should be good.
On the other box try this recent post on the Office Communicator Team Blog, there is great new troublshooting feature in Office Communicator R2.  You can CTRL-right-click on the Communicator R2 icon in the taskbar notification area and select Configuration Information& (just like the similar feature in Microsoft Outlook), to get realtime client configuration information.

The server, port, and mode (TCP or TLS) that the client is currently connected to (Server SIP URI).
The status of the Exchange mailbox integration to get free/busy information (MAPI Information).
Whether the user has valid credentials for the A/V Edge Server (MRAS Server - look at the Status column).
The address used to download the Address Book (GAL Status).
The URL used for the Address Book download (URL Internal From Server).
The URL used to expand Distribution Groups (URL External From Server).
Whether the user is connected to the internal OCS server, or through the Edge (Inside User Status).
Whether the user is connected via TLS or TCP (SIP Server URI - look at the Status column).

There is a copy button, which makes communicating this information with others really easy.

Accepted Solution

TSTechNA earned 1000 total points
ID: 24440176
Fixmapi.exe worked in my case. Thanks, BillCarlin.

Author Closing Comment

ID: 31574951
I was forced to respond

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Welcome to my series of short tips on migrations. Whilst based on Microsoft migrations the same principles can be applied to any type of migration. My first tip Migration Tip #1 – Source Server Health can be found here: http://www.experts-exchang…
Issue: One Windows 2008 R2 64bit server on the network unable to connect to a buffalo Device (Linkstation) with firmware version 1.56. There are a total of four servers on the network this being one of them. Troubleshooting Steps: Connect via h…
Loops Section Overview
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…

873 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question