After speaking with my friend @kamsar, he pointed out the CORS origin on the Identity Server Instance needs an update.
The Identity Server doesn't allow logging in from just any url, for security reasons.
Open the file C:\inetpub\wwwroot\sc910.identityserver.dev.sc.local\Config\production\Sitecore.IdentityServer.Host.xml
Add a new AllowedCorsOriginsGroupN (...
As discussed on the #sif Sitecore Slack channel, when using vanilla SC WDP configs the SIF version does have a dependency on the installed SC version.
SIF 2.0.0 = SC 9.1
SIF 1.2.1 = SC 9.0.x
There are two ways to solve the problem outlined above.
1) Define SIF Version Explicitly
If installing SIF for the first time via PowershellGallery:
Below solution worked for me.
Close all active PowerShell sessions, delete all DO_NOT_TRUST* certificates from all certificate store and C:\certificates. Open “xconnect-createcert.json” and change json as below.
I had the same issue when I tried to install Sitecore 9 with MS SQL Server 2017. The Sitecore 9 has the MS SQL Server 2016 in the prerequisits. Unfortunatelly it looks like the newer versions are not supported.
Try to install the MS SQL Server 2016 and re-run the installation.
There is not currently such a command. I wish there was.
In general terms to uninstall, you will need to:
Remove the two xConnect windows services (with sc delete [servicename])
Remove the Sitecore and xConnect webroots
Remove the databases from SQL Server
If all you wish to do is overwrite an existing SIF-installed instance, removing the databases and re-...
Is this intentional?
This is intentional because Azure App Services require the Data folder (aptly named App_Data) to be located inside of the website root folder since App Services do not have file system access outside of the website root folder.
Instead of having two different configurations (one for on-prem and one for Azure PaaS) defaulting to the way ...
To understand how to validate all of the different parts of Sitecore, you first must understand what parts exist, why they exist, and how they work together. We'll begin with a short definition of terms.
In the world of Sitecore 9.1, there are three PRIMARY applications in play. One or more instances of Sitecore, 1 implementation ...
It's a small thing which I'm hoping to have fixed soon so that things are a little clearer, sorry this isn't as straight-forward as it should be!
Calling Register-SitecoreInstallExtension outside of a running install does nothing as there is no context for it to operate in. The function actually sets information in a dictionary when the install itself ...
You've created two certificates with precisely the same DNS name.
You can see in the verbose output that two certificates have been found as it lists two thumbprints. These values are then returned as an array which causes the error as the Signer parameter only expects a single certificate.
I suggest removing one or both certificates and trying again. I'...
The use of the "Contained Database User model" was introduced for very good reasons, and could be considered useful outside the realm of Sitecore.
You can read the article here and here published by Microsoft on it.
Traditional Login and User Model
The important principal is that both the login (in the master database) and the user (in the user database)...
@Dylan Young, did you solved the uninstall problem ?
Manual way to uninstall an instance of Siteocre 9 involves few steps, but it is not that bad. Assuming that your installation instance is prefixed with xp0Demo then:
Remove the two xConnect windows services (with sc.exe delete [servicename] in poweshell as administrator or in cmd.exe as ...
Right after post my question, realized that sqlcmd was not installed at the server - which is weird, because XP1 topology didn't require at all!
In my case, I had to download and install
Microsoft ODBC Driver 13 for SQL Server
Microsoft Command Line Utilities 13 for SQL Server
Once I got both installed, it was just a matter to re-run the XP0.
Just observed that in Solr 7.1.0 the folder structure is quite different than 6.6.2. Hence the power shell script is unable to find the required folders.
In my case the script is looking for basic_configs folder in \solr-7.1.0\server\solr\configsets, but the folder in no more exists here in Solr 7.1.0, seeme they moved the related files to to \solr-7.1.0\...
If you already know the thumbprint id (listed in the SIF console error), you can execute below PowerShell script to delete
Get-ChildItem Cert:\LocalMachine\Root\<<thumbprint>> | Remove-Item
If you want to list of installed certificate for the location, you can execute below script to get that list.
The source of the issue is actually due to the License as hinted by the entry in the EventLogs.
The Sitecore license being used is fine for our 8.0 implementation and even worked without issue installing 9.0.0. However Sitecore support informed us that the License we are using was outdated, even though still valid.
Contact Sitecore Support and ask them to ...
Differently from XP1, the XP0 topology has a JSON file specifically for create the certificate - xconnect-createcert.json
After creating the certificate using xconnect-createcert.json, I have tried provisioning the XConnect-Collection as I was doing and the error went away.
Now, I wonder what am I missing while generating my certificates manually... well ...
You are missing the SQLServer module.
Either run the prerequisites.json file which will install that and any missing prerequisites or:
Install-Module -Name SQLServer if you are just missing the SQL server module.
The error points to a lock on the IIS configuration. However, after some research, I came across to the solution which I share here hoping it will save someone else's time.
The reason for the error is that ASP.NET, one of the prerequisites, was not installed. The interesting thing is that Windows 10 doesn't show the ASP.NET feature on its "Windows Features" ...
Please make sure you have URL Rewrite IIS module installed? It is a prerequisite for Sitecore 9.
Download the IIS module - https://www.iis.net/downloads/microsoft/url-rewrite
Solr 6.6.2 Microsoft
PowerShell 5.1 or later (Included in Windows 10)
The solution was changing the "bitness" of my PowerShell.exe. Somehow, and I have a guess how, I was running 32 bit Powershell instead of 64 bit Powershell on my 64 bit Azure VM. Once I started the 64 bit version of Powershell, all was fine.
The (correct) 64 bit was located at C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
My guess on how I ...
It sounds like you still have a database or maybe a user left over.
How did you remove the failed installs? If you are running from the example script in the download comment out and in the Install-SitecoreConfiguration and Uninstall-SitecoreConfiguration lines and use that to run the uninstall. That should remove everything for you.
If you used a script to install it, the script requires you to specify a JRE version. If that version does not match the version installed, it acts this way.
If you use Jeremy Davis' easy solr script, you have to specify the version as a variable
$JREVersion = "1.8.0_201"
If you look on your hard drive, in program files look for the JRE version. Make sure ...
Yes, it is possible.
First, you must actually have a new license.
Secondly, make sure you replace the expired license file(s) on your Sitecore instance.
If you are using Sitecore 8.x the old file is under ./Data.
If you are using Sitecore 9.0.x, then look at:
If you are using Sitecore 9.1, then look at:
The "secret" is in the Installation Guide, but you have to jump ahead to Section 5.1 and 5.2. When I then created this PowerShell script:
$prefix = "xp0"
$PSScriptRoot = "D:\downloads\sitecore\sif"
$XConnectCollectionService = "$prefix.xconnect"
$sitecoreSiteName = "$prefix.sc"
$SolrUrl = "https://localhost:8983/solr"
$SolrRoot = "D:\solr\...
I have successfully installed Sitecore 9 with MS SQL Sever 2017 Express. I had encountered the same error and the trick is instead of using $SqlServer="localhost" in the installation script, change it to $SqlServer="localhost\SQLExpress". If you are indeed using the Express version, doing so should avoid the above issue!
The first thing that you need to start with gathering all information about what should be uninstalled. In an easy way you can select a website to uninstall:
$selectedWebSite = (Get-WebSite | Out-GridView -Title "Please select website to uninstall" -OutputMode Single )
Base on this you have information about Website and App Pool to remove, you also have a ...
Installation Guide has the answers, but you have to skip ahead to Section 5.1 and 5.2. Section 5.2 has an example script to use
You can download the guide here:
Section 5.1 has details and Section 5.2 has PowerShell script that has this ...
This error appear because you don't have the right json configuration files
You need to get entire package for xp0
This package contains 3 zip files: (you already use : Sitecore 9.0.1 rev. 171219 (OnPrem)_xp0xconnect.scwdp.zip and ...
I would recommend installing already Sitecore 9 Update 1 as you have Solr 6.6.2 installed. For Sitecore 9 Initial Release (that you are trying to install) Solr 6.6.1 is supported. Take a look here -> https://kb.sitecore.net/articles/227897.
I think your biggest problem is that you have Solr on different machine than Sitecore. I haven't tried that myself by ...