Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Enabling IFD breaks the Plugin registration tool RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    When I enable Internet facing deployment, I get an error when I run the the plugin registration tool – as yet I have not found a solution online.

    I’m assuming its a DNS lookup vs AD authentication issue but cannot yet see a way around it, have you come accross this issue?

    Many thanks,

    Stuart

    Stuart
    Thursday, July 22, 2010 3:11 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Check this registry key:

    hklm/software/microsoft/mscrm/localsdkport

    This key should be the port number that you are running crm on.  If you changed the port after it was installed there is a chance this is wrong.  If your crm runs on port 5555 then this reg key should be 5555.

    Alex Fagundes - www.PowerObjects.com
    • Marked as answer by Jim Glass Jr Thursday, July 22, 2010 5:37 PM
    Thursday, July 22, 2010 4:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    OK if finally came down to being a config error - the IFD declared IPaddresses and subnet masks 

    I needed to add the www.xxx.yyy.zzz address of the server and a suitable subnet mask - i started with 255.255.255.0 and reduced it down to 255.255.255.255 - i'd left in 1270.0.1 & 255.255.255.255

    So thanks for you answers guys but in the end it came down to allowing the server to talk to itself.

    Cheers

    Stuart

    Stuart
    • Marked as answer by Stuart Fawcett Wednesday, July 28, 2010 12:35 PM
    Wednesday, July 28, 2010 12:35 PM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi Stuart,

    When you use the plugging registration tool, make sure you have the latest version and make sure you access crm with the short net bios name.  Also, in the ifdconfig tool verify that the ip address of the server and 127.0.0.1 is included in the list of ips.

    Alex Fagundes - www.PowerObjects.com
    • Marked as answer by Jim Glass Jr Thursday, July 22, 2010 3:56 PM
    • Unmarked as answer by Stuart Fawcett Thursday, July 22, 2010 4:35 PM
    Thursday, July 22, 2010 3:24 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi ALex,

    This 127.0.0.1 looks to be a very good idea, but in my case its not working yet, still  “Unable to connect to the Discovery Service”

    I'm using the short net bios name and now also seeking out the latest latest plugin registration tool, but i don't think its this as I noticed this with another part of the solution where i have a call out of a plugin to another system, this plugin also errors with "HTTP Status 401: Unorthorized".

    I'm thinking DNS, AD or Kerberos  issues somewhere at present.

    Cheers,

    Stuart

    Stuart
    Thursday, July 22, 2010 4:35 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Check this registry key:

    hklm/software/microsoft/mscrm/localsdkport

    This key should be the port number that you are running crm on.  If you changed the port after it was installed there is a chance this is wrong.  If your crm runs on port 5555 then this reg key should be 5555.

    Alex Fagundes - www.PowerObjects.com
    • Marked as answer by Jim Glass Jr Thursday, July 22, 2010 5:37 PM
    Thursday, July 22, 2010 4:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thnaks Alex, No its all standard ports and it switches on and off as i turn IFD on and off i'm still trying to see what might be causing this - i've been checking DNS and manually adjusting the hosts file etc. now looking at static routes - ROUTE ADD etc to try a clean connection.

    Its as if the app can no longer hold a session with its self when IFD is enabled. I have an other custom tool that also fails alon with the Plugin reg tool when IFD is turned on and this also fails with a Host error saying unauthorised.....

     

    Stuart
    Friday, July 23, 2010 5:07 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    OK if finally came down to being a config error - the IFD declared IPaddresses and subnet masks 

    I needed to add the www.xxx.yyy.zzz address of the server and a suitable subnet mask - i started with 255.255.255.0 and reduced it down to 255.255.255.255 - i'd left in 1270.0.1 & 255.255.255.255

    So thanks for you answers guys but in the end it came down to allowing the server to talk to itself.

    Cheers

    Stuart

    Stuart
    • Marked as answer by Stuart Fawcett Wednesday, July 28, 2010 12:35 PM
    Wednesday, July 28, 2010 12:35 PM