I am attempting to install the EIF on a Windows 2000 server with SP3
installed. The machine has Microsoft .NET Framework 1.1 installed, as well
as Framework 1.0 SP2. When I run the EIF installer, it gives me the error
message:
"The .NET Framework of version v1.0 (with SP2) or v1.1 is required. Please
install an appropriate .NET Framework and try setup again."
I looked in my Local Settings\Temp folder and found only a single log file,
EnterpriseInstrumentationSetup.log. It's contents (which are short) are as
follows:
[12/09/04,15:55:20] Starting Install.exe
[12/09/04,15:55:20] SourceDir:
C:\DOCUME~1\jbledsoe\LOCALS~1\Temp\1\IXP000.TMP\
[12/09/04,15:55:20] Package: EnterpriseInstrumentation.msi
[12/09/04,15:55:20] Trying to load msi.dll
[12/09/04,15:55:20] Loading: C:\WINNT\System32\msi.dll
[12/09/04,15:55:20] Switches:
[12/09/04,15:55:20] Install started
[12/09/04,15:55:20] Installing:
C:\DOCUME~1\jbledsoe\LOCALS~1\Temp\1\IXP000.TMP\EnterpriseInstrumentation.msi
[12/09/04,15:55:20] Trying to load msi.dll
[12/09/04,15:55:20] Loading: C:\WINNT\System32\msi.dll
[12/09/04,15:55:20] Full UI
[12/09/04,15:55:20] Calling MsiInstallProduct() with commandline:
REBOOT=ReallySuppress
I have both of the frameworks installed, and I can't see why the installer
says that I don't. Any help that anybody can offer would be greatly
appreciated!
Thanks
Mike Hayton [MS] - 29 Dec 2004 21:32 GMT
Is this still an issue for you?

Signature
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
--------------------
| I am attempting to install the EIF on a Windows 2000 server with SP3
| installed. The machine has Microsoft .NET Framework 1.1 installed, as well
[quoted text clipped - 17 lines]
| [12/09/04,15:55:20] Install started
| [12/09/04,15:55:20] Installing:
C:\DOCUME~1\jbledsoe\LOCALS~1\Temp\1\IXP000.TMP\EnterpriseInstrumentation.ms
i
| [12/09/04,15:55:20] Trying to load msi.dll
| [12/09/04,15:55:20] Loading: C:\WINNT\System32\msi.dll
[quoted text clipped - 7 lines]
|
| Thanks
John B [ATGi] - 29 Dec 2004 23:43 GMT
I found a way to work around the problem, but I'm still interested in
figuring out the root cause. I was able to perform a successful install of
the EIF on another machine, and when I looked at the log file for that
install, I realized that the installer was just doing things that I could do
manually (GAC some assemblies, InstallUtil the trace service, and so forth.)
I just performed the steps of the install manually, and everything seems to
be functioning properly. If there's something wrong with what I did though,
or if there is some solution that you're aware of, I'd be interested in
knowing what it is.
> Is this still an issue for you?
>
[quoted text clipped - 39 lines]
> |
> | Thanks
Mike Hayton [MS] - 17 Jan 2005 18:32 GMT
Sorry about the long delay.
Typically its been a problem with the installation of WMI on the machine.
Here's some things to try.
I. Collection install logs
1. From the Run option off the Start menu, open "cmd" to launch a command
prompt. Then type in the following commands:
2. Change to the directory containing EnterpriseInstrumentation.exe - if it
is in "C:\Documents and Settings\myTempDir" you would type:
cd /d "C:\Documents and Settings\myTempDir"
3. Execute the MSI install with the full logging enabled
EnterpriseInstrumentation.exe /c:"msiexec.exe /q /l*v
%temp%\EnterpriseInstrumentationMSI.log /i enterpriseinstrumentation.msi"
4. Complete the install (or see it fail)
5. Change to the %temp% directory
cd /d %temp%
6. Look for the following files and please attach them to a reply. Possible
filenames are:
EnterpriseInstrumentationMSI.log
EnterpriseInstrumentationInstall.log
EnterpriseInstrumentationInstallUtil.log
EnterpriseInstrumentationSetup.log
(depending on where the installation fails, not all of the files may be
present).
II. Collect versions of scrrun.dll
1. I would like to know the version of Scrrun.dll. There should typically
be only one instance of it on the machine, but I have seen multiple
instances.
III. Check that WMI is running
1. Can you check if the WMI (Windows management Instrumentation) service is
running and set to start "Automatic".
IV. Check whether StdRegProv is accessible
1. Start->Run->Wbemtest
2. Click on "Connect" (twice)
3. Click on "Open Instance" and give "StdRegProv" for the object path
V. Check if other namespace is working fine and
1. Start->Run->Wbemtest
2. Click on "Connect"
3. Type "root\cimv2" instead of "root\default" and "Connect"
4. Click on "Enumerate Instances"
5. Type "Win32_Process" and click ok... (Expected Result: See a new dialog

Signature
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
--------------------
|
| I found a way to work around the problem, but I'm still interested in
[quoted text clipped - 35 lines]
| > | [12/09/04,15:55:20] Install started
| > | [12/09/04,15:55:20] Installing:
C:\DOCUME~1\jbledsoe\LOCALS~1\Temp\1\IXP000.TMP\EnterpriseInstrumentation.ms
| > i
| > | [12/09/04,15:55:20] Trying to load msi.dll
[quoted text clipped - 9 lines]
| > |
| > | Thanks
John B [ATGi] - 17 Jan 2005 18:39 GMT
Thanks Mike. I will probably not look into this for a while, but I
appreciate you posting these steps to try.
> Sorry about the long delay.
>
[quoted text clipped - 107 lines]
> | > |
> | > | Thanks