"Error 1316. The specified account already exists." when installing for VS2019 with Chocolatey

I have the following (custom) Chocolatey script:

Install-ChocolateyPackage 'ncrunch2019' 'msi' '/quiet /norestart' '\\some\network\path\to\NCrunch_VS2019_3.25.0.3.msi'

It fails with error 1316, and the MSI log contains the following:

MSI (s) (18:44) [15:29:53:779]: SECREPAIR: Error determining package source type
MSI (s) (18:44) [15:29:53:779]: SECUREREPAIR: SecureRepair Failed. Error code: 524DC4857F0
MSI (s) (18:44) [15:29:53:779]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (18:44) [15:29:53:779]: Product: NCrunch for Visual Studio 2019 -- Error 1316. The specified account already exists.

The same file installs just fine when it's executed manually. I'm not really sure what using Chocolatey changes though.

Some additional info:

• 
  
• I use the same script for the VS 2017 version, and it works fine
  
• I already have NCrunch for VS 2017 installed
  

I can send the full log file if it helps.

Thanks for sharing this issue.

Unfortunately this problem is outside the boundaries of what we are able to provide support for. We ourselves don't maintain support for chocolatey installers for NCrunch, so to troubleshoot a problem like this we would need to introduce and maintain an entirely new installation use beyond those we currently support. I'm sorry but we simply don't have the capacity to do that.

That's a custom chocolatey script though, so I don't expect you to maintain it. I just shared the issue in case it would ring a bell.

LucasT wrote:That's a custom chocolatey script though, so I don't expect you to maintain it. I just shared the issue in case it would ring a bell.

Sorry no ideas here :( Working with MSIs tends to be a bit of a minefield of problems like this.

Did you have the initial NCrunch for visual studio 2019 version installed? If so would you mind checking to uninstall all the NCrunch for Visual Studio 2019 versions that might be present. The original installer had an upgrade issue. This is the only thing I can think of that could be affected by this.

Thanks for the suggestion, but that was the first time I was installing the VS 2019 version.
I'll try to figure it out if the next release still has this issue.

FWIW v3.27.0.3 fixed this issue, thanks!

I guess it's related to the following changelog item:

Added support for quiet installations with the NCrunch for Visual Studio 2019 installer

Glad it helped!