locked
CRM 4.0 Outlook Plugin needs additional ports into CRM? RRS feed

  • Question

  • Hi,

    I have installed CRM 4.0 behind an F5 BigIP.  Single Virtual Server into a Single CRM web server.  BigIP is terminating the https and then passing http/80 into CRM.  This works as expected.

    However, the outlook plugin no longer works.   I say 'no longer' because we just finished pluggin the BigIP in front of CRM.  When CRM was a plain web server it worked.   

    What 'else' does the Outlook plugin need to successfully work?   I have setup IFD and this also works as expected through IE when you come from Internal/External.

    The Outlook plugin cannot connect, and all the CRM buttons inside Outlook are greyed out and disabled. 

    Do I also need to pass through NTLM through the BigIP via a virtual server.  How do I turn on loggin on the Plugin to determine what actually failing?

    I was under the assumption if the NTLM failed, it would try 'External CRM URL' using simple authentication.  But although they can still login via IE, the Outlook plug in is still disabled.

    Any tips?

    Thanks
    Tuesday, September 1, 2009 4:03 AM

Answers

  • Hi,

    please install Fiddler http://www.fiddler2.com/fiddler2/version.asp on the client, from which you try to connect to the crm system. When you start fiddler, it acts as a transparent http(s) proxy. Enable the HTTPS capturing in Tools -> Fiddler Options -> Tab HTTPS.

    You should see calls for the file CrmDiscoveryService.asmx on your crm server. Mark one of this calls and select 'Inspectors' on the right side of fiddler. The upper part shows the information about the request which was send to your crm server, the lower part the response. In the response, select 'XML'. There you should see the SOAP-Response of the CrmDiscoveryService, which contains the urls which are provided to the client
    Friday, September 4, 2009 6:32 AM

All replies

  • Hi,

    where do you have placed the BigIP? Is it used for internal request, only for external request (from internet) or everytime? Is there any useful error message or just 'could not connect...'

    You can use fiddler, for examination of the HTTP-requests which are sent by the outlook client. There you can see which urls are accessed and if there are some errors returned.
    Tuesday, September 1, 2009 6:51 AM
  • The BigIP is hosting all content, internal or external.   There's no return routing problems or anything else.

    All aspects of MS CRM 4.0 works in IE, and it's working with the BigIP doing SSL termination.

    What I want to know is, what else is the plugin trying to do?  It's *not* just communicating over https because https works without a problem in IE.  It's obviouslt trying to hit an additional port into CRM which doesn't work.
    Tuesday, September 1, 2009 7:53 AM
  • See http://msdn.microsoft.com/en-us/library/dd979226.aspx for a list of required ports. 

    The outlook client makes use of the crm discovery service for configuration. The discovery service returns the web service address for the requested organisation, which is used by the client to access it. Are you sure it returns the correct address?

    Tuesday, September 1, 2009 8:29 AM
  • >> Are you sure it returns the correct address?

    How do I check this?  Do I need any other ports open?

    From the list of ports you have linked, I literally only have HTTPS allowed through. (think of the BigIP as just a firewall that only allows https through)
    Friday, September 4, 2009 3:17 AM
  • Hi,

    please install Fiddler http://www.fiddler2.com/fiddler2/version.asp on the client, from which you try to connect to the crm system. When you start fiddler, it acts as a transparent http(s) proxy. Enable the HTTPS capturing in Tools -> Fiddler Options -> Tab HTTPS.

    You should see calls for the file CrmDiscoveryService.asmx on your crm server. Mark one of this calls and select 'Inspectors' on the right side of fiddler. The upper part shows the information about the request which was send to your crm server, the lower part the response. In the response, select 'XML'. There you should see the SOAP-Response of the CrmDiscoveryService, which contains the urls which are provided to the client
    Friday, September 4, 2009 6:32 AM