Hi Scott,
From Step#5 it seems like WMI is corrupted on the machine. Before we move
further trying to correct WMI, kindly run the following script (it is a .js
file) and update us with the results :
>Script Start<
var runtime = new Date();
WScript.Echo(runtime.toString());
WScript.Echo("Executing command: WMI Test");
var HKEY_LOCAL_MACHINE = 0x80000002;
var strComputer = ".";
var arrValueNames;
var arrValueTypes;
var strKeyPath;
var result;
var oReg = GetObject("winmgmts:{impersonationLevel=impersonate}!\\\\" +
strComputer
+ "\\root\\default:StdRegProv");
// test if v1.0 installed.
strKeyPath = "SOFTWARE\\Microsoft\\.NETFramework\\policy\\v1.0";
result = oReg.EnumValues(HKEY_LOCAL_MACHINE, strKeyPath, arrValueNames,
arrValueTypes);
WScript.Echo("\tKey:"+strKeyPath+"\tResult:"+result);
if (result == 0)
{
WScript.Echo("CLR VERSION 1.0 = True");
// test if v1.0 SP2 installed.
strKeyPath = "SOFTWARE\\Microsoft\\Updates\\.NETFramework\\1.0\\S321884";
result = oReg.EnumValues(HKEY_LOCAL_MACHINE, strKeyPath, arrValueNames,
arrValueTypes);
WScript.Echo("\tKey:"+strKeyPath+"\tResult:"+result);
if (result == 0)
WScript.Echo("CLR VERSION 1.0 SP2 = True");
else
{
WScript.Echo("");
WScript.Echo("Warning: MissingSP2");
WScript.Echo("");
}
}
// test if v1.1 installed.
strKeyPath = "SOFTWARE\\Microsoft\\.NETFramework\\policy\\v1.1";
result = oReg.EnumValues(HKEY_LOCAL_MACHINE, strKeyPath, arrValueNames,
arrValueTypes);
WScript.Echo("\tKey:"+strKeyPath+"\tResult:"+result);
if (result == 0)
{
WScript.Echo("CLR VERSION 1.1 = True");
}
>End Script<
Thx
Barath
This posting is provided "As Is" with no warranties, and confers no
rights.Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
--------------------
>Content-Class: urn:content-classes:message
>From: "Scott Ulman" <anonymous@discussions.microsoft.com>
>Sender: "Scott Ulman" <anonymous@discussions.microsoft.com>
>References: <0c8d01c3b04c$1bd2d1b0$a401280a@phx.gbl>
<COELb3IsDHA.3428@cpmsftngxa07.phx.gbl>
>Subject: RE: Error Code 1603 installing EIF on Win2003 Server
>Date: Sat, 22 Nov 2003 11:31:53 -0800
[quoted text clipped - 62 lines]
>
>Scott Ulman
Scott Ulman - 25 Nov 2003 19:18 GMT
Hello Barath,
I ran the script as instructed using the cscript tool. Got
the following result:
"Microsoft (R) Windows Script Host Version 5.6
Copyright ....
Tue Nove 25 11:27:40 CST 2003
Executing command: WMI Test
E:\Documents and Settings\Scott\scripts\barathjsscript.js
(17,2) SWbemObjectEx:
Unexpected error"
I then inserted the following into the script after the
line var oReg = GetObject(...):
if(oReg != null)
{
WScript.Echo("Got first object oReg");
}
Rerunning the script, I then got
"Microsoft (R) Windows Script Host Version 5.6
...
Executing command: WMI Test
Got first object oReg
E:\Documents and Settings\Scott\scripts\barathjsscript.js
(21,2) SWbemObjectEx:
Unexpected error"
Hence a script error is clearly occurring at the line
"result = oReg.EnumValues(HKEY_LOCAL_MACHINE, strKeyPath,
arrValueNames, arrValueTypes);"
but the oReg object is being created.
I checked and the registry key
SOFTWARE\\Microsoft\\.NETFramework\\policy\\v1.0" has been
deleted.
Hence I removed the tests for the Framework 1.0 from the
script and left only the test for v1.1 starting
with the line 'strKeyPath
= "SOFTWARE\\Microsoft\\.NETFramework\\policy\\v1.1";'
plus all blank lines.
That key DOES exist in the registry.
I ran the shortened script (leaving in my addition to test
for a null object) and got the same result as in
the full script:
"Microsoft (R) Windows Script Host Version 5.6
...
Executing command: WMI Test
Got first object oReg
E:\Documents and
Settings\Scott\scripts\shortbarathjsscript.js(13,2)
SWbemObjectEx:
Unexpected error"
where once again the script error occurred at the line
"result = oReg.EnumValues(HKEY_LOCAL_MACHINE, strKeyPath,
arrValueNames, arrValueTypes);"
I assume this is related to the inability to EnumInstances
in the wbemtest tool?
Thanks for your help. I await your instructions for what
to do next.
Barath Vasudevan [MS] - 26 Nov 2003 16:24 GMT
Hi Scott,
I would believe that the error is due to the WMI not functioning correctly
on your machine. If this is not a production machine you can try to
recreate the WMI repository thro the .cmd script.
Net stop winmgmt /y
If exist ?%windir%\system32\wbem\repository.old? rmdir /s/q
?%windir%\system32\wbem\repository.old?
Rename ?%windir%\system32\wbem\repository?
?%windir%\system32\wbem\repository.old?
for /f %s in ('dir /b /s %windir%\system32\wbem\*.dll') do regsvr32 /s %s
Let me know the results...
Since WMI is a core part of the OS , if the prev steps doesn't help, the
only other option that I can think of is to try reparing the OS or
reinstall it :( . However, if I do find any other option or workaround
I'll let you know.
Regards,
Barath
This posting is provided "As Is" with no warranties, and confers no
rights.Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
--------------------
>Content-Class: urn:content-classes:message
>From: "Scott Ulman" <anonymous@discussions.microsoft.com>
>Sender: "Scott Ulman" <anonymous@discussions.microsoft.com>
>References: <0c8d01c3b04c$1bd2d1b0$a401280a@phx.gbl>
<COELb3IsDHA.3428@cpmsftngxa07.phx.gbl>
<00b801c3b12f$48d03610$a401280a@phx.gbl>
<0mmIGrqsDHA.3428@cpmsftngxa07.phx.gbl>
>Subject: RE: Error Code 1603 installing EIF on Win2003 Server
>Date: Tue, 25 Nov 2003 11:18:34 -0800
[quoted text clipped - 76 lines]
>Thanks for your help. I await your instructions for what
>to do next.