.NET Daily

Sitecore Tracker.Current is not Initialized – During setup of a single Sitecore CD

Introduction

Darius

Darius

Darius Dumitrescu is a creative Senior CMS Consultant with in depth .NET knowledge, focused on Web Development and Architecture Design.


LATEST POSTS

How to solve: An expression tree may not contain a dynamic operation – ASP.NET Core 06th July, 2019

How to use DbContext Scaffold to add only selected tables – ASP.NET Core 01st July, 2019

Sitecore

Sitecore Tracker.Current is not Initialized – During setup of a single Sitecore CD

Posted on .

For configuring the productions instances for a Sitecore project, we usually follow this tutorial from Sitecore website for new CDs configurations.

However, after configuring a particular single Sitecore CD deployment, the following exception has been encountered: System.InvalidOperationException: Tracker.Current is not initialized.

The detailed exception can be seen in the image below:

After trying the solutions from several articles on this matter without any result, we noticed that when installing only a single Sitecore CD environment, the Analytics.ClusterName and Analytics.HostName from the Sitecore.Analytics.Tracking.config file needs to be left with the default values in order for the analytics to work.

So, try it out these changes and see if it solves the issue for you. If not, have a look at this article as well. It further continues the investigation for a possible issue.

Please remember though that these changes are applicable only to a single Sitecore CD installation.

Darius

Darius

Darius Dumitrescu is a creative Senior CMS Consultant with in depth .NET knowledge, focused on Web Development and Architecture Design.

There are no comments.

This site uses Akismet to reduce spam. Learn how your comment data is processed.

View Comments (0) ...
Navigation