web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

"incident entity does not exist" error while configuring Celedon Auto Number

(0) ShareShare
ReportReport
Posted on by 352

Hi, good morning to everyone. We have been using Celedon Auto Number in a couple of customers with CRM Online and On Premise (single server deployment) with success. However, while working in a project with a customer who has CRM 2016 On Premise in multiple server deployment, I am not able to create any Auto Number rule entry. I always got a message saying the entity does not exists. For example, "incident Entity does not exist". I am aware we need to use the schema name for entities and that those names are always in lowercase and I am totally sure I am entering the other parameters correctly. I tried to use the tool with other entities with the same result. We added some extra code to try to figure out where the problem is located and the log file now shows this:

The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in Faulted state.


Checking the Internet I found that message is sometimes related with problems with the Sandbox service in CRM. I double checked this and I am sure the service is up and running, .Net version is 4.5.2 in CRM servers and there are no weird messages in Event Viewer related to this process. The same customer has a Dev environment which runs in a single server deployment and on that environment Celedon Auto Number works perfectly.

I would to know if some of you have found the same problem with this Solution. Any ideas about how to solve this are really, really much appreciated.

Xavier Villafuerte

*This post is locked for comments

I have the same question (0)
  • tw0sh3ds Profile Picture
    5,600 on at
    RE: "incident entity does not exist" error while configuring Celedon Auto Number

    This project is on github, why you don't write your question there? The authors will probaby be the best source of such informations...

  • Verified answer
    Xavier Villafuerte Profile Picture
    352 on at
    RE: "incident entity does not exist" error while configuring Celedon Auto Number

    just FYI. The problem was not in the Celedon AutoNumber solution but in the customer infrastructure. SPNs were not configured for the CRM front end server. These articles were really helpful while troubleshooting the issue.

    http://fkbase.info/node/156

    technet.microsoft.com/.../hh699825.aspx

    Finally, be sure port 808 is open between front end and back end server. That port is needed for Sandbox service to work fine.

    Xavier

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Pallavi Phade – Community Spotlight

We are honored to recognize Pallavi Phade as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
Community Member Profile Picture

Community Member 2

#1
UllrSki Profile Picture

UllrSki 2

#3
SC-08081331-0 Profile Picture

SC-08081331-0 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans