(Ektron CMS 400.Net,Microsoft Windows)
by Jason Skowronek
on 04/08/2010
Ektron has a snazzy plug-in framework that allows developers to write applications that hook directly into the CMS event model, thereby allowing us to create our own logic that is handled inline, alongside, within the CMS's.
If you have installed the Ektron Developer SDK as part of your core platform installation, this service will run automatically and has a couple of default plug-ins (Google, etc.) that run after installation.
The problem is that out of the box, these modules are not configured, so every time someone does anything in the work area that causes the plug-ins to fire, you may see errors similar to this in your Event Viewer/Log:

This can be somewhat annoying when dealing with larger CMS sites that have hundreds or thousands of users, constantly adding, editing, and deleting content. I would imagine most installations do not need the service running, and it was probably installed by accident by the system/server administrator. In these circumstances, the easiest thing to do is to just disable the service in the Windows Services Manager. However, if you actually have a need for the plug-in service to run, you will need to manually configure the problematic plug-ins through the Extensibility Configuration Editor. More than likely your developers have already done this is probably irrelevant.
Hopefully this helps someone searching for a reason for all the "CMS-Plugin" even log errors.