J:\DataStage_install\media\FP2_WIN
的目录
2011-02-23 15:24
<DIR> .
2011-02-23 15:24
<DIR> ..
2010-12-22 15:36
617,189,076 fixpack_FP2_IS81_windows_8100-1.ispkg
2010-12-22 14:35
<DIR> jre
2011-01-28 16:01 1,274,502 updater.jar
2 个文件 618,463,578 字节
3 个目录 58,011,631,616 可用字节
以下为执行时的报错信息.
J:\DataStage_install\media\FP2_WIN>jre\bin\java.exe
-jar updater.jar
The Microsoft Windows
Scripting Engine is not working correctly. You can fix the Windows Scripting
Engine by reinstalling Windows Scripting Engine.
You can download
Windows Scripting Engine from the Microsoft website.
我也根据报错信息,去microsoft的官网,下载补丁MicrosoftFixit50181.msi修复了这个engine,但是仍然无用.
以下为IBM 工程师给出的解决note.
-------------------------------------------------------------------------------------------------------------------
Technote
(troubleshooting)
Problem(Abstract)
Version 163
and higher of the InfoSphere Update Installer requires Microsoft Windows
scripting support to query the status of Microsoft Windows services and other
Microsoft Windows states. If the Microsoft Windows scripting is broken or is
not installed, there will be errors in the logs.
Symptom
An
error in the Update Installer log is similar to this error:
Dec 10, 2009 2:00:55 PM , INFO: com.ibm.is.install.core.CommonProcess
IInstallCore90001:Command Array: cscript C:\Program Files\servicestate.js
//nologo, env = null, workingDir =null
Dec 10, 2009 2:00:55 PM , INFO: com.ibm.is.install.core.CommonProcess Exit
Code: 1, Elapsed Time(ms) = 94, OutputBuffer: Input Error: There is no script
engine for file extension ".js".
Cause
Microsoft
Windows scripting is not operational.
Resolving
the problem
See
the instructions on how to repair the Microsoft Windows scripting environment
athttp://www.winhelponline.com/articles/230/1/Error-There-is-no-script-engine-for-file-extension-when-running-js-files.html
Alternatively,
you can reinstall the Microsoft Windows scripting:
Windows
XP:
http://www.microsoft.com/downloads/details.aspx?FamilyID=47809025-D896-482E-A0D6-524E7E844D81
Windows 2003:
http://www.microsoft.com/downloads/details.aspx?&FamilyID=f00cb8c0-32e9-411d-a896-f2cd5ef21eb4
After the scripting environment has been repaired, install the patch, fix pack, or upgrade again.