Skip to main content

jQuery ajax error logging on the server with log4net

This post is based on Toby Gundry's post on the same technique, but adapted for logging jQuery ajax errors (although I added a few extra things too).

In your Javascript:

        ajaxError: function (event, jqXHR, ajaxSettings) {
            var err = "Location: " + document.location.href + "; ";
            if (jqXHR)
                err += "Status: " + jqXHR.status + "; ";
                err += "Text: " + jqXHR.statusText + "; ";
            if (jqXHR.responseJSON) {
                err += "Message: " + jqXHR.responseJSON.Message + "; ";
                err += "Stack Trace: " + jqXHR.responseJSON.StackTrace + "; ";
            if (ajaxSettings) {
                err += "Data Sent: " + + "; ";
                err += "URL: " + ajaxSettings.url + "; ";
            var message = btoa(err);
            var log = new Image();
            log.src = "/JSLogger.ashx?error=" + message;
            //display some kind of friendly error message to the user

I used the btoa function for base64-encoding the content, but it's quite possibly unnecessary.  Anyway, make a JSLogger handler, something like this:

    public class JSLogger : IHttpHandler
        private static readonly ILog Log = LogManager.GetLogger(typeof(JSLogger));

        public void ProcessRequest(HttpContext context)
            string encodedError = context.Request.QueryString["error"];
            byte[] bytes = Convert.FromBase64String(input);
            string error = Encoding.ASCII.GetString(bytes); //using Unicode seems to have weird effects

                string name = "Username: " + context.User.Identity.Name;
                error += name;
            catch(Exception e){} //in case the username isn't available

        //IHttpHandler boilerplate omitted

Let me know if you have any ideas for improvement!


Post a Comment

Popular posts from this blog

'A section using configSource may contain no other attributes or elements' error after installing Application Insights

After installing the Application Insights nuget package to an Umbraco solution, you'll get this error:

A section using 'configSource' may contain no other attributes or elements

<ExamineLuceneIndexSets configSource="config\ExamineIndex.config" />
     <log4net configSource="config\log4net.config">
             <level value="ALL" />
             <appender-ref ref="aiAppender" />
Source File: \project\web.config

This happens because part of the Application Insights installation process adds a <log4net> section to web.config.  Which would make sense, except Umbraco already has a <log4net> section in /config/log4net.config.  So as you can imagine, the solution is to manually move everything its added into that file. Unfortunately you can't just copy/paste the whole lot, but it's not particularly complicated:

Move <appender-ref ref="aiAppender" /> into the lo…

Handling double-quoted CSVs in Azure Data Factory Pipelines

Azure Data Factory by default uses a backslash as the escape character for CSVs, but we ran into an issue with this today processing one of the CSV files from  As with most CSVs they use quotes around values as normal and with double-quotes for empty values, but they also use double-quotes to escape quotes within non-empty values. This probably sounds confusing, so here's an example:

"column 1","column 2","","column 4 value is ""sort of"" like this"

The ADF pipeline failed because the double-quotes don't get escaped correctly:
ErrorCode=UserErrorSourceDataContainsMoreColumnsThanDefined, found more columns than expected column count.

The solution was to change the "Escape character" property on the dataset, by clicking the "Edit" button beneath it and manually entering "", since "" isn't in the list of escape characters.  I didn't think this would work at fir…

How to make yourself a Dynamics CRM 2011 Deployment Administrator

Today I needed to deactivate one of our Dynamics organisations, but when I opened the Dynamics Deployment Manager, I received the following error:

"Only the Deployment Administrators are able to use Deployment Manager. You are not a Deployment Administrator."
Bummer. I did a bit of Googling and found this post by Ronald Lemmen (thanks for pointing me in the right direction!).  Since the Dynamics Deployment Manager is obviously checking the MSCRM_CONFIG database for this information I attached a database trace to it and found that it's executing these queries (among many others):

exec sp_executesql N'SELECT  Id, [DefaultOrganizationId], [IsDisabled], [Name]   FROM [SystemUser]   WHERE ((([Name] = @Name0)) ) AND (IsDeleted = 0) ', N'@Name0 nvarchar(41)',@Name0=N'{My windows domain account}'
exec sp_executesql N'SELECT  Id, [Name], [UniqueifierId]   FROM [SecurityRole]   WHERE ((([Name] = @Name0)) ) AND (IsDeleted = 0) ', N'@Name0 nvarchar…