4

I know this is a bit late, but I ran into this today and found a resolution. I found the error details in the event viewer under Applications and Services Logs\Microsoft\Windows\WebDeploy\Errors. I had looked before under Applications and Services Logs\Microsoft Web Deploy which was empty. In my case, the issue was the database server name. It needs to ...


3

Got the fix Service "Application Host Helper Service" was not running


3

There is a config which contains events executed during deploy. Search for Sitecore.JavaScriptServices.AppServices.config under ".\App_Config\Sitecore\JavaScriptServices" folder. This file contains "import", "create.item", "update.item" etc. Based on your requirement you can patch respective pipeline. <import> <processor type="Sitecore....


2

You are receiving this error, because "localhost" is not the name that you put on your certificate. Please make sure that the solr certificate has the subject name and the DNS name the same as you are using on your browser: When I try to access from Powershell, I'm able to do so: But if I try to use 'localhost', I get the following error: Also, ensure ...


2

Run Below Script in power shell, This will remove sitecore databases and users import-module sqlps $DBListQuery = "select * from sys.databases where Name like '" + $Prefix + "_%';" $DBList = invoke-sqlcmd -ServerInstance "**SERVERNAME**" -U "sa" -P "**PASSWORD**" -Query $DBListQuery ForEach($DB in $DBList) { Write-host -foregroundcolor Green "Deleting ...


1

I've found the simplest method for resolving issues with starting the service can be found by reviewing Event Viewer on Windows. Event Viewer Review Windows Logs > Application Find records with a Source of nssm Select the records with a Level of Information This lets you see the command NSSM is attempting to execute. In the screenshot above, the key ...


1

Look for the trailing '/' in SolrUrl in your XP0-SingleDeveloper.ps1. An additional '/' is the likely culprit.


1

There are different versions of the Import-PfxCertificate and the Export-PfxCertificate cmdlets. The versions that come with Windows Server 2016 and Windows 10 1703 and earlier do not support importing a PFX generated using the AES256_SHA256 cryptographic algorithm and result in the error that you experienced. This issue doesn't occur with the version of ...


1

From the screenshot, it seems like your solr is listening on port number 8983, While your sitecore instance is hitting on port number 8984.


1

Most of the time I see this error, the issue is with the license. The license needs to be: Up to date Valid Xml Includes the key xDB.Base. XDB.Base signifies that the license is valid for xDB.


1

Short answer - Yes! If you've generated a new Root Certificate, you need to create a new certificate for xConnect_client in-order to maintain the Signer relationship with the Root Certificate. PS: Also, Don't forget to add the App Pool user permission on certificate and update the latest Thumbprint of the new certificate under AppSettings.config (of ...


1

I had this an the issue was either installing the wrong version of Sitecore Powershell Extensions or the wrong version of SXA. Make sure you get Sitecore Powershell Extensions 5.0 for Sitecore 9.2. There is a link on the SXA download page.


1

Update Be sure to disable Capture HTTPS CONNECTs and Decript HTTPS traffic. I ran into an issue where my certificate was invalid and came back as DO_NOT_TRUST_Fiddler instead of the Sitecore certificate. This caused a thumbprint mismatch when the service was started/xConnect was requested. I was able to find a more elegant, complete solution to my previous ...


Only top voted, non community-wiki answers of a minimum length are eligible