thread returns zero but installation fails..
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
There is a problem with this Windows Installer package. A script required for this install to complete could not be run. Contact your support personnel or package vendor. Custom action CUSTOMACTION1 script error -2146828212, Microsoft VBScript runtime error: Path not found Line 10, Column 5,


there's your problem.

also, when posting lengthy bits of text like your log, please use the code tags.

rgds,

PJ
Answered 08/23/2010 by: pjgeutjens
Red Belt

Please log in to comment
0
please use the code tags. Logs of failed installs are mostly air, in terms of useful information. Generally speaking, you need only find the text 'Return value 3.' and post the dozen or so lines above and below the line containing that text.
Answered 08/24/2010 by: VBScab
Red Belt

Please log in to comment
0
CUSTOMACTION1 -- This custom action is failing ..
Answered 08/25/2010 by: blacklisted_packager
Orange Belt

Please log in to comment
0
Microsoft VBScript runtime error: Path not found Line 10, Column 5

Is CUSTOMACTION1 a vbscript that you added. because it's not working. Is there a harcoded path in there?
Answered 08/26/2010 by: timmsie
Fourth Degree Brown Belt

Please log in to comment
0
I'm willing to bet a fairly substantial wedge that your script is an embedded script and has at least one 'WScript' directive in it e.g. WScript.Echo or WScript.CreateObject...

When used embedded (as opposed to external), scripts use the Windows Installer engine's interpreter (let's call it, for argument's sake.) As such, it has no knowledge of Windows Scripting Host directives. You must remove these directives. You would want to avoid WScript.Echo anyway, as your package might be installed silently. As for WScript.CreateObject, just drop the 'WScript.' part.

Note that does not obviate the creation and use of WScript objects e.g. WScript.Network, as inSet objNetwork = CreateObject("Wscript.Network")In these cases, the 'WScript.' prefix must remain.
Answered 08/26/2010 by: VBScab
Red Belt

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