SXC 92 Installation Errors and Some Solutions

I recently wrestled with an SXC 9.2 Installation and ran across a number of problems to which I found no answers.

Working with Sitecore Support, and the school of hard knocks, I'm happy to provide another loosely-organized list of solutions in the hopes that your SXC 9.2 installation runs much smoother than mine own.

  1. Edit the Master_SingleServer.json
    In the Sitecore Experience Commerce Installation Guide for On-Premise Solutions manual, i.e. the SXC 9.2 installation manual, on page 18 Sitecore advises us:
    Sitecore Advisory
    This advice is to be heeded.
    To be explicit, this means editing the SIF.Sitecore.Commerce.3.0.28/Configuration/Commerce/Master_SingleServer.json file by manually removing entries from the "Includes" object.
  2. Error: Before you run the deployment script again, you must remove the reference to the "ModuleHabitatImages" from the Includes section of the Master_SingleServer.json file
    During the install of SXC 9.2, if you should greeted with the message:
    Before you run the deployment script again, you must remove the reference to the "ModuleHabitatImages" from the Includes section of the Master_SingleServer.json file
    You should follow the advice elucidated in item one, above: Remove the following element from the SIF.Sitecore.Commerce.3.0.28/Configuration/Commerce/Master_SingleServer.json file along with all preceding "Includes" entries:
    "Module-HabitatImages": {   "Source": ".\\Configuration\\Commerce\\Common\\Common.InstallWdpModule.json" },
    In fact, the Sitecore Experience Commerce Installation Guide for On-Premise Solutions manual mentions the same on page 32, section "6.5. fails to deploy".
  3. (500) Internal Server Error response to PUT
    You may be presented with the following error message as well (I've formatted the error message for easier reading):
    Error when calling Bootstrap()
    PUT with 0-byte payload
    Install-SitecoreConfiguration : The remote server returned an error: (500) Internal Server Error.
    ERROR Message=SQL.GetDBVersion.Fail: Environment='GlobalEnvironment'|Message='Login failed for user 'DMZVM04\CSFndRuntimeUser'. '|Number='18456' |Procedure='' |Line='65536' |CorrelationId=7ec8bb66180f4348ad19a1da3de49422 |StackTace=    at System.Data.SqlClient.SqlInternalConnectionTds..ctor(
    DbConnectionPoolIdentity identity,
    SqlConnectionString connectionOptions,
    SqlCredential credential,
    Object providerInfo,
    String newPassword,
    SecureString newSecurePassword,
    Boolean redirectedUserInstance,
    SqlConnectionString userConnectionOptions,
    SessionData reconnectSessionData,
    DbConnectionPool pool,
    String accessToken,
    Boolean applyTransientFaultHandling,
    SqlAuthenticationProviderManager sqlAuthProviderManager)
    Sitecore Support advised that I modify the SIF.Sitecore.Commerce.3.0.28/Deploy-Sitecore-Commerce.ps1 file. Sitecore Support advised that I modify the UserName and UserPassword values to that of a local user account with sufficient permissions to logon to SqlServer and perform the needed actions.
    Subsequently, I've discovered another way to address this issue.
    If you open the Windows Event Viewer and examine the Windows Logs/System log, you very well may find an error like this:
    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
         and APPID 
         to the user [Machine Name]\CSFndRuntimeUser SID (S-1-5-21-3907040123-2769532930-2580695905-1026)      from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable).      This security permission can be modified using the Component Services administrative tool.
    My remedy to this issue is as follows:
    1. Open %windir%\system32\compmgmt.msc /s
    2. Go to /Computer Management (Local)/System Tools/Local Users/Users/CSFndRuntimeUser
    3.  Right click, go to membership tab, add CSFndRuntimeUser to an appropriate group with sufficient permissions to perform the operation
  4. Error: Ensure/Sync default content paths for environment AdventureWorksAuthoring failed, please check Engine service logs for more info.
    For this error, you should also check the logs of the invoked Sitecore service for this exception:
    Exception Details: StackExchange.Redis.RedisServerException: ERR unknown command 'EVAL'
    Source Error: 
    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
    Stack Trace: 
    [RedisServerException: ERR unknown command 'EVAL']
       StackExchange.Redis.ConnectionMultiplexer.ExecuteSyncImpl(Message message, ResultProcessor`1 processor, ServerEndPoint server) in c:\TeamCity\buildAgent\work\3ae0647004edff78\StackExchange.Redis\StackExchange\Redis\ConnectionMultiplexer.cs:1713
       StackExchange.Redis.RedisBase.ExecuteSync(Message message, ResultProcessor`1 processor, ServerEndPoint server) in c:\TeamCity\buildAgent\work\3ae0647004edff78\StackExchange.Redis\StackExchange\Redis\RedisBase.cs:81
       StackExchange.Redis.RedisDatabase.ScriptEvaluate(String script, RedisKey[] keys, RedisValue[] values, CommandFlags flags) in c:\TeamCity\buildAgent\work\3ae0647004edff78\StackExchange.Redis\StackExchange\Redis\RedisDatabase.cs:871
       Microsoft.Web.Redis.<>c__DisplayClass4.b__3() in c:\TeamCity\buildAgent\work\e3a19c24ba052c76\src\Shared\StackExchangeClientConnection.cs:108
       Microsoft.Web.Redis.StackExchangeClientConnection.RetryForScriptNotFound(Func`1 redisOperation) in c:\TeamCity\buildAgent\work\e3a19c24ba052c76\src\Shared\StackExchangeClientConnection.cs:126
       Microsoft.Web.Redis.StackExchangeClientConnection.RetryLogic(Func`1 redisOperation) in c:\TeamCity\buildAgent\work\e3a19c24ba052c76\src\Shared\StackExchangeClientConnection.cs:150
       Microsoft.Web.Redis.StackExchangeClientConnection.Eval(String script, String[] keyArgs, Object[] valueArgs) in c:\TeamCity\buildAgent\work\e3a19c24ba052c76\src\Shared\StackExchangeClientConnection.cs:108
       Microsoft.Web.Redis.RedisConnectionWrapper.Set(ISessionStateItemCollection data, Int32 sessionTimeout) in c:\TeamCity\buildAgent\work\e3a19c24ba052c76\src\RedisSessionStateProvider\RedisConnectionWrapper.cs:128
       Microsoft.Web.Redis.RedisSessionStateProvider.SetAndReleaseItemExclusive(HttpContext context, String id, SessionStateStoreData item, Object lockId, Boolean newItem) in c:\TeamCity\buildAgent\work\e3a19c24ba052c76\src\RedisSessionStateProvider\RedisSessionStateProvider.cs:381
       System.Web.SessionState.SessionStateModule.OnReleaseState(Object source, EventArgs eventArgs) +1021
       System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92
       System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +165
    If this exception is present, it means that you need to install a version of Redis greater than 2.6, wherein the EVAL operation was introduced.
    Please note that no version of Redis is mentioned in Sitecore Experience Commerce Installation Guide for On-Premise Solutions manual, i.e. the SXC 9.2 installation manual.
  5. If all else fails and you need to start anew
    If you need to start the installation of SXC 9.2 anew, I've found this procedure to be very helpful in restoring the SXP 9.2 install to a working state:
    1. Restore Master_SingleServer.json from backup
    2. Edit the "Install-SitecoreConfiguration ..." command in the Deploy-Sitecore-Commerce.ps1 to: UnInstall-SitecoreConfiguration @params -Verbose *>&1 | Tee-Object "$PSScriptRoot\XC-Install.log"
    3. Run the Deploy-Sitecore-Commerce.ps1 again. This will uninstall most components installed by the SXC 9.2 installation
    4. Remove the modification made in step 2
    5. In an adminstrative PowerShell terminal, execute: Remove-LocalUser CSFndRuntimeUser
    6. Delete the following directory: C:/Users/CSFndRuntimeUser
    7. Restore the contents of C:\inetpub\wwwroot\[Sitecore Install Directory] from your SXP 9.2 backup*.
      *As a suggested practice, when installing any Sitecore version, it's always a good practice to backup successful installations previous to installing additional Sitecore packages, modules, etc.
      To quote Foghorn Leghorn: "Fortunately, I keep my feathers numbered for just such an emergency"
    8. Regenerate all SOLR indexes
    9. Rebuild all Link Databases



Sitecore 144
Commerce 100
Web Development 100
Sitecore Commerce 83
Sitecore Experience Commerce 9 64
Sitecore Experience Commerce 59
Content Management 55
eCommerce 48
B2B eCommerce 42
Sitecore Experience Platform 39
Sitecore Platinum Partner 39
Architecture 34
Insite 29
User Experience 26
Strategy 22
B2C eCommerce 21
B2B Commerce Blogs 21
commerceconnect 21
CloudCraze 20
SaaS (Software as a Service) 20
Cloud 17
Commerce Server 17
Salesforce B2B Commerce Cloud 16
Mobile 13
Search 13
Plugins 12
Analytics 12
Application Development 12
Digital Transformation 11
Sitecore Symposium 11
Helix 10
Social 8
Business Process 7
Authentication 7
5 Reasons 7
BI and Big Data 6
Data Visualization 6
Sitecore Presentation 6
Coveo 6
NET Development 5
Microsoft Azure 5
Automation 5
Front-End Development 4
SaaS (Software as a Service) 4
Digital Strategy 4
Brightcove 4
Press Release 4
Avalara Tax 3
Sitecore Experience Accelerator (SXA) 3
Sitecore Layouts 3
Video 3
Multi-site 3
Multi-lingual 3
Accessibility 3
Habitat 3
Vault 3
Identity 2
Managed Services 2
Cryptocurrency 2
Sitecore Forms 2
Sitecore Experience Commerce 9 Promotions 2
Uncategorized 2
Conversational Commerce 2
Sitecore SaaS 2
Security 2
Unit Testing 2
Headless Architecture 2
Sitecore Experience Awards 2
Google 1
Content Delivery Network 1
Configure Price Quote 1
Blockchain 1
Coupons 1
Sitecore Rss 1
Artificial Intelligence 1
Machine Learning 1
Okta 1
RFP Process 1
Flex Accelerator for Sitecore 1
Reviews 1
Page Labels 1