The app in question is TradeWeb v7.04. The vendor assures us that it's 7.04 but the version property is '7.3'...which speaks volumes about quality control.

When deployed per-user (a site requirement) via GP, the install fails at the FeaturesInstalling CA which is one of the first CAs. I can install it fine if I RunAs a local admin. I have reset the IS driver (it requires - and checks for! - v7.7.02) COM+ stuff to be 'Launching User' rather than the default 'Interactive User'. The error logged is:

[font="courier new"]MSI (s) (98:F4) [12:30:26:813]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI13E.tmp, Entrypoint: FeaturesInstalling
1: Invoke Function fails, Error = 0x8000ffff

Googling for the error just brings up a bunch of stuff about it occuring for re-installs but this is on a virgin VM which has never seen the app before. If I can't get to the bottom of this, I'm just going to re-package the damn thing.
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
ORIGINAL: VBScab
The app in question is TradeWeb v7.04. The vendor assures us that it's 7.04 but the version property is '7.3'...which speaks volumes about quality control.
When deployed per-user (a site requirement) via GP, the install fails at the FeaturesInstalling CA which is one of the first CAs. I can install it fine if I RunAs a local admin. I have reset the IS driver (it requires - and checks for! - v7.7.02) COM+ stuff to be 'Launching User' rather than the default 'Interactive User'. The error logged is:

[font="courier new"]MSI (s) (98:F4) [12:30:26:813]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI13E.tmp, Entrypoint: FeaturesInstalling
1: Invoke Function fails, Error = 0x8000ffff


VB, if the CA isn't necessary for the app to run correctly, maybe a condition If AdminUser would work for you. Or just comment it out altogether. What does the CA do?

What else? There's the AlwaysInstallElevated policy, but that's not recommended for security reasons.

Or a repackage, as you say. That's always fun. ;-)
Answered 01/18/2008 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
VB let me know what you had to do to fix this once you've got this figured out...I had the same issue w/ an application I was trying to deploy through SMS using the system account. It would fail becuase the DCOM impersonation level was set to interactive user...I could never figure out a workaround for the application deployment, except only have it run when a user was logged on.
Answered 01/18/2008 by: danr29
Purple Belt

Please log in to comment
0
ORIGINAL: aogilmor
VB, if the CA isn't necessary for the app to run correctly, maybe a condition If AdminUser would work for you. Or just comment it out altogether. What does the CA do?
(From MacroVision's site)"OnFeaturesInstalling calls all the feature Installing and Uninstalling events that are defined."
or
"Calls any OnInstalling or OnUninstalling event-handler functions associated with features being installed or uninstalled, depending on the action state of the feature."

Very succint...

ORIGINAL: aogilmor
What else? There's the AlwaysInstallElevated policy, but that's not recommended for security reasons.
This is a GP-driven install so it's elevated by definition. I'm not sure of the relevance here, though.

ORIGINAL: aogilmor
Or a repackage, as you say. That's always fun. ;-)
I'm moving in that direction, given the "tumbleweed blows across set" responses I've had here and elsewhere. (No disrespect to those who *have* responded, of course!)
Answered 01/21/2008 by: VBScab
Red Belt

Please log in to comment
0
Out of interest, what is the value of the Type attribute for the FeaturesInstalling custom action ?

Regards,

Spartacus
Answered 01/21/2008 by: spartacus
Black Belt

Please log in to comment
0
Out of interest, what is the value of the Type attribute for the FeaturesInstalling custom action ? 3073: Calls FeaturesInstalling function in ISScriptBridge.DLL (already installed)/Synchronous/Deferred, System context
Answered 01/21/2008 by: VBScab
Red Belt

Please log in to comment
2
A long shot perhaps, but try changing the type to 1025 as suggested in the following article

http://knowledge.macrovision.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=Q107124&sliceId=

Regards,

Spartacus
Answered 01/21/2008 by: spartacus
Black Belt

Please log in to comment
0
Apologies for not responding, Graham. I've been side-tracked with another project which has taken priority. I'll try that as soon as I've finished and I'll be sure to post back with the result.
Answered 01/22/2008 by: VBScab
Red Belt

Please log in to comment
2
ORIGINAL: spartacus
A long shot perhaps, but try changing the type to 1025 as suggested in the following article
http://knowledge.macrovision.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=Q107124&sliceId=
Bingo! Thanks, Graham. I got the install to complete by:
- resetting the DCOM permissions for all 'InstallShield Driver' COM+ servers to 'Launching User', using the script mentioned often here in a CA placed very early on in the Deferred sequence
- set the OnFeaturesInstalling CA from 'System Context' to 'User Context' (for Orca fans, I edited the 'Type' value 3073 to 1025)
Answered 01/23/2008 by: VBScab
Red Belt

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