locked
EndpointNotFoundException for Sandbox server RRS feed

  • Question

  • I have two CRM Servers:

    1. Full Server Installation (behind firewalls in trusted VLAN)
    2. Front-End Only server (in DMZ VLAN) that is hosting the Org Service

    I am getting an error when I save a record on my Front-End Only that fires a Sandboxed Plugin (Post-Create):

    The plug-in execution failed because no Sandbox Hosts are currently available. Please check that you have a Sandbox server configured and that it is running.
    System.ServiceModel.EndpointNotFoundException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #47CA4F98

    I am also getting errors when I restart IIS in my Event Log on the Front-End Only server that say:

     System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.tcp://<back-end server>/CrmSandboxHost that could accept the message. This is often caused by an incorrect address or SOAP action. 

    Originally I was getting an error about could not connect but after opening the firewall the error changed to the above.  I've tried adding an SPN for the Sandbox Service on the Back-End Server, but it doesn't seem to make a difference.

    This is happening as a result of my need for a "public" Org Service.  In this other question, I asked how that might work.

    I am tempted to add the Back-End components to my Front-End Only server, but it seems like the "distributed" model of the CRM installation should allow for a completely separate Back-End tier.

    Thanks,
    Chris

    Tuesday, February 5, 2013 2:23 PM

Answers

  • I was finally able to solve my issue.  It involved three steps:

    1. Edit registry on the Full CRM server: HKLM\SOFTWARE\Microsoft\MSCRM\sandboxforcemultiplebox (DWord) = 1
    2. Add SPN's to DMZ server for the CRM Service (IIS AppPool Identity) for Cpu Name, FQDN, and CName
    3. Modifying applicationHost.config on DMZ server per KB article: useKernelMode="true" useAppPoolCredentials="true"

    As Andre pointed out, it was important to have the firewall port that the Sandbox uses open (port 808)

    Friday, May 24, 2013 12:49 PM

All replies

  • Hi Chris,

    This message I didn't receive. I solved these problems.

    Did you open enough firewall ports? Because the Sandbox Service runs on different ports.

    Also, did you set:

    useAppPoolCredentials on as well your XRMDeployment application pool (Domain Account) and CRMAppPool (Domain Account)? Also use KernelMode="true" (Only for CRMAppPool needed).

    Did you set: the ServerUrl in registry? The bindings in IIS? Watch out: no more then one binding. This will cause CRM to fail. Don't use CName Records, because that will fail too. This only translates the address to server, and will fail.

    Regards,

    André Krijnen

    Tuesday, February 12, 2013 11:38 PM
  • I was finally able to solve my issue.  It involved three steps:

    1. Edit registry on the Full CRM server: HKLM\SOFTWARE\Microsoft\MSCRM\sandboxforcemultiplebox (DWord) = 1
    2. Add SPN's to DMZ server for the CRM Service (IIS AppPool Identity) for Cpu Name, FQDN, and CName
    3. Modifying applicationHost.config on DMZ server per KB article: useKernelMode="true" useAppPoolCredentials="true"

    As Andre pointed out, it was important to have the firewall port that the Sandbox uses open (port 808)

    Friday, May 24, 2013 12:49 PM