A team member came to me this week with an exception I haven't seen before, which was “Too many variables in the testset”. Searching online was fruitless, so I wanted to share the reason and workaround for this bug.

Replacing a SOLR certificate is routine business these days, but something went sideways this time, and I couldn't stop the service, which led to its own problems. In the end I created a self signed one and used that instead, and I'll show you what I did to get the service to respond. 

My first post about working with new SaaS products! In my new role I'm working with Send to get the team more efficient with their tools. I'll be posting about a feature request I've made due to a shortcoming of its bulk operations, but first, we had an outage with all embedded forms, taking us offline for day. The explanation and workaround are simple, but the cause is not public knowledge. 

Ok I admit it. I took the easy way out. I was setting up a test environment of two instances using the standalone graphical installer and once done, I switched their roles. Everything worked except for one thing; the Experience Profile dashboard.

An Administrator's error caused the SQL account for Sitecore's collection database to be denied login. Normally you'd expect the related services to stop functioning, but in this case the system's various resources spiraled out of control.

We're closing in on the final phases of a Sitecore upgrade, which leverages GeoIp for CTAs and branding throughout the site including the global navigation. Invariably, we get reports from the testing team of inaccurate results. Today I'll walk through the validation and tricks I've used when I need to support someone without being at their same location.

I'm going through a number of Sitecore upgrades this year, and for the most part there have been no gotchas in our coding. This week one of our team members came across a RenderingContext issue that will be sure to catch some teams off guard.  

I recently migrated a project to a new environment, only to find that rendering a date field was inconsistently working. Not Sitecore's fault, but I've never seen this before, and I know as a seasoned developer I should have all (ok most) of the answers. It's a good catch and I wanted to share.

The Sitecore installation process has come a long way since the introduction of SIF. It has been flawless under countless runs, but I was recently tripped up due to a SQL connection error. In this post I'll explain the cause, resolution, and some steps to make your  next try of the installation easier. 

I've had a deluge of requests for a walkthrough of my latest module and the way it can help with excessive garbage data in the xDB. In this video I'll introduce the xDB to non-developers, talk about identifying the cyber attack, and how we can ignore/not capture the false traffic to your site.