Skip to main content

Debugging a Tridion 2011 Event System

OK, so you wrote your Tridion Event System. Now it's time to debug it. I know this is a hypothetical situtation -- your code never needs any kind of debugging ;) but indulge me...

Recently, Alvin Reyes (@nivlong) blogged about being difficult to know how exactly to debug a Tridion Event System. More exactly, the question was "What process do I attach to for debugging even system code?". Unfortunately, there is no simple or generic answer for it.

Different events are fired by different Tridion CM modules. These modules run as different programs (or services) or run inside other programs (e.g. IIS). This means that you will need to monitor (or debug) different processes, based on which events your code handles.

So the usual suspects are:
  • dllhost.exe (or dllhost3g.exe) - running as the MTSUser is the SDL Tridion Content Manager COM+ application and it fires events on generic TOM objects (e.g. events based on Tridion.ContentManager.Extensibility.Events.CrudEventArgs);
  • TcmServiceHost.exe - fires the event that occurs when a Publish Transaction is created;
  • TcmPublisher.exe - fires publishing events based on Tridion.ContentManager.Extensibility.Events.PublishingEventArgs;
  • cm_wf_svc.exe - fires workflow events based on Tridion.ContentManager.Extensibility.Events.WorkflowEventArgs;
  • w3wp.exe - IIS process (not sure is used by Event System);
Tip: if you are not sure which process runs your event system DLL, have a look at the processes that 'use' the DLL (e.g. by using Process Explorer's "Find Handle or DLL..." functionality) and debug those.

Comments

Frank said…
TcmServiceHost fires the event that occurs when a publish transaction is created (TcmPublisher then does the transitions to other states).
Mihai Cădariu said…
Thanks Frank. I updated the post to reflect your information.
Nivlong said…
Not so much for Event System debugging, but Dominic Cronin describes how to use PowerShell's gci command to finding the right w3wp.exe process to attach to (for Content Delivery development).

http://www.dominic.cronin.nl/weblog/debugging-64-bit-tridion-content-delivery-on-iis-7.5-1/blogentry_view#1357182811077846
RobertC said…
In Tridion 2013 we need to attach to the TcmServiceHost, even if we are listening to ComponentSave events.
Mihai Cădariu said…
Yup... COM's gone! COM's gone... :)
Unknown said…
Hi,
I have implemented the Workflow using core-service in Tridion 2011. and i was able to debug the code by attaching the process "cm_wf_svc.exe". recently the Tridion version is being upgraded to 2013 and the Workflow is working fine, but now if i am trying to debug the code by attaching the process "TcmWorkflowAgent.exe", the execution is not stopping at the breakpoint and i am not able to Debug the code. can you please help me on this

Popular posts from this blog

Running sp_updatestats on AWS RDS database

Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: https://dba.stackexchange.com/questions/145982/sp-updatestats-vs-update-statistics I stumbled upon the following post from 2008 (!!!), https://social.msdn.microsoft.com/Forums/sqlserver/en-US/186e3db0-fe37-4c31-b017-8e7c24d19697/spupdatestats-fails-to-run-with-permission-error-under-dbopriveleged-user , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as

Content Delivery Monitoring in AWS with CloudWatch

This post describes a way of monitoring a Tridion 9 combined Deployer by sending the health checks into a custom metric in CloudWatch in AWS. The same approach can also be used for other Content Delivery services. Once the metric is available in CloudWatch, we can create alarms in case the service errors out or becomes unresponsive. The overall architecture is as follows: Content Delivery service sends heartbeat (or exposes HTTP endpoint) for monitoring Monitoring Agent checks heartbeat (or HTTP health check) regularly and stores health state AWS lambda function: runs regularly reads the health state from Monitoring Agent pushes custom metrics into CloudWatch I am running the Deployer ( installation docs ) and Monitoring Agent ( installation docs ) on a t2.medium EC2 instance running CentOS on which I also installed the Systems Manager Agent (SSM Agent) ( installation docs ). In my case I have a combined Deployer that I want to monitor. This consists of an Endpoint and a

SDL Web 8 - Content Delivery Microservices

Among the new features in SDL Web 8 there are the Content Delivery Microservices, namely: Audience Manager Content Deployer Contextual Image Delivery Discovery Service Dynamic Content Dynamic Linking Profiling and Personalization Metadata Query Taxonomy User Generated Content These microservices make up the Content Interaction Services and they expose the existing Content Delivery in-process APIs as RESTful services. They provide the server-side component in a Services-Oriented Architecture and act as data layer between the the web client and the Content Delivery Storage Layer. According to the SDL marketing, these microservices: Simplify upgrades, thus offering shorter time to value Modernize architecture, offering better separation between the web application and Tridion APIs Offer more flexibility with less downtime and improved scalability Improve quality, being self-running, contained and having less dependencies In technical words, these microservices