Sitecore 9.2 Installation Errors using SIA
If you get any of these errors, ensure to cross-check your settings as per my Sitecore 9.2 installation using SIA blog
Cannot find path 'C:\Solr-7.5.0' because it does not exist:
Unable to parse [variable('XConnectSolr_Core.Root')] - Exception calling "Evaluate" with "2" argument(s): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Unable to parse [joinpath(variable('XConnectSolr_Solr.Server'), variable('XConnectSolr_Xdb.Name'))] - Exception calling "Evaluate" with "2" argument(s): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Unable to parse [joinpath(variable('XConnectSolr_Solr.FullRoot'), 'server', 'solr')] - Exception calling "Evaluate" with "2" argument(s): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Unable to parse [resolvepath(parameter('XConnectSolr_SolrRoot'))] - Exception calling "InvokeWithContext" with "2" argument(s): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Cannot find path 'C:\Solr-7.5.0' because it does not exist.""""
Solution: Ensure the solr-7.5.0 folder exists under C:\ in your machine
Installation error: Failed to start service 'Sitecore Marketing Automation Engine
Solution: Run Powershell scripts below to move certificates as stated in this blog - https://community.sitecore.net/developers/f/5/t/10020
Get-Childitem cert:\LocalMachine\root -Recurse | Where-Object {$_.Issuer -ne $_.Subject}
Get-Childitem cert:\LocalMachine\root -Recurse | Where-Object {$_.Issuer -ne $_.Subject} | Move-Item -Destination Cert:\LocalMachine\CA
Login failed for user 'sa'
Unable to connect to target server '(local)'. Please verify the connection information such as the server name, login credentials, and firewall rules for the target server.
Login failed for user 'sa'.
Solution: Ensure the user id and password you use to log into SQL Server management studio is correct and same as what is provided here in the setup
Failed to start service 'Sitecore XConnect Search Indexer
Failed to start service 'Sitecore XConnect Search Indexer - <sitecore instance>xconnect.dev.local-IndexWorker (<sitecore instance>xconnect.dev.local-IndexWorker)'.
Solution: Check if the Sitecore license file is valid and is unexpired by searching for expiration tag within the file
The remote name could not be resolved: 'solr750'
Exception calling "GetResponse" with "0" argument(s): "The remote name could not be resolved: 'solr750'"
At C:\projects\habitat\install-xp0.ps1:72 char:2
+ $SolrResponse = $SolrRequest.GetResponse()
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : WebException
Solution: Ensure to setup solr using this script and ensure the files are downloaded as well as running as a service
Cannot find path 'C:\Solr-7.5.0' because it does not exist:
Unable to parse [variable('XConnectSolr_Core.Root')] - Exception calling "Evaluate" with "2" argument(s): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Unable to parse [joinpath(variable('XConnectSolr_Solr.Server'), variable('XConnectSolr_Xdb.Name'))] - Exception calling "Evaluate" with "2" argument(s): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Unable to parse [joinpath(variable('XConnectSolr_Solr.FullRoot'), 'server', 'solr')] - Exception calling "Evaluate" with "2" argument(s): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Unable to parse [resolvepath(parameter('XConnectSolr_SolrRoot'))] - Exception calling "InvokeWithContext" with "2" argument(s): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Cannot find path 'C:\Solr-7.5.0' because it does not exist.""""
Solution: Ensure the solr-7.5.0 folder exists under C:\ in your machine
Installation error: Failed to start service 'Sitecore Marketing Automation Engine
Solution: Run Powershell scripts below to move certificates as stated in this blog - https://community.sitecore.net/developers/f/5/t/10020
Get-Childitem cert:\LocalMachine\root -Recurse | Where-Object {$_.Issuer -ne $_.Subject}
Get-Childitem cert:\LocalMachine\root -Recurse | Where-Object {$_.Issuer -ne $_.Subject} | Move-Item -Destination Cert:\LocalMachine\CA
Login failed for user 'sa'
Unable to connect to target server '(local)'. Please verify the connection information such as the server name, login credentials, and firewall rules for the target server.
Login failed for user 'sa'.
Solution: Ensure the user id and password you use to log into SQL Server management studio is correct and same as what is provided here in the setup
Failed to start service 'Sitecore XConnect Search Indexer
Failed to start service 'Sitecore XConnect Search Indexer - <sitecore instance>xconnect.dev.local-IndexWorker (<sitecore instance>xconnect.dev.local-IndexWorker)'.
Solution: Check if the Sitecore license file is valid and is unexpired by searching for expiration tag within the file
The remote name could not be resolved: 'solr750'
Exception calling "GetResponse" with "0" argument(s): "The remote name could not be resolved: 'solr750'"
At C:\projects\habitat\install-xp0.ps1:72 char:2
+ $SolrResponse = $SolrRequest.GetResponse()
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : WebException
Solution: Ensure to setup solr using this script and ensure the files are downloaded as well as running as a service
In case if you get the below error, then install nodejs.
The term 'npm' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
Solution: Install nodejs, add nodejs path to user variables under environment variables.
Comments
Post a Comment