locked
"communicator could not determine the location of your exchange web services" integration error with Communicator RRS feed

  • Question

  •  

    I'm getting this message on all Communicator 2007  clients.. i'm not sure what could suddenly be causing this.

     

    We run Exchange 2007 sp1 and it was fine previously.  We do not use ISA or similar.  We are experiencing a free/busy information glitch with appointments in outlook (the free/busy info is unavailable or never connects).. not sure if this is related.

     

    Thanks

    Monday, March 3, 2008 9:34 PM

All replies

  •  

    Noone has any thoughts on this?

     

    Thanks

    Wednesday, March 5, 2008 5:08 PM
  • Hi,

    we had the same problem but after we published the autodiscover record for our exchange 2007 ISA 2006 this warning in our cumminicator disappeard.

     

    regards

    Henrik

     

    Wednesday, March 5, 2008 5:47 PM
  •  HenrikR wrote:

    Hi,

    we had the same problem but after we published the autodiscover record for our exchange 2007 ISA 2006 this warning in our cumminicator disappeard.

     

    regards

    Henrik

     

     

    unfortunately for us nothing has changed, we dont use isa either

    Wednesday, March 5, 2008 5:59 PM
  •  markm75c wrote:
     HenrikR wrote:

    Hi,

    we had the same problem but after we published the autodiscover record for our exchange 2007 ISA 2006 this warning in our cumminicator disappeard.

     

    regards

    Henrik

     

     

    unfortunately for us nothing has changed, we dont use isa either

     

    Oh wait.. i just figured part of this out.. we installed a new firewall router.. now from behind the firewall we cant access external addresses..

     

    so in our case.. autodiscover is set to wan1.domain.com  but.. we cant get to that from inside the firewall (even though it points at our local comcast address which points to our exchange server via the firewall rule)..

     

    I'd need to find a workaround.. once inside addresses can resolve this.. it will work..

    Wednesday, March 5, 2008 6:01 PM


  • it has got something to do with the Autodiscover.

    see the topic below:
    http://forums.microsoft.com/unifiedcommunications/ShowPost.aspx?PostID=3711024&SiteID=57&mode=1

    HTH.
    Wednesday, August 6, 2008 4:38 AM