Problem with Minor MSI Upgrades

[DarwinCSIWindowscom]

This was experienced with the package sql2012.nativeclient

When installing on server 2012 I get the following error "Microsoft SQL 2012 Native Client: A network error occured while attempting to read from the file: c:\users\administrator\appdata\local\temp\chocolatey\SQL2012.NativeClient\sqlncli.msi"

When I visit that folder the MSI appears to be called "SQL2012.NativeClientInstall.msi"

Renaming the file appears to be a standard operation of the Chocolatey framework as they are all like this.

This package is being installed as a dependency for sql2012.powershell.

This machine already has the SQL native client via a previous install of the SQL engine and SQL management studio.

So at the MSI level, here is what is happening:

When MSI does an official MSI Minor upgrade to an existing product, it finds the same product code installed on the machine. From the previous run it can tell the original file name that is registered in the MSI repository.

If the previous version was installed as an "MSI managed package", it then goes back to the new location the current version is being installed from and looks for the previous original name in that location.

It would take a long time to explain - but this is a way of preventing non-admin users from gaining MSI admin rights by upgrading an existing MSI on the system that was installed by an admin.

To eliminate these types of conflicts, you would want to not engage in a practice of renaming the MSI files.

A second, and even better thing to do, would be to have the chocolatey framework intelligently detect whenever an MSI is already installed and check versions. From there your options would be to [a] do the correct MSI command line to accomplish a minor upgrade (always uses "msiexec /fvomus .msi") [many packages aren't written correctly to accomplish a minor upgrade, [b] or better uninstall the previous version [works for imperfect MSIs and for major upgrades], [c] or at the chocolatey level, just mark the package as installed if it is the SAME or older version (doing this when the new MSI is truly new is probably not be what people expect of an installation framework that is supposed to automatically do everything correctly)

[DarwinCSIWindowscom]

Is there already a way for me to force a chocolatey package to appear installed without installing it?

I'm thinking about situations like the above where I already know the pre-requisite is installed, it's just not installed by chocolatey.

Something like:
choco install abc -onlyregisterasinstalled

[ferventcoder]

--skippowershell.

On Sunday, February 1, 2015, DarwinCSIWindowscom [email protected]
wrote:

Is there already a way for me to force a chocolatey package to appear
installed without installing it?

I'm thinking about situations like the above where I already know the
pre-requisite is installed, it's just not installed by chocolatey.

Something like:
choco install abc -onlyregisterasinstalled

—
Reply to this email directly or view it on GitHub
#49 (comment).

Rob
"Be passionate in all you do"

http://devlicio.us/blogs/rob_reynolds
http://ferventcoder.com
http://twitter.com/ferventcoder

[ferventcoder]

Also --ignoredependencies

On Sunday, February 1, 2015, Rob Reynolds [email protected] wrote:

-skippowershell.

On Sunday, February 1, 2015, DarwinCSIWindowscom <[email protected]
javascript:_e(%7B%7D,'cvml','[email protected]');> wrote:

Is there already a way for me to force a chocolatey package to appear
installed without installing it?

I'm thinking about situations like the above where I already know the
pre-requisite is installed, it's just not installed by chocolatey.

Something like:
choco install abc -onlyregisterasinstalled

—
Reply to this email directly or view it on GitHub
#49 (comment).

Rob
"Be passionate in all you do"

http://devlicio.us/blogs/rob_reynolds
http://ferventcoder.com
http://twitter.com/ferventcoder

Rob
"Be passionate in all you do"

http://devlicio.us/blogs/rob_reynolds
http://ferventcoder.com
http://twitter.com/ferventcoder

[DarwinCSIWindowscom]

Could you please show a complete command line?

I tried -skippowershell and --skippowershell and --skip-powershell and they all report "unknown option" and then "command install failed".

I tried adding "-o" and "--override" and still get the same result.

Latest version of chocolately on a fresh Server 2012 build.

Thanks for any help!

[gep13]

Latest version of chocolately on a fresh Server 2012 build.

When you say latest version, can you confirm exactly what version?

We have a beta package of Chocolatey, which is version 0.9.9-beta-20150201, which is where the above command switches will work. I suspect you might have version 0.9.8.32 which is the latest non beta version, where these command switches don't exist.

[DarwinCSIWindowscom]

You are correct - how do I update to the beta - doesn't seem to be a pre-release of the regular package, but not sure if I'm checking correctly.

Also interested in the oneliner to install the beta on a bare machine if there is one.

Thanks!
D.

[gep13]

If you already have choco installed use:

choco install Chocolatey -pre

For a fresh machine, there is a url you can use, but I am AFK. @ferventcoder, you around?

Sent from my Windows Phone

---

From: DarwinCSIWindowscommailto:[email protected]
Sent: ‎02/‎02/‎2015 16:54
To: chocolatey/chocomailto:[email protected]
Cc: Gary Ewan Parkmailto:[email protected]
Subject: Re: [choco] Problem with Minor MSI Upgrades (#49)

You are correct - how do I update to the beta - doesn't seem to be a pre-release of the regular package, but not sure if I'm checking correctly.

Also interested in the oneliner to install the beta on a bare machine if there is one.

Thanks!
D.

---

Reply to this email directly or view it on GitHub:
#49 (comment)

[gep13]

@DarwinCSIWindowscom on a fresh machine, rather than doing this:

@powershell -NoProfile -ExecutionPolicy unrestricted -Command "iex ((new-object net.webclient).DownloadString('https://chocolatey.org/install.ps1'))" && SET PATH=%PATH%;%ALLUSERSPROFILE%\chocolatey\bin

use this:

@powershell -NoProfile -ExecutionPolicy unrestricted -Command "iex ((new-object net.webclient).DownloadString('https://chocolatey.org/InstallAbsoluteLatest.ps1'))" && SET PATH=%PATH%;%ALLUSERSPROFILE%\chocolatey\bin

instead. That should get you the latest pre-release version.

[ferventcoder]

:)

[DarwinCSIWindowscom]

I am getting the error that there is no longer a "sources" command - do you want me to submit an issue somewhere?

Also it is prompting for confirmation for each package - is there a way to globally disable that so that it behaves like the prior version?

I can see in the command lines that there is a confirmation prompt, but would prefer not to update all my scripts with the confirmation prompt for every package.

Thanks,
D.

[ferventcoder]

@DarwinCSIWindowscom Please read the documentation. https://github.com/chocolatey/choco/wiki/ReleaseNotes

[ferventcoder]

I highly recommend you get familiar with choco -? and choco command -?

[ferventcoder]

For your global insecure confirmation option - #52

[pauby]

There doesn't look like they're is anything too do in this issue so I'm going to go ahead and close it. We can always reopen it again later, if necessary.