Error Code: -5009 : 0x80040702 after updating to IS 2010 SP1

[Reureu]

Hi,

Since we updated to IS 2010 and the corresponding SAB to SP1, the following error occurs when launching a pure InstallScript setup on Windows 2000:

Error Code: -5009 : 0x80040702
Error Information:
>Kernel\ObjectWrapper.cpp (162)
>Kernel\ObjectWrapper.cpp (557)
>Kernel\Component.cpp (1275)
>Kernel\CABFile.cpp (436)
>SetupNew\setup.cpp (831)
PAPP:
PVENDOR:MyCompany
PGUID:01B6CBAA-D707-4F1D-BFC8-7D9D76FA9CAB
$16.0.0.400PAK
@Windows 2000 Service Pack 4 (2195)
IE Version: 6.0.2800.1106

The same setup built with IS 2010 without SP1 works fine.

Any idea? Any workaround?

I have found many outdated posts related to similar problems, and none of the proposed solution actually worked.

Regards

[joshstechnij]

A hotfix has been provided in KB Q206628 that should resolve this behavior.

[Mrunmayee]

Thanks joshstechnij,

The hotfix provided solved my problem 🙂

--Mrunmayee

[Charlie_Phelps]

Reureu: I am getting an identical looking error on a Windows Server 2000 box. I am wondering if/how you resolved this. Thank you!

[Charlie_Phelps]

I am hopeful that you have resolvedd this and can share your resolution! Thanks.

Reureu wrote:
Hi,

Since we updated to IS 2010 and the corresponding SAB to SP1, the following error occurs when launching a pure InstallScript setup on Windows 2000:



The same setup built with IS 2010 without SP1 works fine.

Any idea? Any workaround?

I have found many outdated posts related to similar problems, and none of the proposed solution actually worked.

Regards

[joshstechnij]

If you are seeing this behavior after building with IS 2010 SP1, the hotfix mentioned earlier in KB Q206628 needs to be applied to resolve the behavior seen on Windows 2000 machines. If the behavior still occurs after correctly applying the hotfix, then another issue is occurring that we would need to reproduce.

[Reureu]

@Charlie Phelps: I think Josh has already answered your question.

Regard
Reureu

[Charlie_Phelps]

Josh,

We are calling ISCmdBld.exe from a build script to build an installation exe to deploy on on a Windows Server 2000 box.

The installation exe works fine on Windows XP and on Windows Server 2003.

However, we receive error code -5009, 0x80040702 when we try to run the installation exe on Windows Server 2000. (When it fails, I see the same c++ line numbers and classes that I see in the original post above.)

Does our build box (where ISCmdBld.exe resides) need to have SP1, the hotfix, and/or some other update installed if we want to use ISCmdBld.exe to build our installation exe for deployment on a Windows Server 2000 box?

Many thanks!

[joshstechnij]

After SP1 is installed, the hotfix from the previously mentioned KB needs to be applied in order to resolve this runtime error on Windows 2000 machines. This applies to either a machine using the IDE or a machine that is using the standalone build.

[Charlie_Phelps]

...thanks!