Almost near to the end of a major Sitecore as well as infrastructure upgrade from Sitecore version 7.2 to 9.0.2. Thought of penning my upgrade story which becomes more spicier with lots of mysterious twists by having xConnect in the lead role. 😊
Just like all my previous Sitecore upgrades this was almost similar apart from adding Sitecore Official Nuget, CI/CD using Octopus and most importantly the tedious patch up between xConnect and the client certificates issued by organizational authorities. Using Sitecore official Nuget for latest assembly references and Express migration tool for Database migration, the upgrade was a bit smoother without any critical errors/hiccups. But when we were at the stage to test the complete ecosystem in XP9 platform from hitting the website and generating the related reporting graph on the Experience Analytics Dashboard, resolving the issues with xConnect and non-self-signed Client Certificates was such a bumpy ride. 😦
We faced a lot of issues and it was troublesome to find root cause behind the incompatibility between xConnect and Client Certificates. I also get a chance to chat with some of my Sitecore community friends over Slack and almost everyone who implemented Sitecore 9 for the very first time, sailed the same boat. Though as always I found a lot of excellent blogs and questions on SSE with similar problem and relevant answers. But for us the culprit was something else but not Certificates hence thought of blogging a consolidated post with all the issues we faced and our approach towards Nirvana!!!
So we have a scaled Sitecore 9.0.2 environment with
- One Instance for combined Content Management, Processing and Reporting Roles
- Scaled Instances for each the xConnect roles
- xConnect Collection
- xConnect Collection Search
- xDb Reference Data
- Marketing Automation Operation
- Marketing Automation Reporting
- Two Load balanced Instances for Content Delivery Roles
- Two Solr Instances – Master and Slave
- Two SQL Server Instances
Please have a look at the Sitecore Network Topology Diagram. The CM and few of the databases were on the corporate (internal) network whereas the xConnect, Solr, SQL and the CD Roles were on DMZ behind F5.
Following are the series of exceptions we faced one after another when we were applying the fixes during our research and debugging.
Series of Incompatibility Exceptions
FATAL [Experience Analytics]: Failed to synchronize segments. Message: Ensure definition type did not complete successfully. StatusCode: 401, ReasonPhrase: 'Invalid certificate', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
FATAL [Experience Analytics]: Failed to synchronize segments. Message: Ensure definition type did not complete successfully. StatusCode: 403, ReasonPhrase: 'Forbidden', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
An unhandled exception of type 'Sitecore.XConnect.XdbCollectionUnavailableException' occurred in mscorlib.dll The HTTP response was not successful: Unauthorized
Really great article and very helpful. Just wanted to add that often the update of thumbprint is missed in AppSettings.Config file of relevant App Services which could lead to analytics not working.
I am facing the same issue.
Sitecore.XConnect.XdbCollectionUnavailableException – An error occurred while sending the request-Sitecore.Xdb.Common.Web.ConnectionTimeoutException
Can you pls let me in detail about F5 and CLR check and how it got resolved.