[wix-users] Issue installing via TFS agent

Tyler Gustafson tgustafson at solacom.com
Fri Oct 14 08:34:10 PDT 2016

Based on the original information it sounds like this isn't the case since Andrew manages to get the program on there the first time using that account but maybe it's missing some privilege specific to updating. Andrew are you able to reproduce the problem when you log into the box as the service user instead of yourself?

I don't think I have much to contribute here but I will mention an issue we ran into with our deployment process in case it happens to help.
At the time our environment was TFS and InstallShield and we had an issue because InstallShield was grabbing build artifacts from the build environment's TFS workspace. I don't remember the terminology anymore but all source control files on the build workspace were write protected (I think it was called a server workspace).

InstallShield was grabbing this web.config file which was still write protected and then when it got to its step to set up IIS it was trying to modify the web.config file and choking there with a similar error message. I'll admit I haven't done any googling on your error message, but the mention of IIS reminded me of this and figured it might spark an idea.


-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of John Cooper
Sent: October-14-16 10:34 AM
To: WiX Toolset Users Mailing List
Subject: Re: [wix-users] Issue installing via TFS agent

I don't know about your location, but our CS department generally specifically removes the ability to install from the build service account.  This is in accordance with Microsoft guidance as service accounts generally don't have the rights to install.  The solution to this problem is to use a tool like Release Management or Octopus.

John Merryweather Cooper
Senior Software Engineer -- Integration Development Group -- Enterprise Notification Service Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Office:  913-341-3434x431050 JoCooper at jackhenry.com

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Andrew Moser
Sent: Friday, October 14, 2016 8:48 AM
To: wix-users at lists.wixtoolset.org
Subject: [wix-users] Issue installing via TFS agent

The e-mail below is from an external source.  Please do not open attachments or click links from an unknown or suspicious origin.

Environment Details: Installation package is created via a TFS continuous integration build process (using Wix 3.10.3) that has an agent on the deployment test server (A TFS user is running as a service on the release
box) where I am having the issue below. Package is downloaded and installed via the release agent of TFS using the powershell function (NOT powershell on targeted machine) with this script, which runs the installation in admin mode if not already in admin mode.

If (-NOT ([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole]
    Echo "This script needs to be run As Admin"
    Start-Process powershell -ArgumentList '-noprofile -file [ps1file]' -verb RunAs
    Echo "Running as Admin"
    MSIEXEC /i "[PathToMSI]" /qn /L*v "[PathToLog]"
    Echo "Script complete"

First off I can install this product without issue the first time on the server in question, it is the updates that are producing strange behavior.
The agent automated update produces this error code.

MSI (s) (34!1C) [16:27:41:979]: Doing action: StartIIS7ConfigTransaction MSI (s) (34!1C) [16:27:41:979]: Product: MyProduct -- Error 26031.
Failed to schedule transaction for changes to IIS.  (-2147418113

MSI (s) (34:48) [16:27:41:994]: Note: 1: 2265 2:  3: -2147287035 MSI (s) (34:48) [16:27:41:994]: Machine policy value 'DisableRollback' is 0 MSI (s) (34:48) [16:27:41:994]: Note: 1: 1402 2:
3: 2
MSI (s) (34:48) [16:27:41:994]: Note: 1: 1402 2:
3: 2
MSI (s) (34:48) [16:27:41:994]: No System Restore sequence number for this installation.
MSI (s) (34:48) [16:27:41:994]: Unlocking Server MSI (s) (34:48) [16:27:42:010]: Note: 1: 1708 MSI (s) (34:48) [16:27:42:010]: Product: MyProduct -- Installation failed.

MSI (s) (34:48) [16:27:42:010]: Windows Installer installed the product. Product Name: MyProduct. Product Version: Product
Language: 1033. Manufacturer: Me. Installation success or error
status: 1603.

When I log into the server myself and run the save powershell script the installation installs without issue, the TFSservice user that is installing the application per the TFS release agent have the same privileges.  Is there something in the IISConfig steps that requires some special permission or action that only a logged in user can grant or that is prevented when run from a service?

I have scoured this and other forums looking for any indication of how to fix it, but have yet to turn up anything related to this specific error code/text. I have exhausted all options I could think of over the last few days. Any help would be appreciated.

Andrew Moser
malquijelkah at gmail.com

WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.

WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/
Scanned by Total Defense Email Cloud Security http://cloud.totaldefense.com

More information about the wix-users mailing list