Software Deployment

Hi,

This error occurs if you are using any script in your package.The best way to use a script is to sore this first in the Binary table and then use this in the custom action table.Make sure that you use Type = 6 when doing so and try it sequencing after InstallFinalize.

This error occurs if you are using any script in your package.Utter tosh. A 1720 error simply means that the script couldn't be run.

I can practically guarantee that you have fallen foul of the packaging beginner's trap and are using 'WScript' directives in the script. By that I mean things like 'WScript.Echo', 'WScript.CreateObject' and so on. WScript is used by the Windows Scripting Host runtime on the workstation itself. The Windows Installer uses its own runtime, not WSH, for VBScript. Thus, you need to remove all such directives from your script. This, of course, makes it tricky to have scripts which can run externally (for testing) and internally. I use a test for a common Session property, setting a Boolean which can be tested in the code to branch accordingly.

What is the script doing? It may well be that you can achieve its effect using native MSI functionality.

Any action after InstallFinalize runs in the context of the logged-in user, rather than in System context. If what the CA is doing requires admin-level privileges, it will fail.

AFAIK 1720 is concerned only the instsall log would help you,