When more complicated problems with MCMS arise, I was finding myself wishing I could enable tracing to MCMS rather than go to support to solve the problem. Eventually I ended up using Reflector and finding the Switches MCMS uses internally. Being that none of these switches are documented anywhere else online, I thought I’d share the knowledge.
There are 3 Switches in total:
- CmsAuthTraceSwitch
- Trace messages related to authentication and authorization (I find myself using this one most often)
- CmsCacheTraceSwitch
- Trace messages related to node caching. Strangely enough, I have never enabled this one
- CmsGlobalTraceSwitch
- Trace messages related to everything else
Please note that these are all TraceSwitches and therefore need a value attribute between “1″ (just errors) and “4″ (verbose)
I hope this helps someone out there who is having trouble with MCMS
Advertisement
Hi Richard We have an MCMS issue and have been looking for a way to turn on some sort of logging. I came accross this blog with hope!!! I have inserted the code into our web.config and was wondering where the logs go? We have checked logfiles under the MCMS installation folder and the eventviewer, but found nothing. If you could clarify the location that would be great
Rob
Hi Rob,Once you have added the trace switches into your configuration file, the trace messages will go through the standard .NET tracing libraries. That means you can just setup a trace listener and the messages will be written to that.
Thanks, this helped and we have resolved our problem
Rob