Just in case you are facing the certificate error while installing Sitecore 9.0 update 2 with SIF 1.2.1 as step CreateSignedCert : NewSignedCertificate, as below:
Install-SitecoreConfiguration : Cannot process argument transformation on parameter 'Signer'. Cannot convert the "System.Object" value of type "System.Object" to type "System.Security.Cryptography.X509Certificates.X509Certificate2".
The issue is coming from having the certificate already in a system, so you might manually delete that those from Microsoft Management Console (mmc.exe from Windows start menu).
In my case, I had several certificates named
DO_NOT_TRUST_SitecoreRootCert installed under
Certificates - Current User - Trusted Root Certification Auhorities- Certificates, deleting them helped progress.
Hope this helps!
When creating websites with Sitecore it is always nice to a have a nice and shiny 404-page that complies with the website styles and is content editable. Which will not work in all the cases, unfortunately. If the request falls out of site context - user won't get that nice and shiny page. So let's see what we can do in Helix, as it assumes multisite by design. The code below is written on top of Habitat, but that should not make a big difference.
Since this functionality is website agnostic and relates to Project layer, we will be using Project.Common.Website. Here is the configuration within
<processor patch:before="processor[@type='Sitecore.Pipelines.HttpRequest.LayoutResolver, Sitecore.Kernel']"
patch:after="processor[@type='Sitecore.Pipelines.HttpRequest.ItemResolver, Sitecore.Kernel']" />
And the processor
public class HandleRequestError : HttpRequestProcessor
public override void Process(HttpRequestArgs args)
if (Context.Item != null || Context.Site == null)
string filePath = HttpContext.Current.Server.MapPath(args.Url.FilePath);
if (Context.Database != null)
// if we are in a context of a specific site - serve content-editable 404
Context.Item = Context.Database.GetItem(Context.Site.StartPath + "/404");
// return 404 HTTP status code in either cases, to be picked up further ahead
HttpContext.Current.Response.TrySkipIisCustomErrors = true;
HttpContext.Current.Response.StatusCode = (int)HttpStatusCode.NotFound;
private bool IsValidItem()
if (Context.Item == null || Context.Item.Versions.Count == 0) return false;
if (Context.Item.Visualization.Layout == null) return false;
}So briefly, if we have website resolved - we serve its customized content-editable /404 page item (each of the sites has this page under the same root-relative path).