Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Microsoft Dynamics CRM 2011 Outlook client configuration problem RRS feed

 > 

  • General discussion

  • Discussion
    Sign in to vote
    0
    Sign in to vote
    I installed Microsoft Dynamics CRM Outlook client.
    When I am configuring this Outlook client through Configuration wizard I am getting following error
    "The specified Microsoft Dynamics CRM server is not available. Make sure that the URL is correct. To test the URL, try opening it in Internet Explorer."

    But I am able to access the same URL in web browser.
    What should I do to conigure MS CRM Outlook client

    Intranet CRM URL: http://192.168.1.4
                                  http://crmserver

    Server Details:
    Windows server 2008
    MS CRM 2011

    Clent Machine details:
    Windows 7 Pro
    Office Outlook 2007
    Microsoft Dynamics CRM for Outlook
    Alexis Jimenez
    Friday, April 15, 2011 12:18 PM

All replies

  • Discussion
    Sign in to vote
    0
    Sign in to vote

    Same problem here..

    No-one?

     

    Wednesday, May 11, 2011 1:05 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote

    I had a similar problem I found the link below as a possible solution and it worked, I just had to change the port number to match.

     

    http://support.microsoft.com/kb/948779

     

    Regards

    Monday, May 16, 2011 9:01 AM
  • Discussion
    Sign in to vote
    0
    Sign in to vote

    This actually worked for you on a CRM 2011 installation?

    Friday, May 20, 2011 8:46 AM
  • Discussion
    Sign in to vote
    0
    Sign in to vote

    This is related to multiple bindings, i solved a case in which the user was using an 80 port in his crm web binding when the user had the 5555 but changed it to 80, worked in url in IE, but oddly outlook didn't like it, it was tryin to connect to the original port but the user had 80 ports in the default website as well, causing conflict, once 5555 was put in the binding for the crm, the test connection succeeded, but the user also had to type in the hostname:5555 from the server originally which was different from what he was using in IE. COnfusing yes.. just leave ports alone in bindings.

     

    IFD can help change it,but the user didnt have ifd so the 5555 but this KB is related to the issue http://support.microsoft.com/kb/2498357

    Wednesday, June 22, 2011 12:09 AM