Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / Enterprise Tools / November 2003

Tip: Looking for answers? Try searching our database.

Error Code 1603 installing EIF on Win2003 Server

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Scott Ulman - 21 Nov 2003 16:25 GMT
I am unable to install EIF on a Win2003 Server.  I get an
error return code of 1603.  Can anybody tell me what is
happening?

Details from the log files follow along with brief machine
desription.

Errors installing EnterpriseInstrumentation.exe Package  to
  Windows 2003 Server
     Framework 1.1 and Visual Studio .NET 2003 installed
and working properly
               (Net Framework Configuration tool shows
proper version and works)
               (VS.NET developer tools work)
     Previously side-by-side versions of Framework 1.0
and Visual Studio .NET were installed;
            (they were apparenly successfullyremoved via
the Control Panel | Add/Remove Programs)

The log files show this:
MSI9af4d.log:
  The .NET Framework of version v1.0 (with SP2) or v1.1
is required.  Please install an appropriate    

.NET Framework and try setup again.
  === Logging stopped: 11/20/2003  13:17:34 ===

EnterpriseInstrumentationSetup.log
  [11/20/03,13:17:22] Starting Install.exe
  [11/20/03,13:17:22] SourceDir: E:\DOCUME~1
\Scott\LOCALS~1\Temp\IXP000.TMP\
  [11/20/03,13:17:22] Package:
EnterpriseInstrumentation.msi
  [11/20/03,13:17:22] Trying to load msi.dll
  [11/20/03,13:17:22] Loading: E:\WIN2000\system32\msi.dll
  [11/20/03,13:17:23] Switches:
  [11/20/03,13:17:23] Install started
  [11/20/03,13:17:23] Installing:    

E:\DOCUME~1\Scott\LOCALS~1
\Temp\IXP000.TMP\EnterpriseInstrumentation.msi
  [11/20/03,13:17:23] Trying to load msi.dll
  [11/20/03,13:17:23] Loading: E:\WIN2000\system32\msi.dll
  [11/20/03,13:17:23] Full UI
  [11/20/03,13:17:23] Calling MsiInstallProduct() with
commandline: REBOOT=ReallySuppress
  [11/20/03,13:17:34] MsiInstallProduct() returned 1603
  [11/20/03,13:17:34]    [MsiInstallProduct]  
ReturnCode=1603
 [11/20/03,13:17:34] Preparing Dialog
  [11/20/03,13:17:34] Message: Setup failed.  Please
review the Enterprise Instrumentation readme    

file, which describes known issues and contains
information on obtaining support from Product    

Support Services.
  [11/20/03,13:17:38] Install.exe returning 1603
  [11/20/03,13:17:38]    [Install.exe]   ReturnCode=1603

EnterpriseInstrumentationInstall.log
  Thu Nov 20 13:17:26 CST 2003
  Executing command: IsDotNetInstalled
    Exception: Unexpected error
Jyothi Srinivasan [MS] - 22 Nov 2003 00:16 GMT
Hello Scott,

A similar error was seen before and it has been corruption of either the
scripting or wmi on the machine. Can

you perform the following steps and send us the associated files? From this
we should be able to diagnose what is

going on and help to solve 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. There should typically be only one instance of it on the machine, but we
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
box with the list of processes running on

the machine! )

Regards,
Jyothi

| I am unable to install EIF on a Win2003 Server.  I get an
| error return code of 1603.  Can anybody tell me what is
[quoted text clipped - 60 lines]
|    Executing command: IsDotNetInstalled
|     Exception: Unexpected error

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
Scott Ulman - 22 Nov 2003 19:31 GMT
Hello Jyothi,
I am unable to email a log-file attachment to you since
the Reply (E-mail) 'button' on the site is an unworking
URL. If you need the files, please email me an address
where I can send them.

I followed your instructions.  Especially pertinent is the
following excerpt from 2/3 of the way down the
EnterpriseInstrumentationMSI.log:

Property(S): MissingSP2 = Setup has detected that you have
versions 1.0 and 1.1 of the .NET Framework installed.  
While Enterprise Instrumentation is compatible with both
versions of the .NET Framework, please make sure that you
have installed Service Pac
k 2 (SP2) or later for the .NET Framework 1.0 to ensure
full compatibility.

As I indicated in my initial posting, we originally had
both Frameworks side-by-side for testing but have removed
Framework 1.0 via the Control Panel's Add/Remove programs.
We never installed SP2.

Evidently the setup is still finding some reference in the
registry to the Framework 1.0 installation.  Can you tell
me what entry I need to purge?

As to the other steps:
II) version of scrrun.dll in %windir%\system32 is
5.6.0.8515

III) WMI service is running but WMIDriverExtensions is not-
set to manual startup

IV) StdRegProv IS ACCESSIBLE

V) Other namespace-FAILURE here.  Got error message:

Number:0x800410003

Facility: WMI

Description: Access denied

I am running as Enterprise Admin

I appreciate the help

Scott Ulman
Barath Vasudevan [MS] - 24 Nov 2003 16:47 GMT
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.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.