[wpkg-users] Script execution: failure. Exit code: 1

[Malte Starostik]

Hi Ulli,

I was recently bitten by an uninstall of Adobe CS3 which badly messed up the 
.js file association - presumably because of Dreamweaver which registers 
itself for those files.
It was not a matter of assuring .js files run with [cw]script.exe, because 
somehow CS3 managed to completely break the thing - when running sth. like 
"cscript /nologo somescript.js", WSH complained that it has no scripting 
engine for files with the extension .js.
The simple fix was to set the (default) value of the registry key HKCR\.js to 
"JSFile" (w/o the quotes).

HTH,
Malte

Am Mittwoch, 27. Oktober 2010, 14:28:41 schrieb Ulli Conrad:
> Hi there,
> 
> had this problem on one machine. WPKG works perfect on all other
> machines in our department.
> 
> Since I saw (while searching the list archive) that a lot of people
> have/had this problem too, here's the solution (for this particular
> machine):
> 
> Another application (Apple Quicktime) has claimed handling of .js
> files (for whatever reason), so Windows Scripting Host didn't
> executed the wpkg.js file on the server...
> Solution is to reassign file type .js to WSH (in Windows Explorer -
> folder options - file types) and/or reinstall WSH (by right click on
> %windir%\inf\wsh.inf and select "Install").
> 
> Just posting this in case someone else have the same problem ;-)