When running active setup with stubpath msiexec /fu [productcode] I get this error.
Any idea what might be causing this.

This is not the first time i get this error. Had it with other packages as well.
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
Const intPosterBehaviourBoneIdle = 0
Const Const intPosterBehaviourSentient = 1

blnReturn = GetPosterBehaviour(ReadThisPost, intPosterBehaviour)
If intPosterBehaviour=intPosterBehaviourBoneIdle Then
Call DisplayURL("http://itninja.com/question/gnu,-freeware-and-shareware-programs-to-cloning3167")
End If
Answered 12/08/2009 by: VBScab
Red Belt

Please log in to comment
2
I might be mistaken but I think this means more than one Windows Installer package is trying to execute actions in server context. Does your msi happen to return error 1618?

In other words, 2 packages are trying to install at the same time.

EDIT: or, since I'm a slow typer, what Ian said [:)]
Answered 12/08/2009 by: pjgeutjens
Red Belt

Please log in to comment
0
@ pjgeutjes, is there any way that I can avoid them from installing at the same time ?
When logging in all msi's with active setup built in are triggered.
Answered 12/08/2009 by: ikke
Senior Purple Belt

Please log in to comment
2
tbh I didn't know they were triggered at the same time...
thought Windows would be smart enough to process them one by one, but then using Windows and smart in the same sentence might not be a good idea :)

So in short, no idea really
Answered 12/08/2009 by: pjgeutjens
Red Belt

Please log in to comment
0
Ok, thanks for your information !
Answered 12/08/2009 by: ikke
Senior Purple Belt

Please log in to comment
0
AS isn't multi-threaded (witness the set-up of IE, WMP and so on in a standard build) so your interfering MSI is coming from elsewhere. Do you deploy anything by SCCM/SMS, Tivoli, or whatever? Is there a post-reboot application finishing up?
Answered 12/09/2009 by: VBScab
Red Belt

Please log in to comment
0
It seems that a java msi is doing a curent user but I will have investigate how this is triggered.
After two activesetups fail, this is the msi one that fininshes its configuration.
Answered 12/09/2009 by: ikke
Senior Purple Belt

Please log in to comment
2
Enable the windows installer Logging policy and check the timestamps between the logs created during logon.
Empty the %temp% folder for the user you're going to do this to easier find the newly created MSI logs.

You could also launch autoruns from sysinternals...oops I mean Microsoft too check what is launched during logon.
Answered 12/10/2009 by: AngelD
Red Belt

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