Blog | Nimesh Manmohanlal personal blog

2014

Debug EPiServer Search (lucene)

A quick note to self: To debug EPiServer Search indexing, the below should be added to EPiServerlog.config:    <logger name="IndexingService"> <level value="All" /> </logger> <logger name="EPiServer.Search"> <level value="All" /> </logger>  <logger name="EPiServer.Core.ContentProvider" additivity="false"> <level value="Debug" /> </logger> <logger name="EPiServer.Data.Dynamic.Providers.DbDataStoreProvider" additivity="false"> <level value="Error" /> </logger> <logger name="EPiServer.Data.Providers.SqlDatabaseHandler" additivity="false"> <level value="Error" /> </logger> <logger name="EPiServer.Data.Providers.ConnectionContext" additivity="false"> <level value="Error" /> </logger>  

n nimeshjm
September 3, 2014
1 min read
EPiServer workflows – emails not being sent

The most commonly used workflow in EPiServer is the Sequential approval workflow. It is primarily used to assign tasks and send notifications through the various stages of page publication. Troubleshooting workflows is no easy task. You typically have to enable Windows Workflow Foundation diagnostics and examine the logs. You can achieve this by adding the following element to your web.config: <system.diagnostics> <switches> <add name="System.Workflow.Runtime" value="All" /> <add name="System.Workflow.Runtime.Hosting" value="All" /> <add name="

n nimeshjm
August 28, 2014
1 min read
Security misconfiguration – server headers

Revealing specific details about the operating system and the platform you are using to host your website can make it more vulnerable. While knowing that you’re using Windows/Linux as the operating system or IIS/Apache/nginx as your application server won’t make it less secure, it does help an attacker tailor his attack vector against your system. This type of vulnerability is detailed in the Owasp top 10: A5. Revealing information about your system may help an attacker.

n nimeshjm
February 25, 2014
1 min read
Debug live website performance with DebugDiag and Windbg – capture memory dump

In this scenario we have an application that performs slowly and has high CPU usage. Typically pages take longer to load and sometimes might timeout. Start DebugDiag Collector and select “Performance” Select the second option to monitor the HTTP response times of your website Add the urls to the pages that are performing slowly to monitor their response times Enter the page urls and set the timeout after which the rule is triggered.

n nimeshjm
February 7, 2014
1 min read
Debug live website crash with DebugDiag and Windbg – capture memory dump

Application crash In this scenario we want to capture a memory dump at the exact moment the application has crashed. Start the “Debug Diag Collection” tool and select “Crash” Select a specific application pool, i.e the application pool that your site is running. Select the application pool of your website Leave the defaults selected. In DebugDiag 2.0 this will record the call stack for first chance exceptions and a full memory dump for second chance exceptions, i.

n nimeshjm
February 6, 2014
1 min read