Posts

Showing posts from 2018

Added Contact Is Not Shown in List Manager in a Scaled Sitecore XP 9

There was a time when I needed to help someone from finding what’s wrong with List Manager in a scaled SXP 9 (the exact version was Sitecore Experience Platform 9.0 rev. 180604 (9.0 Update-2) ). New contacts added into List Manager does not appear even though the blue color message box around the top area says: “ The contact has been added to the list, and will be available after indexing. ” Looking at the Sitecore logs, there are errors such as: 4244 17:14:27 ERROR [ListManagement]: Failed to get count of contacts for 86c048c4-761d-47c8-814f-30344a5dcac8 contact list. The error has been occurred: The HTTP response was not successful: InternalServerError Exception: Sitecore.XConnect.XdbSearchUnavailableException Message: The HTTP response was not successful: InternalServerError Source: Sitecore.Xdb.Common.Web    at Sitecore.Xdb.Common.Web.Synchronous.SynchronousExtensions.SuspendContextLock[TResult](Func`1 taskFactory)    at Sitecore.XConnect.Client.XConnectSync

Why Translation Command in Content Editor Does Not Work in Sitecore Experience Commerce 9.0 Update 1

Image
This article explains what causes the translation in Content Editor to be not working correctly in Sitecore Experience Commerce (SXC) 9.0 Update-1 installed on Sitecore XP 9 Update 1 (rev. 171219) . The scenario is when you run two instances of Sitecore XP 9.0.1 , one with SXC 9 installed and another one without SXC 9 (I will call it “default” SXP 9 as this refers to the fresh instance without SXC 9 installed), clicking on the Translation Command will give the following results. This is how it looks in default SXP 9. Whereas, this is how it looks in SXC 9 (in the ribbon, VERSIONS > Translate command button is clicked but the translation is not shown). The reason can be explained as follows: Let’s first look at the difference of showconfig (<yourSitecore>/sitecore/admin/showconfig.aspx) between those two instances. There are 2 additional processors under <renderContentEditor> as highlighted in blue rectangle below.   The