9

I had a strange problem when I was installing Sitecore 9.1 and here is the solution.

The problem occurred when running the SIF command Install-SitecoreConfiguration @xconnectParams from the SIF section # Deploy XConnect instance. It failed with this error:

Install-SitecoreConfiguration : Cannot retrieve the dynamic parameters for the cmdlet. Retrieving the COM class factory for component with CLSID {688EEEE5-6A7E-422F-B2E1-6AF00DC944A6} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)). At line:1 char:1 + Install-SitecoreConfiguration @xconnectParams -verbose *>&1 | Tee-Ob ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Install-SitecoreConfiguration

  • Hi Ariel, and welcome to Sitecore Stack Exchange :-) This is a Q&A database. We love your contribution to the site - but could you please arrange it as a Question and fill in your solution as an answer, please? When done, self-mark your answer. That way everyone (and the search engines) knows what's what. – Mark Cassidy Sep 14 '18 at 13:41
  • Are you really using Sitecore 9.1? This was not released so far? Did you mean Sitecore 9.0.1? Please check – Peter Procházka Sep 14 '18 at 18:34
8

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 started the 32 bit instead was I searched for Powershell.exe and did not notice that it was starting from the 32 bit folder C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe

4

There is an easy way, to protect Powershell scripts to run under wrong bit versions.

If(![Environment]::Is64BitProcess) 
{
    Write-Host "Please run 64-bit PowerShell" -foregroundcolor "yellow"
    return
}
1

One side note for this... If you are running PowerShell from within VS so you have admin privileges in PowerShell (using VS admin privileges) no matter what path you are pointing to, it will always open the 32bit even if the (x86) is not in the menu bar. You need to open PowerShell 64 bit directly with Admin privileges.

  • I've been successfully installed Sc 9.1 for several times. But when I add PowerShell shortcut into my VS and almost used it since, everything went strange when installing sitecore lol Thanks bro, you're my hero for saving me hours – Dika Purnasucita Oct 24 at 6:57

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.