Fixing Sitecore xConnect and xDB errors

Short answerMost Sitecore xConnect errors come from three causes: the xConnect client certificate has expired or its thumbprint doesn't match, an xConnect Windows service such as the Search Indexer has stopped, or the xDB Solr cores are unhealthy. If your organization doesn't use personalization or analytics, switching xDB off is often the simplest and cheapest fix.

xConnect is the service layer Sitecore XP uses to store and read visitor data in the Experience Database (xDB). It powers analytics, personalization, the Experience Profile, marketing automation and parts of Sitecore Forms. When it breaks, the site itself often keeps working, but the logs fill with errors and features quietly stop.

Common symptoms

  • The Sitecore log has repeated errors mentioning xConnect, the collection service or certificates.
  • The Experience Profile is empty or shows an error.
  • Analytics dashboards show no new data.
  • Personalization rules based on visitor behavior stop working.
  • The site is slower because each request waits for xConnect calls to time out.

1. Expired or mismatched certificates (the most common cause)

Sitecore servers use a client certificate to talk to xConnect. The certificate thumbprint is stored in the connection strings. Certificates created during installation often have short lifetimes, so a year or two after go-live they expire, and xConnect starts refusing connections. Nothing in Sitecore warns you in advance.

Fix:

  1. Open the certificate store on each Sitecore server and check the expiry date of the xConnect client certificate.
  2. Compare its thumbprint with the one in ConnectionStrings.config on the Sitecore roles and in the xConnect configuration.
  3. If it has expired, create or buy a new certificate, install it, give the app pool identity read access to its private key, and update the thumbprints everywhere they appear.
  4. Put the new expiry date in a shared calendar with a reminder a month before.

Missing private key permissions is the classic follow-up problem. If errors continue after a certificate change, check those first.

2. A stopped Windows service

xConnect depends on background services, especially the xConnect Search Indexer and the Marketing Automation Engine. They're Windows services (or WebJobs on Azure), and they stop after server restarts or crashes without anyone noticing. When the Search Indexer stops, the Experience Profile and contact search go stale.

Fix: check that both services are running and set to start automatically. Read their own log files in the xConnect folder, because their errors don't appear in the main Sitecore log.

3. Unhealthy xDB Solr cores

xConnect uses its own Solr cores, usually named xdb and xdb_rebuild. If these cores are broken, out of sync, or on a Solr version Sitecore doesn't support, contact search fails.

Fix: check the cores in the Solr admin UI. If the xdb index is broken, Sitecore provides a documented process to rebuild it using the rebuild core. See also Sitecore Solr index problems.

4. Collection databases and processing pools

xDB stores data in SQL collection shards and uses processing pool tables to queue work. When processing falls behind, those tables grow and the reporting data goes stale. Large shard databases also make backups slow.

Fix: monitor the size of the shard and processing pool databases, and agree how long you actually need to keep visitor data. Sitecore has documented options for removing old contacts and interactions. See Sitecore database growth.

5. If nobody uses it, switch xDB off

Many organizations bought Sitecore XP for its marketing features and then only ever used the content management side. If that's you, xDB is costing you servers, licences for SQL and Solr capacity, and support time, for data nobody looks at.

You can switch off xDB and tracking with these settings:

  • Xdb.Enabled set to false
  • Xdb.Tracking.Enabled set to false

This stops Sitecore from calling xConnect. Do it with a proper config patch, test Sitecore Forms and any personalization first, because some features depend on xDB. If you later decide you only need content management, moving to Sitecore XM may also reduce licence costs. That's worth discussing with your Sitecore account manager.

What to do next

Check the certificate expiry date today. It takes two minutes and it's the cause in a large share of cases. If you're not sure whether your organization uses xDB at all, I can review your setup and give you a clear recommendation as part of a support engagement.

Prabh

Independent Sitecore developer and administrator. I help agencies and businesses keep Sitecore fast, patched and publishing.

Get in touch

Got a Sitecore problem that won't go away?

Tell me what's happening. You'll get a straight answer on whether I can help, usually within one business day.

Book a free 20-minute call