none
Outlook 2010 with Communicator 2007 R2

    Pergunta

  • Hi
    I use Windows 7 Enterprise (x64) with Outlook 2010 (x64) and Communicator 2007 R2 .
    I get Outlook Integration error in Office Communicator and could not update status information.

    "Communicator could not determine the location of your Exchange Web services"

    Any idea?

    Thanks

    Ola Persson, QSi Sweden
    terça-feira, 23 de fevereiro de 2010 21:32

Respostas

Todas as Respostas

  • Hi Ola

    Are we talking about Microsoft Online Services here and that too OCO?

    Moreover make sure you are configuring your OCO and MS Outlook through Single Sign On Client.


    Regards

    Ashish
    quarta-feira, 24 de fevereiro de 2010 05:02
  • Hi Ashish

    Yes I use BPOS and Sign On Client version 1.0.1418.146 and my Sign on Client auto config my Outlook and Communicator.
    I only have one Outlook profile on my computer.

    Yesterday I test with another computer with Office 2007 and everything works well. Are there any problem with Office 2010 and BPOS?

    Thanks

    Ola
    quarta-feira, 24 de fevereiro de 2010 05:58
  • Hi Ola

    I've just went through the details and found out the known integration error between OCO 200 R2 and Outlook x64.

    We're working on it and it will be rectified in next release.


    Regards

    Ashish
    quarta-feira, 24 de fevereiro de 2010 06:26
  • Next release is here and the Integration error is still showing in OC 2007 R2 3.5.6907.83 with Office 2010 RTM, released today!

    Any ideas?

    quinta-feira, 22 de abril de 2010 22:07
  • I still have the integration error on the following setup:

    - Win 7 Pro x64

    - Office Pro Plus 2010 x64 (RTM)

    - Communicator 2007 R2 3.5.6907.83

    The exact error is: "Communicator could not determine the location of your Exchange Web Services".

     

    sexta-feira, 23 de abril de 2010 13:55
  • I also am experiencing this same error in Communicator.

    Office Communicator 2007 R2 (3.5.6907.83)
    Microsoft Office 2010 RTM x64 (14.0.4760.1000)
    Windows 7 x64 Ultimate

    sexta-feira, 23 de abril de 2010 15:21
  • So Do We!

    • Office Communicator 2007 R2 (3.5.6907.196)
    • Microsoft Office 2010 RTM x64 (14.0.4760.1000)
    • Windows 7 x64 Utlimate
    segunda-feira, 26 de abril de 2010 15:23
  • Same error here too:

    • Office Pro Plus 2010 RTM x64 (14.4769.1000)
    • Office Communicator 2007 R2 (3.5.6907.83)
    • Windows 7 x64 Ultimate
    segunda-feira, 26 de abril de 2010 16:19
  • We have the same error too

  • Office Communicator 2007 R2 (3.5.6907.196)
  • Microsoft Office 2010 RTM x64 (14.0.4760.1000)
  • Windows 7 x64 Utlimate
segunda-feira, 26 de abril de 2010 17:34
  • As I understand it, the behavior that you are seeing can occur if if the client cannot get to Exchange Web Services which would be the case with 64-bit. That aside, this functionality is expected to work if you have the latest Cumulative Update installed. Please test using this update, http://support.microsoft.com/kb/978564.
    segunda-feira, 26 de abril de 2010 18:55
  • Hello,

    I actually install this update http://support.microsoft.com/kb/978564. and the problem persists...some ideias??

    Thanks,

     


    Vitor
    segunda-feira, 26 de abril de 2010 19:16
  • Thanks for the feedback Vitor, aplogize it did not work.  The functionality is definitely in that update.  I am asking a peer on the Communicator team to follow up on this and get back to you.
    segunda-feira, 26 de abril de 2010 21:51
  • The most likely cause could be that the Exchange Web services is not configured properly and OC cannot look up that information. Take a look at this posting.

    "Communicator could not determine the location of your Exchange Web Services"

    It may appear if you don't have a correct autodiscovery record created.

    The last (and pretty rare) manifestation of this error can look like this:

    terça-feira, 27 de abril de 2010 03:11
  • Same problem after installing the update.  Everything was working fine with Office 2007, with 2010 x64 not working even after update.
    quarta-feira, 28 de abril de 2010 13:16
  • So is everyone seeing this only with x64 2010 Outlook? What happens if you use x86 version of Outlook 2010? Does it work fine? Would you know what is your Autodiscover URL ? If it works with x86 I am thinking the issue is with Autodiscover URL pointing to the Exhange Web Service(just my guess). FInally are you trying this with Exchange Online or ON-Premise exchange?

     

    quinta-feira, 29 de abril de 2010 21:20
  • I installed the update so now my Communicator version is at 3.5.6907.196.

    Communicator was working fine when I was running 32bit office 2007 (before the removal of 07 and installation of 2010 x64).

    My Autodiscover URL works fine as nobody else is having any problems with integration, just my new Outlook 2010x64 install.

    We are using On-premise exchange.

    segunda-feira, 3 de maio de 2010 15:10
  • Hi Peter

    To confirm ,  you are using Office Communicator Online and your Exchange On-Premise? The reasons others are not seeing is probably they are using x86 bit and that uses MAPI. Since you are using your Exchange on-premise do you have a way of opening an issue with support so they can troubleshoot this? Looks like other folks are using both OCO and Exchange On-line? Can all the users seeing the issue confirm this? For latest update of Office Communicator we fall back to EWS to get OOF and free/busy information. So looks like there is an issue trying to get to the Autodiscover URL.

     

    segunda-feira, 3 de maio de 2010 15:34
  • Thanks.  I will recheck my setups for Autodiscover.
    • Sugerido como Resposta Satam Amit segunda-feira, 4 de junho de 2012 13:16
    segunda-feira, 3 de maio de 2010 15:57
  • Just to clarify, there are several potential issues that re being discussed in this thread and I will try and address them all. Hopefull we can close this thread after this.

     

    What is in the latest released update for OC 2007 R2 for Exchange Connectivity:

    ·         64-bit MAPI is not supported for OC 2007 R2 in any configuration.

    ·         In the event that MAPI is not available (Outlook not installed, or only 64bit MAPI is available) OC 2007 R2 falls back to EWS.

    ·         In order for OC to discover Exchange and EWS,  auto-discovery for Exchange to be enabled via the Exchange auto-discovery URLs.

     

    Connectivity to Exchange Online:

    ·         For customers that are using ExOnline where no auto-discovery is provisioned by BPOS, they should use 32 bit Office instead of 64 bit Office.

    o   BPOS uses local configuration files via the Single-Sign On Service Agent to configure Outlook to connect to ExO. OC relies solely on Exchange auto-discovery which is not configured for ExOnline.

    o   This will allow OC 2007 R2 to leverage 32bit MAPI to access Exchange Online via Outlook’s local configuration file that BPOS SSO/Service Agent drops.

     

    Outlook Integration Error with 64bit Office 2010:

    ·         For customers that are seeing an issue with on-premise Exchange deployments where auto-discovery is setup and enabled as described above , OC 2007 R2 CU4 should be able to connect to Exchange. These customers will still see an Outlook integration error in OC (since we couldn’t integrate with Outlook x64).

    o   For example, free/busy and out-of-office information should still be available in OC via EWS.

    Hope this helps clarify the questions here.

     

    • Sugerido como Resposta Tomasz Skrypij sábado, 25 de dezembro de 2010 06:35
    segunda-feira, 3 de maio de 2010 18:42
  • So, in the EWS-only configuration (64-bit MAPI\Outlook), will conversations be saved in the 'Conversation History' folder? Does that go through the web services or the MAPI interface?
    terça-feira, 4 de maio de 2010 16:15
  • Check this KB out - http://support.microsoft.com/kb/968629 . It has all the details you are looking for and also answers your question about Conversation History.

    -Iyaz

    terça-feira, 4 de maio de 2010 17:00
  • Hi Iyaz,

    I have a customer who wants to use OC online, but Exchange on premise. Nevertheless he want presence from the OL Calendar in OC and conversation history from OC in Outlook.

    Is that a possible scenario, or do we have to migratie the customer towrds Exchange online too.

    regards,

    Niels

    terça-feira, 11 de maio de 2010 12:04
  • I am having hte same issue using the 32-bit version of Office 2010 on Windows 7. I have installed the communicator update and no help. A coworker with the exact same configuration is having the issue as well.
    quarta-feira, 12 de maio de 2010 02:54
  • As long as OC can use the MAPI or EWS to get to the information this should work, but please do check with the OC Online folks for their supportability stance on this.

    -Iyaz

    quarta-feira, 12 de maio de 2010 13:56
  • There is not much information here to go with. Are you using OC Online and Exchange Online or both? What is the configuration? With 32 bit version there has never been any issues reported so far. So I think this is some configuration issue.

    Thanks.

    quarta-feira, 12 de maio de 2010 13:57
  • Iyaz said:

    "Connectivity to Exchange Online:

    For customers that are using ExOnline where no auto-discovery is provisioned by BPOS, they should use 32 bit Office instead of 64 bit Office.

    o   BPOS uses local configuration files via the Single-Sign On Service Agent to configure Outlook to connect to ExO. OC relies solely on Exchange auto-discovery which is not configured for ExOnline.

    o   This will allow OC 2007 R2 to leverage 32bit MAPI to access Exchange Online via Outlook’s local configuration file that BPOS SSO/Service Agent drops."

    I use BPOS, I have Outlook 2010 14.4760.1000 (32-bit) and Office Communicator 2007 R2 3.5.6907.196 installed, but I still get the same integration error message.  My machine had Outlook 2007 and Office Communicator installed and I upgraded to 2010 RTM.

    Is there anything else I should try?


    Don Demsak - MVP Data Platform

    quinta-feira, 13 de maio de 2010 13:28
  • Hi Don

    When the BPOS Service was purchased I assume you also have a way to contact support for the purchased BPOS service right? Have you contacted them?

    Thanks.

    -Iyaz

    quinta-feira, 13 de maio de 2010 17:55
  • I have the same or similar issue; 2007R2,Office2010 64bit.

    My problem is what is stated in kb968629;

    "Any Office Communicator user interface that requires entry point to x64 edition of Outlook does not work in the integration environment. This includes the following:

    • Right-click on Contact properties to see Outlook properties
    • Right-click on Contact to find previous conversations
    • Right-click to schedule a meeting or send an e-mail"

    My questions is - will this be fixed, and if so, when? CU5?

     

    Cheers,
    Per

    segunda-feira, 17 de maio de 2010 09:17
  • 64-bit MAPI is not supported for OC 2007 R2 in any configuration and there is not a plan for this for future CUs.

    segunda-feira, 17 de maio de 2010 13:59
  • We are having the same issue, has anyone found a fix?

    I have only 4 users switched to Exchange On-Line, the rest or still On-Prem.  Of the 4 users, only 1 is able to have others (by others I mean other 3 on Exchange On-Line) see his calendar information thru Communicator.  He's running Outlook 2007 x32, Windows 7 Enterprise x32, and Office Communicator 2007 R2.

    The users who can't have others see their calendar availability thru Communicator, 2 users have Outlook 2010 x64 installed, on Windows 7 Enterprise, and the last user is running Windows Vista x64, with Outlook 2003 SP3.  These 3 users all receive this error in Office Communicator

    "Communicator could not determine the location of your Exchange Web Services

    Your Outlook calendar information and Out of Office message may not be available and your calls may not be forwarded based on working hours.

    Communicator will try to retrieve this information again later. If this problem persists, contact your system admin"

    We thought for a moment that our ISA firewall was blocking some of the traffic but we are all at the same location, behind the same firewall, and have the same rules applied.  I did try applying the hotfix released in April, but that didn't resolve the issue.

    I also receive an error every time I "reconfigure" the applications using the Single Sign On application, when I start the Communicator it says that there is no default mail client.

    Just throwing all the information I can out there, seems like there is no fix available at this time.

    quarta-feira, 23 de junho de 2010 12:39
  • Yes. We finally fixed it on our side. The trick was to change the user name context when the integration prompt was displayed from OCS. The account name in the user field was the email address. To correct, we click on "Other user" and type in the domain name "Domain\accountname" and then it authenticates fine. For some reason, our ISA server will accept the domain name ID authentication method, but not the account in email address form. 

     

    I hope that helps.

    quarta-feira, 23 de junho de 2010 23:55
  • What I don't understand is that even though MOC is a frequently used IM for many companies and used to integrate with Outlook there is still no MOC 2010 at the horizon. Since 64-bit MAPI is not supported why isn't there a MOC 2010? Can we expect something during 2010?


    Bis dat, qui cito dat
    sexta-feira, 2 de julho de 2010 10:12
  • This issue is now documented in this KB article, http://support.microsoft.com/default.aspx?scid=kb;en-US;2028836.  If you need to use the Communicator integration with Office 2010 against BPOS then the client needs to run Office 2010 32-Bit.  The 64-Bit client will not enable all of the features.
    sexta-feira, 9 de julho de 2010 18:05
  • Can I get some clarification?  I read this entire thread and I'm confused.  We our hosting our own Exchange 2007 SP2 server and OCS 2007 R2 server.  We have 1 user that is running MS Outlook 2010 (64 bit) and MOC 2007 R2.  This user is receiving "Communicator 2007 R2 could not determine the location of your Exchange Web Services."  We have the AutoDiscover service installed and working correctly (I was able to configure the Outlook profile automatically).  We also have EWS installed and work correctly (mail clients accessing mail through this service). 

    When I read this article (http://support.microsoft.com/default.aspx?scid=kb;en-US;2028836), I was under the impression that if I installed the Office Communicator 2007 R2 CU4 update, this would resolve the issue.  I was unable to specifically find that update, so I installed the latest update, Microsoft Office Communicator 2007 R2 Hotfix KB 2291453, (http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=515d6dba-4c6a-48bb-a06a-d99c5742676d).  This took me up to version 3.5.6907.221.  This did not resolve my issue of conversation history not saving in Outlook 2010 (64 bit).

    Can you clarify that the following features are supposed to work with Outlook 2010 (64 bit) and Communicator 2007 R2?

    • Conversation History Integration
    • Search for Personal Outlook Contacts in Office Communicator
    • Search and, in Outlook, Search by using Office Communicator in the integration environment
    • Missed IM and Call Notification

    Thank you,

    DBailey

    terça-feira, 11 de janeiro de 2011 01:24
  • David,

    I need the exact same clarification you do.

    Outlook 2010 x64 and Communicator 2007 R2, Conversation history integration.

    Have you fixed this issue?

    Thanks, Sam

    sexta-feira, 4 de março de 2011 15:22
  • We are having a similar integration issue: outlook 2010 plus, exchange 2003, communicator 2007 r2 v 3.5.6907.0

    Does any patch exists? thanks

    terça-feira, 22 de março de 2011 11:48
  • I have a customer who currently has this issue as well, with 64 bit Windows 7 and Outlook 2010 w/ Communicator 2007 R2.  The usual fixes do not seem to fix it.

    The post that said a fix was coming in the next update was over a year ago (Feb 2010).  Has this already been implemented or are we still waiting?

    quarta-feira, 13 de abril de 2011 14:30
  • It seems Communicator just will not integrate with Outlook 64 bit.  There are no plans to make it work, as Lync is replacing communicator with Office 365.
    sexta-feira, 29 de abril de 2011 17:44
  • Greetings all!

    I'm doing some additional research however in the Service Description for OCO (downloaded here http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=b4dae726-215f-481b-bca2-c525fe9b6e76) I found the following information:

    Microsoft Office Communicator 2007 R2 Support

    Office Communications Online requires the separate purchase and installation of Microsoft® Office Communicator 2007 R2.  Office Communicator 2007 is the enterprise desktop client that enables users to send and receive instant messages, organize and manage a Contact List, and monitor presence information for contacts.

    Office Communicator 2007 R2 requires that client computers run one of the following operating systems:

    ·         Windows® Vista™ (32-bit)

    ·         Microsoft® Windows® XP SP2

    Limit

    Microsoft Online does not support client deployment in a customer organization. Microsoft recommends that organizations work with their IT partner if they need assistance deploying Office Communicator to users.

    Ashish's comment mentioned integration issues with Outlook x64 so I'm not sure if it covered 64bit operating systems.

    Vickie

    segunda-feira, 20 de junho de 2011 22:28
    Moderador
  • HI Sam,

    We are running Outlook 2010 x64 and OCS 2007 R2.  We have the latest updates for the OCS and MOC.

    AutoDiscover and EWS is configured properly and working for Outlook x86.

    We are still encountering this error, if anyone has a fix I'm listening.

    Thanks,

    Dave

    quinta-feira, 11 de agosto de 2011 16:47
  • I'm having this problem as well with 64 bit Office 2010. I got the latest update for Office Communicator 2007 R2 and it didn't solve the problem. I am running OC version 3.5.6907.236 now.
    quarta-feira, 26 de outubro de 2011 13:59
  • When it comes down to it, the ability to not be able to simply save chat history in Communicator is a joke. You'd think MS would have a better product than this after buying Skype. The ridiculous and complex work arounds to get this working properly is absurd.

     

    quarta-feira, 25 de janeiro de 2012 17:17
  • Hi Ola

    Are we talking about Microsoft Online Services here and that too OCO?

    Moreover make sure you are configuring your OCO and MS Outlook through Single Sign On Client.


    Regards

    Ashish

    So this is still unresolved, Ashish? You posted this 2 1/2 yrs ago...

    Is there an update to Office 2010 and/or to Communicator 2007 that resolves this issue?


    quinta-feira, 6 de setembro de 2012 13:56