{"id":2369,"date":"2016-05-04T10:50:09","date_gmt":"2016-05-04T10:50:09","guid":{"rendered":"http:\/\/sitecore.robhabraken.nl\/?p=2369"},"modified":"2019-12-18T12:58:46","modified_gmt":"2019-12-18T12:58:46","slug":"configuring-server-roles-part-1","status":"publish","type":"post","link":"https:\/\/www.robhabraken.nl\/index.php\/2369\/configuring-server-roles-part-1\/","title":{"rendered":"Configuring server roles"},"content":{"rendered":"

I have invested a lot of time lately in configuring different server roles and trying to see structure in the Sitecore documentation concerning server role configuration, which can be found here (…)\/xdb_configuration\/configuring_servers<\/a>. Mind that the documentation behind this link constantly changes, so I cannot guarantee that my blog will stay consistent with it, but at least for now it is. Actually, that is one of my largest concerns considering this topic: there’s only a version toggle on the top right between 8.0 and 8.1, but when working on it for a few weeks I saw it changing, without any chance logs or notifications. It is hard to make up if you need to update your Sitecore implementations based on those silent updates and even harder to keep track of any changes this way. I already sent in a feature request for this.<\/p>\n

I intend to do a series on this topic and share my findings, ultimately leading to an easy set of documentation on this. But to be honest, when almost having finished my first blog, it got outdated right away because Sitecore released an update.. I didn’t like the online list of files to disable and to enable, which was already improved by providing the list as an Excel worksheet (which also included numerous fixes like combining path and filename, using backward slashed instead of forward slashes and allowing you to sort on alphabet and on enable\/disable if you want). So I will still share as much as possible, but I know Sitecore is working on this too.<\/p>\n

onPublishEndAsync strategy<\/h2>\n

One of the things which turns out to be incomplete or not the full truth, is how to configure the processing server<\/strong>. The following instructions tell you to comment out the onPublishEndAsync strategy containing a reference to the web database, which isn’t available from the processing server: (…)\/configuring_servers\/configure_a_processing_server<\/a>.<\/p>\n

\"onpublishendasync\"<\/p>\n

Upon doing so, your processing server might stop working (strange enough, it didn’t in all cases) while reporting about the following exception:<\/p>\n

ManagedPoolThread #14 15:02:08 INFO  Trying to load XML configuration \/App_Config\/Security\/Domains.config\n3220 15:02:08 ERROR Error loading hook: <hook type=\"Sitecore.ContentSearch.Hooks.Initializer, Sitecore.ContentSearch\" patch:source=\"Sitecore.ContentSearch.config\" xmlns:patch=\"http:\/\/www.sitecore.net\/xmlconfig\/\" \/>\nException: System.InvalidOperationException\nMessage: Could not find configuration node: contentSearch\/indexConfigurations\/indexUpdateStrategies\/onPublishEndAsync\nSource: Sitecore.Kernel\n   at Sitecore.Diagnostics.Assert.IsTrue(Boolean condition, String message)\n   at Sitecore.Configuration.Factory.GetConfigNode(String xpath, Boolean assert)\n   at Sitecore.Configuration.Factory.CreateObject(String configPath, String[] parameters, Boolean assert)\n   at Sitecore.Configuration.Factory.CreateFromReference(XmlNode configNode, String[] parameters, Boolean assert)\n   at Sitecore.Configuration.Factory.CreateObject(XmlNode configNode, String[] parameters, Boolean assert, IFactoryHelper helper)\n   at Sitecore.Configuration.Factory.GetInnerObject(XmlNode paramNode, String[] parameters, Boolean assert)\n   at Sitecore.Configuration.Factory.AssignProperties(XmlNode configNode, String[] parameters, Object obj, Boolean assert, Boolean deferred, IFactoryHelper helper)\n   at Sitecore.Configuration.Factory.CreateObject(XmlNode configNode, String[] parameters, Boolean assert, IFactoryHelper helper)\n   at Sitecore.Configuration.Factory.GetInnerObject(XmlNode paramNode, String[] parameters, Boolean assert)\n   at Sitecore.Configuration.Factory.AssignProperties(XmlNode configNode, String[] parameters, Object obj, Boolean assert, Boolean deferred, IFactoryHelper helper)\n   at Sitecore.Configuration.Factory.CreateObject(XmlNode configNode, String[] parameters, Boolean assert, IFactoryHelper helper)\n   at Sitecore.Configuration.Factory.CreateObject(String configPath, String[] parameters, Boolean assert)\n   at Sitecore.ContentSearch.ContentSearchManager.get_SearchConfiguration()\n   at Sitecore.ContentSearch.Hooks.Initializer.Initialize()\n   at Sitecore.Events.Hooks.HookManager.LoadAll()<\/pre>\n
This isn’t strange at all, because multiple configuration files, that are still enabled on the processing server as indicated by the documentation, list the onPublishEndAsync strategy. I had contact with Sitecore support on this, and however we could not find the reason why it did<\/em> work on one of our implementations, we concluded that you cannot only remove the strategy, while not removing any references to it.<\/p>\n
So, our solution was to remove this strategy from the list in all of the following files as well (inside \\Website\\App_Config\\Include\\):<\/p>\n
\n