Hi!
I could not install MSI package using OpenSSH secure shell. Procedure is the
following:
1. ssh administrator@windowsnode
2. msiexec /I package.msi /qn /L*v "c:\logfile.txt"
Installation aborts after some time. In the logfile there are the following
interesting lines:
MSI (s) (90:90): Skipping action: CCPSearch (condition is false)
MSI (s) (90:90): Skipping action: RMCCPSearch (condition is false)
MSI (s) (90:90): Doing action: VBSCheckForDependentProducts
MSI (s) (90:90): Creating MSIHANDLE (1) of type 790542 for thread 1424
MSI (s) (90:90): Creating MSIHANDLE (2) of type 0 for thread 1424
MSI (s) (90:90): Failed to marshal script action.
MSI (s) (90:90): Failed to marshal script action.
MSI (s) (90:90): Closing MSIHANDLE (2) of type 0 for thread 1424
MSI (s) (90:90): Closing MSIHANDLE (1) of type 790542 for thread 1424
MSI (s) (90:90): Note: 1: 1708
MSI (s) (90:90): Product: <Some XYZ package> -- Installation operation
failed.
The specialty of this MSI package is that it calls VBS functions.
Installation aborts before VBS function is executed (during function call, I
believe).
Even if VBS function is an empty one the symptom is the same.
This does not happen if package is installed locally, that is in Command
Prompt on Windows
node. This also does not happen if some other (commercial) SSH servers
are used (e.g. MKS secshd, WinSSHD).
OpenSSH is installed from latest package setupssh381-20040709.zip.
Windows systems are Windows 2000 Advanced Server, Windows XP and Windows XP
SP2.
Version of cygwin1.dll is 1005.10.0.0.
I personally believe that it must be something with threads. If I am right
cygwin does not use Windows native threads.
I would like to know if this is known behavior and if there is some patch or
configuration setting to solve this problem?
Best regards,
Ludvik
