Failed to get EA::IDualApp interface [0x80029c4a]

[ngong]

When creating a new JavaScript script some default statements are generated.
When running that script without any changes it should prompt the user with "This script does not support items of this type.".
Instead in EA-17 it output on my computer "Failed to get EA::IDualApp interface [0x80029c4a]" in the System Output window.

What is wrong with my installation?

[Paolo F Cantoni]

When creating a new JavaScript script, some default statements are generated.
When running that script without any changes, it should prompt the user with "This script does not support items of this type.".
Instead, in EA-17, it output on my computer "Failed to get EA::IDualApp interface [0x80029c4a]" in the System Output window.

What is wrong with my installation?

Hi Rolf,
I can confirm that scripting "ist KAPUT!" in v1704, NONE of my scripts work!   VBScript, JScript or Javascript!
They all fail with your Failed to get EA::IDualApp interface message!
Needs FIXING IMMEDIATELY!
I've had to revert to 1703.
Please report a defect also!

Reported,
Paolo

[Takeshi K]

If you use 64bit version of EA and your machine has the following Registry key, renaming it to like 'win32_bak' (to be able to revert) and restart Windows might help you.

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{64FB2BF4-9EFA-11D2-8307-C45586000000}\2.a\0\win32

[Paolo F Cantoni]

If you use 64bit version of EA and your machine has the following Registry key, renaming it to like 'win32_bak' (to be able to revert) and restart Windows might help you.

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{64FB2BF4-9EFA-11D2-8307-C45586000000}\2.a\0\win32

Thanks, Takeshi-San,

We had already determined that installing the 32-bit version of 1703 would enable scripting on 32-bit 1704, but the 64-bit scripting remained elusive.

Sparxians, ensure the fix is in...  And you have a new regression test...

Paolo

[Takeshi K]

Hi Paolo-san,

I am sorry that my information could not solve your problem.

When the 'win32' key exists and EA 32bit version is NOT installed, Windows cannot find the EA.* COM Objects and this causes the error. Now when installing EA 64bit, the installer creates the 'win64' key and I think it works fine. (i.e., on a fresh Windows environment, I guess that the script with the build 1704 64bit could work fine.)

Anyway, on all my machines, currently the script on EA 64bit works fine. So there might be another reason/condition.

[Paolo F Cantoni]

Hi Paolo-san,

I am sorry that my information could not solve your problem.

When the 'win32' key exists and the EA 32bit version is NOT installed, Windows cannot find the EA.* COM Objects, which causes the error. Now, when installing EA 64bit, the installer creates the 'win64' key, and I think it works fine. (i.e., on a fresh Windows environment, I guess that the script with the build 1704 64bit could work fine.)

Anyway, the script on EA 64bit currently works fine on all my machines, so there might be another reason/condition.

I'm sorry, Takeshi-san, I did not explain myself well.  Your fix DID solve my problem!  I was trying to say that we'd got the 1704 32-bit variant working by installing 1703 in addition.  But the 64-bit did not work until we put in the fix you suggested.

Thanks for the further explanation.  It is most useful.

FWIW, we have multiple versions of both 64-bit and 32-bit variants installed on the same machine, each in its own folder. We have v17, v16, and v15 installed for testing and regression purposes.

Paolo

[Takeshi K]

Hi Paolo,

Glad to hear you solved the problem!