RE: Enterprise Instrumentation -- Installation operation failed.

From: Mike Hayton [MS] (mikehayt__at_online.microsoft.com)
Date: 09/04/04 

Date: Sat, 04 Sep 2004 01:52:05 GMT

Here's the standard reply below...

Its maybe WMI corruption on the machine.
What's the OS that you're trying to install on?
Can you supply the EnterpriseInstrumentationInstall.log &
EnterpriseInstrumentationInstallUtil.log files if they exist? (see below)

FYI: Im out of office next week - so I may take some time to reply to this.

Cheers

Mike

======================================

This error has been seen before on other machines - it appears to be
typically a corruption with WMI on the machine, or in the perf counters.

However one posting said:
| Found what my problem was: Although I had removed .Net 1.0 from my
| workstation previously, it was not successfully uninstalled. Therefore,
I
| had two versions of .Net on my box 1.0 and 1.1. Once I SUCCESSFULLY
| removed 1.0 all went fine.

I'd try reseting WMI

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

I'd also collect some more information about the problem

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

Lastly I'd try rebuilding the perf counters

How to Manually Rebuild Performance Counter Library Values
http://support.microsoft.com/?kbid=300956

Please note that the above article pertains to english versions of the
Win2k.

To identify the available extensible counters on the machine use the tool
Extensible Performance Counter List
http://www.microsoft.com/windows2000/techinfo/reskit/tools/existing/exctrlst
-o.asp

The steps in teh KB article provides info on rebuilding only those ini
files available in the System32 folder. To rebuild the other extensible
counters (identified thro the exctrlst.exe) you'll need to lodctr the ini
files specific to the apps . For e.g the .Net perf coutners are exposed
thro ini files available in %windir%\Microsoft.Net\Framework\1.1.4322\*.ini

There is a tool available for rebuilding perf counters, send
(bvasude@online.microsoft.com) an email
(remove the online.) and he can send the tool to you. 

-- 
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'm getting error 1603 when trying to install the EIF on a Windows 2000 
| machine.  From reading previous posts I've already tried rebuilding the 
| performance counters using pcrwizard.exe, without success. Can anyone 
help 
| please?
| 
| Below is an extract from the end of the EnterpriseInstrumentationMSI.log 
| file which I generated using the command EnterpriseInstrumentation.exe 
| /c:"msiexec.exe /q /l*v %temp% EnterpriseInstrumentationMSI.log /i 
| enterpriseinstrumentation.msi"
| 
| 
| 
| Property(S): SystemLanguageID = 1033
| Property(S): ScreenX = 1280
| Property(S): ScreenY = 1024
| Property(S): CaptionHeight = 19
| Property(S): BorderTop = 1
| Property(S): BorderSide = 1
| Property(S): TextHeight = 16
| Property(S): ColorBits = 32
| Property(S): TTCSupport = 1
| Property(S): MsiNetAssemblySupport = 1.1.4322.573
| Property(S): RedirectedDllSupport = 1
| Property(S): Time = 9:25:21
| Property(S): Date = 9/2/2004
| Property(S): DATABASE = c:\WINNT\Installer\2313b.msi
| Property(S): OriginalDatabase = 
| c:\Temp\IXP000.TMP\enterpriseinstrumentation.msi
| Property(S): UILevel = 2
| Property(S): ACTION = INSTALL
| Property(S): ROOTDRIVE = c:\
| Property(S): CostingComplete = 1
| Property(S): OutOfDiskSpace = 0
| Property(S): OutOfNoRbDiskSpace = 0
| Property(S): PrimaryVolumeSpaceAvailable = 0
| Property(S): PrimaryVolumeSpaceRequired = 0
| Property(S): PrimaryVolumeSpaceRemaining = 0
| Property(S): SOURCEDIR = c:\Temp\IXP000.TMP\
| Property(S): SourcedirProduct = {9E8A483C-BE5B-4EDC-B649-63E0A47FB779}
| Property(S): ProductToBeRegistered = 1
| === Logging stopped: 9/2/2004  9:25:21 ===
| MSI (s) (60:70): Note: 1: 1708 
| MSI (s) (60:70): Product: Enterprise Instrumentation -- Installation 
| operation failed.
| 
| MSI (s) (60:70): Cleaning up uninstalled install packages, if any exist
| MSI (s) (60:70): MainEngineThread is returning 1603
| MSI (c) (44:A0): Decrementing counter to disable shutdown. If counter >= 
0, 
| shutdown will be denied.  Counter after decrement: -1
| MSI (c) (44:A0): MainEngineThread is returning 1603
| === Verbose logging stopped: 9/2/2004  9:25:22 ===
| 
| 
|

Relevant Pages

  • RE: EIF Installation Error 1722
    ... There's a more recent thread titled "EIF Install Problem" that appears ... typically a corruption with WMI on the machine, or in the perf counters. ... The steps in teh KB article provides info on rebuilding only those ini ... | "Mike Hayton " wrote: ...
    (microsoft.public.vsnet.enterprise.tools)
  • RE: EIF Install problem
    ... typically a corruption with WMI on the machine, or in the perf counters. ... I'd try reseting WMI ... Execute the MSI install with the full logging enabled ...
    (microsoft.public.vsnet.enterprise.tools)
  • RE: Enterprise Instrumentation -- Installation operation failed.
    ... but without success. ... > What's the OS that you're trying to install on? ... > typically a corruption with WMI on the machine, or in the perf counters. ... > The steps in teh KB article provides info on rebuilding only those ini ...
    (microsoft.public.vsnet.enterprise.tools)
  • RE: FC4 does not work, "out of the box" for me; GUI/X11 fails
    ... that it doesn't pay to spend the energy rebuilding the current ... Install routines that don't install unless the user ... The fingers have been burnt by Red Hat, but Fedora remains the distro ...
    (Fedora)
  • Re: WMI Failure
    ... Sorry for late response. ... An alternative to doing a clean install is to just do these steps which will ... type the drive letter of your Windows XP installation media. ... WMI, RPC, etc look like they are all running. ...
    (microsoft.public.windowsxp.wmi)