We wanted to setup a server as ContentManagement,Processing and Reporting instance. As we can combine roles, we changed the config accordingly.

<add key="role:define" value="ContentManagement,Processing,Reporting" />

We immediatly got errors and noticed that we hadn't done the content management setup as described here. So we set the serviceUrl's and got rid of the errors. Looked weird to send all requests for processing and reporting to ourselves but still.. let's try to follow the guide.

But.. our server went berzerk.. CPU peaking, no responses anymore.

We tried to set the server (back) into the "Standalone" role, and he worked fine. So, something seems wrong with the config role setup?

Using Sitecore 9.0-update1. Trying to setup a CM (incl reporting & processing) + CD...

  • Any idea if this issue is resolved for Sitecore 9.1? Jul 2, 2019 at 14:24
  • I would assume it is, but haven't been able to test that yet
    – Gatogordo
    Jul 2, 2019 at 15:28
  • I was checking with Sitecore 9.1 and got the same errors when role was defined as above Jul 3, 2019 at 8:52
  • @PankajTiwari - Did you get the errors for Sitecore 9.1 Initial Release? Nov 21, 2019 at 4:50
  • @VarunShringarpure, yes we had similar errors on Sitecore 9.1 initial release but removing content management from role solved the issue. Nov 22, 2019 at 10:54

2 Answers 2


We called upon Sitecore Support and they told us this was a "bug". It will be documented but until that is done, you can follow this guide:

  1. App_Config\Sitecore\Marketing.xDB\Sitecore.Xdb.Remote.Client.config: set role:require on sitecore element to "ContentManagement AND !Reporting"

    <sitecore role:require="ContentManagement AND !Reporting">

  2. App_Config\Sitecore\Marketing.xDB\Sitecore.Xdb.Remote.Server.config: set role:require on reporting element to "Reporting AND !ContentManagement"

    <reporting role:require="Reporting AND !ContentManagement">

  3. App_Config\Sitecore\PathAnalyzer\Sitecore.PathAnalyzer.RemoteClient.config: set role:require on sitecore element to "ContentManagement AND !Reporting"

    <sitecore role:require="ContentManagement AND !Reporting">

  4. App_Config\Sitecore\PathAnalyzer\Sitecore.PathAnalyzer.Services.RemoteServer.config: set role:require on sitecore element to "Reporting AND !ContentManagement"

    <sitecore role:require="Reporting AND !ContentManagement">

  5. App_Config\Sitecore\Marketing.Operations.Xdb.ReferenceData\Sitecore.Marketing.Taxonomy.Xdb.ReferenceData.config: set role:require on sitecore element to "(Processing or Reporting) AND !ContentManagement"

    <sitecore role:require="(Processing or Reporting) AND !ContentManagement">

  6. App_Config\Sitecore\Marketing.Operations.Xdb.ReferenceData\Sitecore.Marketing.Operations.Xdb.ReferenceData.config: Set role:require on sitecore element to "(Processing or Reporting) AND !ContentManagement"

    <sitecore role:require="(Processing or Reporting) AND !ContentManagement">

When doing this, there is no more need to set serviceUrl and such as the remoting for reporting and processing server is turned off as it should.

  • I guess at the end of the day.. what's the difference between "Standalone" and "CM/Process/Reporting"? At that point, you're just excluding CD, which... to be fair, generally you want to deliver elements of your site. My assumption is the Sitecore probably expected people to just use "Standalone" for that configuration then trying to call out each role. Feb 8, 2018 at 16:07
  • We made that assumption as well, but as Support didn't tell us to just use Standalone we tried this. Will be checking the differences between Standalone and our combi to see if there is any benefit in doing this.
    – Gatogordo
    Feb 8, 2018 at 16:13
  • Thank you, this seems to have solved the issue. Is there a public reference number for the Sitecore bug?
    – Dave
    Feb 19, 2018 at 17:36
  • There are 3: 205757, 203749, 205439
    – Gatogordo
    Feb 19, 2018 at 18:58
  • @PeteNavarra I thought the same however was slightly concerned that this may impact the inter-role communication eg. Publish / Indexing events etc. Gatogordo have you noticed anything particular around the processing remotes/clients, they haven't been called out and I would think that the issue may be similar?
    – Svenkle
    May 1, 2018 at 9:05

It looks like this issue has now been resolved in Sitecore 9 Update 2: https://dev.sitecore.net/Downloads/Sitecore%20Experience%20Platform/90/Sitecore%20Experience%20Platform%2090%20Update2/Release%20Notes

"The Experience Analytics and Path Analyzer applications fail to start on a Sitecore instance that is configured with the following role combination: Content Management, Processing, and Reporting ."

  • Not completely. On 9 Update-2 You will still have to patch Sitecore.Marketing.Taxonomy.Xdb.ReferenceData.config Sitecore.Marketing.Operations.Xdb.ReferenceData.config
    – Mark Lowe
    Mar 7, 2019 at 11:42

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.