I recently discovered that my companies software cannot be deployed via GPO. I want our software to be available for GPO deployment but need to figure out what is wrong with our MSI. I can install our software silently /qn with absolutely no problem at all. When I deploy via GPO, the target system log file provides an error of 1605. The GPO is per machine. The MSI is placed on a network share and I confirmed that the target system can access and install from that share. I have tried using the MSI and also extracted the contents (msiexec /a) and attempted from the extracted MSI as well. Using Orca and viewing the Properties table, we have: ALLUSERS = 1 and we do NOT have a MSINSTALLPERUSER entry. The installation GUI does have a couple of prompts requiring user input to continue, with one being the license agreement. Because I can install silently with no user interaction, I'm assuming that that this isn't the issue. Can anyone provide any suggestions on what I can try next or what some possible culprits might be? I can't even seem to find documentation on how to build your MSI to ensure GPO compatibility. Any help would be so very much appreciated.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
1605 is a generic error, the cause could be any one of a hundred.

What does a verbose log tell you? You'll need to use the 'Enable MSI Logging' policy to get a log but that's simple enough. Remember to turn it off when you're done, if you're not using virtual machines to test with (!)
Answered 01/20/2012 by: VBScab
Red Belt

Please log in to comment
0
I did do that and have been staring at it but nothing is jumping out at me. Not sure how to attach it here so I'll copy and paste what I think might be relevant? I'm seeing user exit and wondering if it has something to do with the license prompt - perhaps defaulting to cancel? Thank you so very much for any help.

Info 2898. For WixUI_Font_Title textstyle, the system created a 'Tahoma' font, in 0 character set, of 14 pixels height.
Action 15:01:34: LicenseAgreementDlg. Dialog created
Action 15:02:26: CancelDlg. Dialog created
Action ended 15:02:27: WelcomeDlg. Return value 2.
MSI (c) (50:6C) [15:02:27:884]: Doing action: UserExit
Action 15:02:27: UserExit.
Action start 15:02:27: UserExit.
Action 15:02:27: UserExit. Dialog created
Action ended 15:02:30: UserExit. Return value 2.
Action ended 15:02:30: INSTALL. Return value 2.
Property(C): UpgradeCode = {C9213280-0D15-48CA-8014-527B4A6973C2}
Property(C): DPI = #96
Property(C): NETFRAMEWORK35 = #1
Property(C): WINAMPFOLDER = C:\Program Files (x86)\Winamp\
Property(C): METRICSALLOWED = 1
Property(C): OLYMPIA = C:\Program Files (x86)\Plantronics\PlantronicsURE\
Property(C): OLYMPIA_DATA = C:\ProgramData\Plantronics\PlantronicsURE\
Property(C): TARGETDIR = C:\
Property(C): SDK_FOLDER = C:\Program Files (x86)\Plantronics\PlantronicsURE\
Property(C): ShortcutFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Plantronics\
Property(C): da = C:\Program Files (x86)\Plantronics\PlantronicsURE\da\
Property(C): de = C:\Program Files (x86)\Plantronics\PlantronicsURE\de\
Property(C): enGB = C:\Program Files (x86)\Plantronics\PlantronicsURE\en-GB\
Property(C): es = C:\Program Files (x86)\Plantronics\PlantronicsURE\es\
Property(C): esES = C:\Program Files (x86)\Plantronics\PlantronicsURE\es-ES\
Property(C): esMX = C:\Program Files (x86)\Plantronics\PlantronicsURE\es-MX\
Property(C): fi = C:\Program Files (x86)\Plantronics\PlantronicsURE\fi\
Property(C): frCA = C:\Program Files (x86)\Plantronics\PlantronicsURE\fr-CA\
Property(C): fr = C:\Program Files (x86)\Plantronics\PlantronicsURE\fr\
Property(C): it = C:\Program Files (x86)\Plantronics\PlantronicsURE\it\
Property(C): ja = C:\Program Files (x86)\Plantronics\PlantronicsURE\ja\
Property(C): ko = C:\Program Files (x86)\Plantronics\PlantronicsURE\ko\
Property(C): nl = C:\Program Files (x86)\Plantronics\PlantronicsURE\nl\
Property(C): no = C:\Program Files (x86)\Plantronics\PlantronicsURE\no\
Property(C): pt = C:\Program Files (x86)\Plantronics\PlantronicsURE\pt\
Property(C): ptBR = C:\Program Files (x86)\Plantronics\PlantronicsURE\pt-BR\
Property(C): ptPT = C:\Program Files (x86)\Plantronics\PlantronicsURE\pt-PT\
Property(C): sv = C:\Program Files (x86)\Plantronics\PlantronicsURE\sv\
Property(C): tr = C:\Program Files (x86)\Plantronics\PlantronicsURE\tr\
Property(C): zhCN = C:\Program Files (x86)\Plantronics\PlantronicsURE\zh-CN\
Property(C): zhTW = C:\Program Files (x86)\Plantronics\PlantronicsURE\zh-TW\
Property(C): Plugins = C:\Program Files (x86)\Winamp\Plugins\
Property(C): WixUIRMOption = UseRM
Property(C): ALLUSERS = 1
Property(C): WixUI_Dialog = WixUI_Dialog_Small
Property(C): WixUI_Banner = WixUI_Banner_Small
Property(C): Plantronics = C:\Program Files (x86)\Plantronics\
Property(C): ProgramFilesFolder = C:\Program Files (x86)\
Property(C): ProgramMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\
Property(C): CompanyFolder = C:\ProgramData\Plantronics\
Property(C): CommonAppDataFolder = C:\ProgramData\
Property(C): SourceDir = \\pltbsnadc01\Deployment\01182012\extracted\
Property(C): Manufacturer = Plantronics, Inc.
Property(C): ProductCode = {92C1B9C1-367D-4227-95D4-660412AFFD0D}
Property(C): ProductLanguage = 1033
Property(C): ProductName = Plantronics Spokes Software
Property(C): ProductVersion = 2.5.50537.0
Property(C): WIXUI_INSTALLDIR = OLYMPIA
Property(C): ARPPRODUCTICON = Sparta.ico
Property(C): ARPHELPLINK = http://www.plantronics.com
Property(C): ARPCONTACT = Plantronics, Inc.
Property(C): DefaultUIFont = WixUI_Font_Normal
Property(C): WixUI_Mode = Mondo
Property(C): WixUI_InstallMode = InstallCustom
Property(C): ErrorDialog = ErrorDlg
Property(C): SecureCustomProperties = NETFRAMEWORK35;NEWPRODUCTFOUND;OLDPRODUCTFOUND
Property(C): OLDPRODUCTFOUND = {04F40296-1509-4DD2-92FC-261BDC825D76}
Property(C): FLEXNET.9FC896E6_8DD6_4BFD_A02C_189B1B87F512 = C:\ProgramData\FLEXnet\
Property(C): CONNECT.9FC896E6_8DD6_4BFD_A02C_189B1B87F512 = C:\ProgramData\FLEXnet\Connect\
Property(C): CommonFilesFolder = C:\Program Files (x86)\Common Files\
Property(C): MACROVISION.9FC896E6_8DD6_4BFD_A02C_189B1B87F512 = C:\ProgramData\Macrovision\
Property(C): FLEXNET_CONNECT.9FC896E6_8DD6_4BFD_A02C_189B1B87F512 = C:\ProgramData\Macrovision\FLEXnet Connect\
Property(C): FNC11DIR.9FC896E6_8DD6_4BFD_A02C_189B1B87F512 = C:\ProgramData\Macrovision\FLEXnet Connect\11\
Property(C): FNC61DIR.9FC896E6_8DD6_4BFD_A02C_189B1B87F512 = C:\ProgramData\Macrovision\FLEXnet Connect\6\
Property(C): FNCBINDIR.9FC896E6_8DD6_4BFD_A02C_189B1B87F512 = C:\ProgramData\FLEXnet\Connect\11\
Property(C): INSTALLSHIELD.9FC896E6_8DD6_4BFD_A02C_189B1B87F512 = C:\Program Files (x86)\Common Files\InstallShield\
Property(C): UPDATESERVICE.9FC896E6_8DD6_4BFD_A02C_189B1B87F512 = C:\Program Files (x86)\Common Files\InstallShield\UpdateService\
Property(C): IE5FOUND.9FC896E6_8DD6_4BFD_A02C_189B1B87F512 = C:\Windows\SysWOW64\shdocvw.dll
Property(C): DWUSOWNINGFEATURE.9FC896E6_8DD6_4BFD_A02C_189B1B87F512 = Sparta
Property(C): SecureCustomProperties.9FC896E6_8DD6_4BFD_A02C_189B1B87F512 = IE5FOUND.9FC896E6_8DD6_4BFD_A02C_189B1B87F512
Property(C): SKYPESHAREDDIR.6F88B3BF_1A40_4409_9A67_3EC9E8B8AD33 = C:\Program Files (x86)\Common Files\Skype\
Property(C): CommonFilesFolder.6F88B3BF_1A40_4409_9A67_3EC9E8B8AD33 = C:\Program Files (x86)\Common Files\
Property(C): MsiLogFileLocation = C:\Users\sujdavis\AppData\Local\Temp\MSIc58c6.LOG
Property(C): PackageCode = {DE7AE6AE-9786-4752-8B63-3A8D4C38F79A}
Property(C): ProductState = -1
Property(C): PackagecodeChanging = 1
Property(C): IsAdminPackage = 1
Property(C): CURRENTDIRECTORY = \\pltbsnadc01\Deployment\01182012\extracted
Property(C): CLIENTUILEVEL = 0
Property(C): CLIENTPROCESSID = 3664
Property(C): VersionDatabase = 300
Property(C): VersionMsi = 5.00
Property(C): VersionNT = 601
Property(C): VersionNT64 = 601
Property(C): WindowsBuild = 7601
Property(C): ServicePackLevel = 1
Property(C): ServicePackLevelMinor = 0
Property(C): MsiNTProductType = 1
Property(C): WindowsFolder = C:\Windows\
Property(C): WindowsVolume = C:\
Property(C): System64Folder = C:\Windows\system32\
Property(C): SystemFolder = C:\Windows\SysWOW64\
Property(C): RemoteAdminTS = 1
Property(C): TempFolder = C:\Users\sujdavis\AppData\Local\Temp\
Property(C): ProgramFiles64Folder = C:\Program Files\
Property(C): CommonFiles64Folder = C:\Program Files\Common Files\
Property(C): AppDataFolder = C:\Users\sujdavis\AppData\Roaming\
Property(C): FavoritesFolder = C:\Users\sujdavis\Favorites\
Property(C): NetHoodFolder = C:\Users\sujdavis\AppData\Roaming\Microsoft\Windows\Network Shortcuts\
Property(C): PersonalFolder = C:\Users\sujdavis\Documents\
Property(C): PrintHoodFolder = C:\Users\sujdavis\AppData\Roaming\Microsoft\Windows\Printer Shortcuts\
Property(C): RecentFolder = C:\Users\sujdavis\AppData\Roaming\Microsoft\Windows\Recent\
Property(C): SendToFolder = C:\Users\sujdavis\AppData\Roaming\Microsoft\Windows\SendTo\
Property(C): TemplateFolder = C:\ProgramData\Microsoft\Windows\Templates\
Property(C): LocalAppDataFolder = C:\Users\sujdavis\AppData\Local\
Property(C): MyPicturesFolder = C:\Users\sujdavis\Pictures\
Property(C): AdminToolsFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools\
Property(C): StartupFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\
Property(C): StartMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\
Property(C): DesktopFolder = C:\Users\Public\Desktop\
Property(C): FontsFolder = C:\Windows\Fonts\
Property(C): GPTSupport = 1
Property(C): OLEAdvtSupport = 1
Property(C): ShellAdvtSupport = 1
Property(C): MsiAMD64 = 6
Property(C): Msix64 = 6
Property(C): Intel = 6
Property(C): PhysicalMemory = 2048
Property(C): VirtualMemory = 3298
Property(C): AdminUser = 1
Property(C): MsiTrueAdminUser = 1
Property(C): LogonUser = sujdavis
Property(C): UserSID = S-1-5-21-2356834242-3937279893-1142474906-1433
Property(C): UserLanguageID = 1033
Property(C): ComputerName = DMOULDS-WIN7X64
Property(C): SystemLanguageID = 1033
Property(C): ScreenX = 1920
Property(C): ScreenY = 1080
Property(C): CaptionHeight = 22
Property(C): BorderTop = 1
Property(C): BorderSide = 1
Property(C): TextHeight = 16
Property(C): TextInternalLeading = 3
Property(C): ColorBits = 32
Property(C): TTCSupport = 1
Property(C): Time = 15:02:30
Property(C): Date = 1/18/2012
Property(C): MsiNetAssemblySupport = 2.0.50727.4927
Property(C): MsiWin32AssemblySupport = 6.1.7601.17514
Property(C): RedirectedDllSupport = 2
Property(C): MsiRunningElevated = 1
Property(C): Privileged = 1
Property(C): USERNAME = don
Property(C): DATABASE = C:\Users\sujdavis\AppData\Local\Temp\1c58c7.msi
Property(C): OriginalDatabase = \\pltbsnadc01\Deployment\01182012\extracted\plantronicsure2-5.msi
Property(C): SOURCEDIR = \\pltbsnadc01\Deployment\01182012\extracted\
Property(C): VersionHandler = 5.00
Property(C): UILevel = 5
Property(C): ACTION = INSTALL
Property(C): EXECUTEACTION = INSTALL
Property(C): ROOTDRIVE = C:\
Property(C): CostingComplete = 1
Property(C): OutOfDiskSpace = 0
Property(C): OutOfNoRbDiskSpace = 0
Property(C): PrimaryVolumeSpaceAvailable = 0
Property(C): PrimaryVolumeSpaceRequired = 0
Property(C): PrimaryVolumeSpaceRemaining = 0
Property(C): INSTALLLEVEL = 1
=== Logging stopped: 1/18/2012 15:02:30 ===
MSI (c) (50:6C) [15:02:30:056]: Note: 1: 1708
MSI (c) (50:6C) [15:02:30:057]: Product: Plantronics Spokes Software -- Installation failed.

MSI (c) (50:6C) [15:02:30:058]: Windows Installer installed the product. Product Name: Plantronics Spokes Software. Product Version: 2.5.50537.0. Product Language: 1033. Manufacturer: Plantronics, Inc.. Installation success or error status: 1602.

MSI (c) (50:6C) [15:02:30:063]: Grabbed execution mutex.
MSI (c) (50:6C) [15:02:30:063]: Cleaning up uninstalled install packages, if any exist
MSI (c) (50:6C) [15:02:30:070]: MainEngineThread is returning 1602
=== Verbose logging stopped: 1/18/2012 15:02:30 ===
Answered 01/20/2012 by: jendeeda
Yellow Belt

Please log in to comment
0
ORIGINAL: jendeeda

I did do that and have been staring at it but nothing is jumping out at me. Not sure how to attach it here so I'll copy and paste what I think might be relevant? I'm seeing user exit and wondering if it has something to do with the license prompt - perhaps defaulting to cancel? Thank you so very much for any help.
.
.
.
.
MSI (c) (50:6C) [15:02:30:058]: Windows Installer installed the product. Product Name: Plantronics Spokes Software. Product Version: 2.5.50537.0. Product Language: 1033. Manufacturer: Plantronics, Inc.. Installation success or error status: 1602.



Have a look at this reference guide
http://desktopengineer.com/msierrors

Seems the installation is cancelled (probably due to input missing).
Have a look in the MSI if there is a property for the license and add it in either an MST or to the install string.

/Anders
Answered 01/23/2012 by: andemats
Second Degree Black Belt

Please log in to comment
0
Hey jendeeda,
Just to rule some things in or out but are you trying to install this on Windows 7 64 bit? Or have you downloaded the 64bit version when you need the 32bit version?
Answered 01/23/2012 by: alphabeta
Third Degree Brown Belt

Please log in to comment
0
Action ended 15:02:27: WelcomeDlg. Return value 2. It's hard to tell without the lines above this one but it *looks* like the exit is happening from the 'Welcome' dialog, not the 'License Agreement' dialog.

BTW, I would change the 'LicenseAccepted' property to be a public property, i.e. in all upper-case. That way, it can be passed on the command line. Ditto for any other properties which you are prompting the user for.
Answered 01/23/2012 by: VBScab
Red Belt

Please log in to comment
0
Our msi works for both 32/64 but I installing it on a Win764bit but honestly I've tried it on 32 bit and had the same issue. I can't even get an MSI log anymore. I've deployed the sw probably 50 times now and one time it produced a log file but I don't know what I did different that time. I have loggin enabled in the MSI, in the registry on the target system and even in the GPO. I added the LicenseAccepted =1 to the Properties table and confirmed that the checkbox is selected by default but still won't install. I've elevated rights, tried both computer and user gpo's - I feel like I've tried everything. Since I can't even get an MSI log, I am really lost. To be clear, I'm looking in both %temp% and c:\windows\temp.I'll go look at the Welcome dialog and see if there is anything special there. I've beat the License Agreement to death I think. Again, any and all help is so much appreciated. If anyone is so inclined (please be inclined!) the MSI is available here: http://www.plantronics.com/us/support/software-downloads/download.jsp?file=PlantronicsURE-2-5-50537-0.msi&KeepThis=true&TB_iframe=true&height=420&width=640
Answered 01/24/2012 by: jendeeda
Yellow Belt

Please log in to comment
0
I've had a look at the MSI and the log you provided above. Like Ian said, it looks like it's not the License agreement that's causing the problem.
ORIGINAL: VBScab
It's hard to tell without the lines above this one but it *looks* like the exit is happening from the 'Welcome' dialog, not the 'License Agreement' dialog.


There's even a dialogue before the Welcome, 'PrepareDlg', which is checking for newer versions.
I'd give it a try to rem the following lines in the MSI-script, to make sure that's not bugging the install.

If NEWPRODUCTFOUND then
Cancel Installation Newer version already installed (PreventDowngrading)
End


I don't have the possibility to give the GPO deploy a test, so can't really help you there.

Did you try changing the license property to puplic (all UPPERCASE)?
Answered 01/25/2012 by: andemats
Second Degree Black Belt

Please log in to comment
0
@Jennifer:I can't even get an MSI log anymore.Really?!? Are you installing to a clean build machine each time? If you can't produce a log at all, it sounds like your WI installation may be broken. Do you get a log on one of the targets if you install from the command line?I have loggin enabled in the MSIThat's a neat trick. How have you managed that?!?

The 'PrepareDlg' dialog doesn't appear to do anything - it has no control events and no properties - so I would think you would be better removing that dialog completely.

Anders' advice is sound but note that a) he is saying to REM (i.e. comment or condition) out those lines, rather than remove them and b) he forgot to mention that, since the UI sequence doesn't run in a GPO install, you'll need to duplicate that in the InstallExecuteSequence. The quickest way to stop that CA running is to change the lineIf NEWPRODUCTFOUND thento something likeIf NEWPRODUCTFOUND AND 0=1 then in both sequences.
Answered 01/25/2012 by: VBScab
Red Belt

Please log in to comment
0
You're right Ian.
I was about to run off for lunch, so I only scribbled down my first thoughts.
Answered 01/25/2012 by: andemats
Second Degree Black Belt

Please log in to comment
0
Thank you both. Boy do I feel like a rookie. I don't know how to access the MSI script file that you are referring to. I ran an network install to extract the contents of the MSI and it is not there. I don't see a table with this name in the MSI using Orca. Can you tell me where to access?

I am not using a clean system every time I test. I would have to have 100 VM's! I am able to get a log file when I install manually and I'm also able to get a log file when I push out other MSI's via GPO. This MSI is pure evil I've decided. I read that you can add MsiLogging to the Properties table with a value of voicewarmupx to make the package create a log. The other thing I've noticed and I'm not sure if this is significant but when I load the MSI into the GPO the GPO shows the language as being Chinese. I'm not sure why it thinks it's chinese but I have been making sure to check the 'ignore language when installing' option within the object. @vbscab - You mention PrepareDlg, did you mean WelcomeDlg? I did remove the WelcomeDlg from the MSI completely and GPO did not install and no log file was created. Would love to work on MSI script file you reference today if you are available answer. Thank you!

Below are the lines that are above the section of log file I had sent previously:

MSI (c) (50:C8) [15:01:32:373]: Note: 1: 2262 2: Extension 3: -2147287038
MSI (c) (50:C8) [15:01:32:374]: Note: 1: 2262 2: Class 3: -2147287038
MSI (c) (50:C8) [15:01:32:374]: Note: 1: 2262 2: Extension 3: -2147287038
MSI (c) (50:C8) [15:01:32:374]: Note: 1: 2262 2: Class 3: -2147287038
MSI (c) (50:C8) [15:01:32:374]: Note: 1: 2262 2: Extension 3: -2147287038
MSI (c) (50:C8) [15:01:32:374]: Note: 1: 2262 2: Class 3: -2147287038
MSI (c) (50:C8) [15:01:32:374]: Note: 1: 2262 2: Extension 3: -2147287038
MSI (c) (50:C8) [15:01:32:374]: Note: 1: 2262 2: Class 3: -2147287038
MSI (c) (50:C8) [15:01:32:374]: Note: 1: 2262 2: Extension 3: -2147287038
MSI (c) (50:C8) [15:01:32:374]: Note: 1: 2262 2: Class 3: -2147287038
MSI (c) (50:C8) [15:01:32:374]: Note: 1: 2262 2: Extension 3: -2147287038
MSI (c) (50:C8) [15:01:32:374]: Note: 1: 2262 2: Class 3: -2147287038
MSI (c) (50:C8) [15:01:32:374]: Note: 1: 2262 2: Extension 3: -2147287038
MSI (c) (50:C8) [15:01:32:375]: Note: 1: 2262 2: Class 3: -2147287038
MSI (c) (50:C8) [15:01:32:375]: Note: 1: 2262 2: Extension 3: -2147287038
MSI (c) (50:C8) [15:01:32:375]: Note: 1: 2262 2: Class 3: -2147287038
MSI (c) (50:C8) [15:01:32:375]: Note: 1: 2262 2: Extension 3: -2147287038
MSI (c) (50:C8) [15:01:32:375]: Note: 1: 2262 2: Class 3: -2147287038
MSI (c) (50:C8) [15:01:32:375]: Note: 1: 2262 2: Extension 3: -2147287038
MSI (c) (50:C8) [15:01:32:375]: Note: 1: 2262 2: Class 3: -2147287038
MSI (c) (50:C8) [15:01:32:375]: Note: 1: 2262 2: Extension 3: -2147287038
MSI (c) (50:C8) [15:01:32:375]: Note: 1: 2262 2: Class 3: -2147287038
MSI (c) (50:C8) [15:01:32:375]: Note: 1: 2262 2: Extension 3: -2147287038
MSI (c) (50:C8) [15:01:32:376]: Note: 1: 2262 2: Class 3: -2147287038
MSI (c) (50:C8) [15:01:32:376]: Note: 1: 2262 2: Extension 3: -2147287038
MSI (c) (50:C8) [15:01:32:376]: PROPERTY CHANGE: Modifying CostingComplete property. Its current value is '0'. Its new value: '1'.
MSI (c) (50:C8) [15:01:32:376]: Note: 1: 2205 2: 3: BindImage
MSI (c) (50:C8) [15:01:32:377]: Note: 1: 2205 2: 3: PublishComponent
MSI (c) (50:C8) [15:01:32:377]: Note: 1: 2205 2: 3: SelfReg
MSI (c) (50:C8) [15:01:32:377]: Note: 1: 2262 2: Extension 3: -2147287038
MSI (c) (50:C8) [15:01:32:377]: Note: 1: 2205 2: 3: Font
MSI (c) (50:C8) [15:01:32:377]: Note: 1: 2262 2: Class 3: -2147287038
MSI (c) (50:C8) [15:01:32:377]: Note: 1: 2727 2:
Info 2898. For WixUI_Font_Title textstyle, the system created a 'Tahoma' font, in 0 character set, of 14 pixels height.
Action 15:01:34: LicenseAgreementDlg. Dialog created
Action 15:02:26: CancelDlg. Dialog created
Action ended 15:02:27: WelcomeDlg. Return value 2.
MSI (c) (50:6C) [15:02:27:884]: Doing action: UserExit
Action 15:02:27: UserExit.
Action start 15:02:27: UserExit.
Action 15:02:27: UserExit. Dialog created
Action ended 15:02:30: UserExit. Return value 2.
Action ended 15:02:30: INSTALL. Return value 2.
Property(C): UpgradeCode = {C9213280-0D15-48CA-8014-527B4A6973C2}
Property(C): DPI = #96
Answered 01/25/2012 by: jendeeda
Yellow Belt

Please log in to comment
0
I am not using a clean system every time I test. B I G mistake. You cannot perform a valid test on a "dirty" target. I would have to have 100 VM's!Er...no! Part of the geniius of VMs is that, once you have finished, you just click and voilá! The machine is in exactly the state is was before you started.

For example, how do you test that your latest package successfully upgrades an older version? I'll bet it's by installing vX, then installing vY, right? And this on an already dirty machine, right? How much easier and quicker it would be to have a stored snapshot of vX? Fire up a VM, load the snapshot and you're ready to test.

You cannot, cannot, CANNOT package without clean machines and VMs are by far and away the best way to have as many as you need.

Moving on, no, I didn't mean the 'Welcome' dialog, I meant 'PrepareDlg'. Delete it. Then get your employer to spring for a copy of InstallShield. I know your MSIs are created by Wix but doing work of any great length in Orca/InstEdit - especially for a newcomer to packaging - is not recommended. While you're waiting for the PO to be authorised and the software delivered, you can read & digest Phil Wilson's The Definitive Guide To Windows Installer. You will struggle with WI unless you know the fundamentals.

EDIT:
Thinking about it, Flexera offers offers a 30-day trial of IS. Go for that while you wait but definitely read Phil's book first. BTW, forget Amazon: it's available for free. Search the forums here on AppDeploy. Someone posted a link to the free copy.

If you're going to persist with Orca/InstEdit, you will need to

- attend to the Control and ControlEvent tables to remove references to the deleted PrepareDlg dialog.
- find the line with sequence number 26 in the InstallExecuteSequence table and alter the text in the 'Condition' column to read 'NEWPRODUCTFOUND AND 0=1'
- copy that text to the clipboard, then...
- ...paste it into the 'Conditon' column for sequence number 26 in the 'InstallUISequence' table.
Answered 01/26/2012 by: VBScab
Red Belt

Please log in to comment
0
Yeah, I wouldn't use Orca more than to view or do minor changes.

ORIGINAL: VBScab
EDIT:
Thinking about it, Flexera offers offers a 30-day trial of IS. Go for that while you wait but definitely read Phil's book first. BTW, forget Amazon: it's available for free. Search the forums here on AppDeploy. Someone posted a link to the free copy.


I did download the trial version, but there's really so much you can do with it.
Also got a phone call from "My personal contact person at Flexera" [8D], so I told him what I wanted to try (snapshot, edit MSI/MST and so on...). He told me those functions weren't really enabled in the trial version.[>:]

But I agree.. You can't really be asked to perform major changes and so on to an MSI without the proper tools. It's like plowing a field with a tooth pick
Answered 01/26/2012 by: andemats
Second Degree Black Belt

Please log in to comment
0
He told me those functions weren't really enabled in the trial version.PMSL...he will have been a S A L E S person so he's going to tell you that. All of the trial versions I've ever used have been fully functional but they do not load at all after 30 days.
Answered 01/26/2012 by: VBScab
Red Belt

Please log in to comment
0
Hi everyone
I should have been more clear. I am the product manager for software. I am not the IT person (access to vm creation) or the sw engineer(person who actually does the builds). I've been asked to figure out why our MSI can't be installed via group policy. Unfortunately, I do not have the access to likely a lot of what would be helpful. I only have the ability to create/deploy GPO's on our test domain and of course Orca. Our sw eng group is slammed and doesn't have the bandwidth to spend time on the issue but it's important to me so they've asked that I take a stab at telling them what is wrong. I apologize if I wasn't clear about my role before and I can imagine its frustrating to help truly such a rook! Thank you tho for the effort thus far.

I did some more digging into the log file and think that perhaps the "remove file path" might be what it's crashing on?

MSI (c) (50:6C) [15:01:32:183]: skipping installation of assembly component: {E4C397DE-374A-43B9-BFDC-F81424F8C790} since the assembly already exists
Action ended 15:01:32: CostFinalize. Return value 1.
MSI (c) (50:6C) [15:01:32:188]: Skipping action: MaintenanceWelcomeDlg (condition is false)
MSI (c) (50:6C) [15:01:32:188]: Skipping action: ResumeDlg (condition is false)
MSI (c) (50:6C) [15:01:32:188]: Doing action: WelcomeDlg
Action 15:01:32: WelcomeDlg.
Action start 15:01:32: WelcomeDlg.
Action 15:01:32: WelcomeDlg. Dialog created
MSI (c) (50:C8) [15:01:32:299]: Note: 1: 2205 2: 3: _RemoveFilePath
MSI (c) (50:C8) [15:01:32:338]: Note: 1: 2262 2: Class 3: -2147287038
MSI (c) (50:C8) [15:01:32:338]: Note: 1: 2262 2: Extension 3: -2147287038
MSI (c) (50:C8) [15:01:32:338]: Note: 1: 2262 2: Class 3: -2147287038
Answered 01/26/2012 by: jendeeda
Yellow Belt

Please log in to comment
0
ORIGINAL: jendeeda
...they've asked that I take a stab at telling them what is wrong.


I can relate to being "slammed" with work.
How about giving them some of the pointers we've come up with here and go from there.
If they have access (and I really hope they do) to the proper tools (Wise/AS/IS/VM...), they would soon be able to modify the installer with the changes above and perhaps even try it out and log the installation on a clean snapshot of a virtual machine.
Answered 01/27/2012 by: andemats
Second Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity