Skip to main content

Experience Analytics not working

Hello Sitecorian,

How many of you have encountered an error or the situation where graph on the experience analytics dashboard or graph on launchpad's dashboard is not working

I recently encountered with this scenario where i was presented with the situation where simply graph was not coming up, Before digging completely into it and checking logs and everything, From very first high level thoughts pointed me to check

  • Is the valid certificate is used for xconnect?
  • Are thumbprints are correct in all configs? We had scaled environment so i needed to check the thumbprint in all the needed roles.
  • Is xconnect site is accessible from CD? Without any https exceptions?
  • Is XDB is enable? 
  • Is Tracking is enable? 
Everything looked ok on first place, so i finally took my sleeves up and started digging into details, Below are the details steps and exceptions those were captured and i will also show you the topology of instances we were using.

Scaled instance

We are using Sitecore 9.0.2 XP1 installation so we had CM and CD two physical servers, and on CM we had all roles installed with different web site in IIS, so basically all roles are working separately.

Now it was time to start to do some initial check, in most 99% cases it is certificate issue or certificate thumbprint issue so i quickly did following

1) Checked xconnect certificate on CM and CD and also double checked the thumbprint used 
You can find Here The detail steps how to see correct certificate and correct thumbprint of that certificate and make sure the same thumbprint is used in all the roles, In our case everything was good, right thumbprint was used in all roles, all had correct thumbprint of xconnect certificate.

2) Checked by visiting the xconnect site URL from CD and CM
To make sure that visits are registered, first step is to check if the xconnect site is accessible from CD instance and it was being accessible in our case, right certificate was used and correct site was being resolved.

3) Very initial steps after sitecore installation is to "Deploy marketing definitions" and "Rebuild link database"
It is must to deploy marketing definitions after configuring the scaled instance, as shown below in the image taken from Sitecore Documentation 
This steps was performed, i restarted IIS and visited the CD site but still there was no graph.
4) Double check the connection string on all roles.
Just to make sure that all roles are having right connection strings and having proper username and password, and right certificate thumbprint.
 5) Check the log of XConnect Instance, CM server Processing instance and Reporting instance
On checking the xconnect log i came across below exception

System.UnauthorizedAccessException: Access to the registry key 'Global' is denied


To fix this exception, we will need to add app pool user to the following groups

Performance Monitor Users
Performance Log Users

to do that, go to Computer Management and go to following path



Now double click both of this and add xconnect app pool use to this group, restart IIS and check the log again, GOOD, the error was gone

NOTE: Make sure to see whichever role is having this exception, add them to this group.

6) Message: Login failed for user 'poolsuser' in processing role instance log.
Because processing does the processing for collected data and processes it, this exception also gave me the clue that something is wrong, and i checked in the database and found out that in connection string for processing this user was used.

So i checked the DB and processing database and found out that this user did not exist for some reason, so created user and gave it proper access rights, restarted the processing instance and this error was gone, and now processing user was able to connect to DB.

7) Dimension could not be resolved for for dimension id: {GUID}
Looking further, when connection strings were checked and all instance were able to connect to DB , i started getting

10472 07:59:51 ERROR [Experience Analytics]: SegmentProcessor failed to process interaction 'fde57c16-f6a0-0000-0000-058df2ab65f2' segment '2985ad79-b475-494d-a3e0-df2573e66f04' - System.InvalidOperationException: Dimension could not be resolved for for dimension id: fa282c5b-a373-4b89-9977-18a8498ee53e
   at Sitecore.ExperienceAnalytics.Aggregation.Data.Model.AggregationSegment.get_Dimension()
   at Sitecore.ExperienceAnalytics.Aggregation.Data.Model.AggregationSegment.GetData(IVisitAggregationContext context)
   at Sitecore.ExperienceAnalytics.Aggregation.Pipeline.SegmentProcessor.ProcessSegments(IInteractionAggregationContext context, IEnumerable`1 segments)
10472 07:59:51 ERROR Aggregation Error
Exception: System.InvalidOperationException
Message: Dimension could not be resolved for for dimension id: fa282c5b-a373-4b89-9977-18a8498ee53e
Source: Sitecore.ExperienceAnalytics.Aggregation
   at Sitecore.ExperienceAnalytics.Aggregation.Pipeline.SegmentProcessor.ProcessSegments(IInteractionAggregationContext context, IEnumerable`1 segments)
   at Sitecore.ExperienceAnalytics.Aggregation.Pipeline.InteractionProcessor.AggregateSegments(IInteractionAggregationContext context, AggregationScope scope)
   at Sitecore.Analytics.Aggregation.Pipeline.InteractionAggregationPipelineProcessor.Process(InteractionAggregationPipelineArgs args) 

I tried to search this in sitecore and found out that, Dimensions did exist on following path

"/sitecore/system/Marketing Control Panel/Experience Analytics/Dimensions/Connect/By contact orders"

We found out that this dimension belongs to Sitecore Commerce and processing instance also need this dimension and not only CM instance

So We went to Sitecore Commerce installation package and found out the folder "Sitecore Commerce ExperienceAnalytics Core 11.2.83.zip" and manually copied DLLs and Configs to processing server's bin and App_Config

Restarted the IIS but no luck, because one final step was missing

8) Rebuild Reporting DB
I tried to look into the table and found out that interaction table was actually having interactions, so only thing was that they were not being aggregated and processed to show the report somehow.

So It was time to Rebuild Reporting DB, Restarted IIS.



And.......Hurrreeeeyyyy the graph was back and started registering the hits, Phew...huge relief.

I had some close interaction with few of my colleague which really helped me understand the flow of information and xconnect troubleshooting

Kiran Patil
Mahek Chaniyara
Sreekrishnan

NOTE: After having this analytics issue, I found out that in most of the cases related to experience analytics and xconnect issue, Following are the most frequent reasons

1) Xconnect certificate and its thumbprint issue
2) Marketing definitions not deployed (Dimensions and Interaction will not be found otherwise)
3) Reporting DB is not rebuild

I hope above steps will help someone troubleshoot the issue related to similar situation




 

Comments

Popular posts from this blog

An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.

You have noticed many times that everything was working fine and suddenly the below error starts coming and you find no way to work it out An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. The reason for this is the receiving size of WCF service is smaller then the data which is coming from service It was working before because it was small,So you will have to try to increase the receiving setting in your end point,Possible settings can be following maxStringContentLength="2147483647" maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" maxArrayLength="2147483647" That would definately help you!!!

Sitecore Serialization - Error connecting to /.well-known/openid-configuration: Bad Gateway

Hi Team, Recently, I faced an issue where for the new project my Sitecore serialization started giving me following error. Error: "Error connecting to https://sc10.dev.local/.well-known/openid-configuration: Bad Gateway" My identity server when browsed above url was also not working and showing following. Well, I tried seeing logs and different things, I also followed what is given on these links.  https://sitecore.stackexchange.com/questions/34744/open-id-configuration-issue-with-sitecore-cli https://tekkishare.azurewebsites.net/pages/sitecore-clilogin-error-badgateway https://www.stockpick.nl/english/sitecore-cli-login-error/ But I was still getting the same error. Solution If you see above screenshot of my identity server, in "Troubleshooting steps" it is mentioned that "Check the system event log for error messages." It triggered me, I opened event log of windows, and I could see following error.  Now, i already update my .net run time version accordin

Set up leprechaun code generation with Sitecore XM Cloud Starterkit

Hi Sitecorians, It has been amazing learning year so far and with the change in technology and shift of the focus on frontend frameworks and composable products, it has been market demand to keep learning and exploring new things. Reasons behind this blog Today's topic is something that was in my draft from April-May, and I always thought that there is already a good documentation out there for  Leprechaun  and a blog post is not needed, Until I realized that there was so many of us facing same kind of issues and same kind of problems and spending same amount of time, That is where I thought, if I could write something which can reduce that repetitive troubleshooting time, That would really help the community. 1)  In a project environment, if we get into some configuration issues, we resolve them, we make sure we are not blocked and continue, but if you think same issue, same step and same scenario will come to other people, so if we can draft it online, it will help other people 2