WebHelp 5.10.001 JavaScript runtime error

[will3m]

Using WebHelp 5.10.001 (Adobe RoboHelp 11, WebHelp 5.50) and am receiving the following error:

JavaScript runtime error: Object doesn't support property or method 'RegisterListener'

The above occurs on js file: whproxy.js

function RegisterListener(framename, nMessageId) {

    var wSP = getStubPage();

    if (wSP && wSP != this) {

        //return wSP.RegisterListener(framename, nMessageId);

    }

    else {

        return false;

    }

}

So I commented it out to avoid the error being thrown. What is the fix for this?

[RajeevAdobe]

Did you test the output on any other browser like Google chrome and Firefox?

Is it happen with a specific project or any project you create in Robohelp 11.

Regards,

Rajeev.

[will3m]

Yep - tried in IE, Chrome and Firefox. The error is thrown all the time regardless of browser so to hide it I commented out the code. That's like a bandage and I'd prefer to find a valid solution.

[RajeevAdobe]

Is it happen with a specific project or any project you create in Robohelp 11.

Regards,

Rajeev.

[will3m]

any project; granted we have one main but did spin up another smaller project.

[RajeevAdobe]

Could you please check that Robohelp 11 is updated to the latest update and also try to clear the cache and temp files from the machine and test the output.

Also could you please also check to login with any other user account in your machine which has the complete admin rights on it.

Is it possible for you to share the generated output with us or the project.

Regards,

Rajeev.

[will3m]

I'll go through what you've suggested and the account used is a local admin; however, I can't share the output.

[Willam_van_Weelden]

Can you perhaps create a small sample project with one or two problems that exhibit this issue? You can share it with us if you just add some lorem ipsum on the pages, right?

[will3m]

Hey - I was troubleshooting this on the behalf of another - whom has since told me the issue has been fixed. All that I know is that the broken page was done and the issue is no longer present. Not sure what was exactly completed - perhaps a rebuild?? This can be closed out.

[Willam_van_Weelden · Accepted solution]

Very strange. Thanks for letting us know that it was fixed.

[will3m]

I agree