Problems installing EIF on systems with Crystal Reports 8.0 (currently or previously installed)

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Jim - 02 Nov 2003 00:38 GMT

We have isolated a problem down on installing EIF on Windows 2000 systems to
those that have currently or have had Crystal Reports 8.0 installed. It
produces the following two entries in the EventLog. Has anyone run into this
problem before? Any ideas as to what may be the problem?

We have made sure that only .NET Framework 1.1 is installed and have tried
uninstalling and reinstalling the .NET Framework 1.1 but it made no
difference.

Thank you in advance for assistance you can offer.

Jim

Event Type:    Error
Event Source:    MsiInstaller
Event Category:    None
Event ID:    11720
Date:        10/2/2003
Time:        10:15:12 AM
User:        N/A
Computer:    BILLSPEC
Description:
Product: Enterprise Instrumentation -- Error 1720. There is a problem with
this Windows Installer package. A script required for this install to
complete could not be run. Contact your support personnel or package vendor.
Custom action IsDotNetInstalled script error -2146827859, Microsoft JScript
runtime error: Automation server can't create object Line 1, Column 1,
andEvent Type:    Error
Event Source:    MsiInstaller
Event Category:    None
Event ID:    11722
Date:        10/2/2003
Time:        4:39:03 PM
User:        N/A
Computer:    BILLING1
Description:
Product: Enterprise Instrumentation -- Error 1722. There is a problem with
this Windows Installer package. A program run as part of the setup did not
finish as expected. Contact your support personnel or package vendor.
Action RegAsm11, location: C:\WINNT\Installer\MSI46C.tmp, command: regasm
"C:\Program Files\Microsoft Enterprise Instrumentation\Bin"

Reply to this Message

Mike Hayton [MS] - 02 Nov 2003 17:12 GMT

Jim,

I have seen this sort of error 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. I've added more tests that are probably necessary, but it
should reduce the number of roundtrips required 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. 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
box with the list of processes running on the machine! )

Thanks

Mike

--------------------

| We have isolated a problem down on installing EIF on Windows 2000 systems to
| those that have currently or have had Crystal Reports 8.0 installed. It
[quoted text clipped - 37 lines]
| Action RegAsm11, location: C:\WINNT\Installer\MSI46C.tmp, command: regasm
| "C:\Program Files\Microsoft Enterprise Instrumentation\Bin"

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

Reply to this Message

Udi Dahan - 15 Nov 2003 21:45 GMT

I have had this exact same problem, please let me know
what resolution there is.

Thank you.
Udi Dahan

>-----Original Message-----
>Jim,
[quoted text clipped - 13 lines]
>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)
[quoted text clipped - 81 lines]
>| Action RegAsm11, location: C:\WINNT\Installer\MSI46C.tmp, command: regasm
>| "C:\Program Files\Microsoft Enterprise Instrumentation\Bin"

Reply to this Message

Mike Hayton [MS] - 17 Nov 2003 16:51 GMT

Hi there,

It really depends on what the tests below show is corrupt.
Generally it involves re-registering parts of WMI.

If you still have the problem, can you perform the below steps and reply
with them attached.

Thanks

Mike

--------------------

| I have had this exact same problem, please let me know
| what resolution there is.
[quoted text clipped - 144 lines]
| >
| >.

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

Reply to this Message

Harsh Kundra - 24 Nov 2003 02:45 GMT

Did this issue ever get resolved? I am having the exact
same problem as Jim had. I understand that I need to re-
register part of WMI - can someone please explain how to
do that?

Many thanks,
Harsh

>-----Original Message-----
>Jim,
[quoted text clipped - 13 lines]
>3. Execute the MSI install with the full logging enabled
>

EnterpriseInstrumentation.exe /c:"msiexec.exe /q /l*v

Reply to this Message

Mike Hayton [MS] - 27 Nov 2003 07:36 GMT

The general way to reregister WMI is to do the following 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 if you have any more problems.

Mike

--------------------

| Did this issue ever get resolved? I am having the exact
| same problem as Jim had. I understand that I need to re-
[quoted text clipped - 147 lines]
| >
| >.

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

Reply to this Message

bala murugan - 18 Nov 2004 14:13 GMT

Hi,

The script engine is not running. This means you are having a old version of SCRRUN.DLL in your system. Check the version of SCRRUN.DLL. If it is 5.1.0, you will not be able to run this EXE. You need to get SCRRUN.DLL version 5.6.0.

Thanks,
Balamurugan M.N

Reply to this Message

Problems installing EIF on systems with Crystal Reports 8.0 (currently or previously installed)

Free Magazines