[Allen Gaminde]

When I try to launch the Web 2.0 browser by going to the MyEclipse Web 2.0 perspective and clicking the Web 2.0 Browser icon on the toolbar, I receive an alert box with following text –

The procedure entry point ?Length@nsACString@@QBEIXZ could not be located in the dynamic link library xpcom.dll

A Web2.0 Browser tab appears. If I try to launch the browser again, a new tab appears and I receive the following text “in the new browser tab’s window”

Unable to create this part due to an internal error. Reason for the failure: COM object method returns error code: 0x80040154

Clicking the available “Details” button gives me the following:

com.jniwrapper.xpcom.ComException: COM object method returns error code: 0x80040154
at com.jniwrapper.xpcom.mozilla.impl.NsISupportsImpl.createComException(NsISupportsImpl.java:157)
at com.jniwrapper.abstractcom.impl.AbstractComImpl.doInvokeStandardVirtualMethod(AbstractComImpl.java:402)
at com.jniwrapper.xpcom.mozilla.impl.NsISupportsImpl.invokeStandardVirtualMethod(NsISupportsImpl.java:86)
at com.jniwrapper.xpcom.mozilla.xpcom_components.impl.NsIComponentManagerImpl.createInstanceByContractID(NsIComponentManagerImpl.java:91)
at com.genuitec.javascript.debug.ui.BrowserCanvas.createBrowser(BrowserCanvas.java:74)
at com.genuitec.javascript.debug.ui.BrowserCanvas.<init>(BrowserCanvas.java:57)
at com.genuitec.javascript.debug.ui.SWTBrowserChromeDelegate.createBrowserArea(SWTBrowserChromeDelegate.java:356)
at com.genuitec.javascript.debug.ui.SWTBrowserChromeDelegate.<init>(SWTBrowserChromeDelegate.java:120)
at com.genuitec.javascript.debug.ui.editor.BrowserEditor.createPartControl(BrowserEditor.java:82)
at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:609)
at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:384)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:552)
at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:223)
at org.eclipse.ui.internal.WorkbenchPage.makeActiveEditor(WorkbenchPage.java:1115)
at org.eclipse.ui.internal.WorkbenchPage.updateActivePart(WorkbenchPage.java:1073)
at org.eclipse.ui.internal.WorkbenchPage.partAdded(WorkbenchPage.java:1422)
at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:205)
at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:758)
at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:665)
at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:628)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2360)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2295)
at org.eclipse.ui.internal.WorkbenchPage.access$9(WorkbenchPage.java:2287)
at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:2273)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2268)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2241)
at com.genuitec.javascript.debug.JSDebugPlugin.createBrowserEditor(JSDebugPlugin.java:222)
at com.genuitec.eclipse.web20.action.OpenWeb20BrowserAction.run(OpenWeb20BrowserAction.java:45)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:246)
at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:223)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:538)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:441)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3125)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2758)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334)
at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
at org.eclipse.core.launcher.Main.run(Main.java:973)
at org.eclipse.core.launcher.Main.main(Main.java:948)

My configuration is –

*** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.4.2_10

*** MyEclipse details:
MyEclipse Enterprise Workbench

Version: 4.1.0 GA
Build id: 20060122-4.1-GA

*** Eclipse details:
Eclipse SDK

Version: 3.1.2
Build id: M20060118-1600

Eclipse Platform

Version: 3.1.2
Build id: M20060118-1600

Eclipse RCP

Version: 3.1.2
Build id: M20060118-1600

Eclipse Java Development Tools

Version: 3.1.2
Build id: M20060118-1600

Eclipse Plug-in Development Environment

Version: 3.1.2
Build id: M20060118-1600

Eclipse Project SDK

Version: 3.1.2
Build id: M20060118-1600

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-launcher
C:\Eclipse\eclipse\eclipse.exe
-name
Eclipse
-showsplash
600
-exitdata
490_98
-vm

Basically, this is a fresh install of Eclipse 3.1.2 and a fresh install of MyEclipse 4.1.0 GA.

thanks,
Allen Gaminde

[Greg]

Allen,

Sorry your having trouble. Do you have any copies of Mozilla installed on your system? Are there any mozilla dlls in your default library path. For instance, could you check in your C:\windows\system and c:\windows\system32 directory for mozilla dlls?

Take a look at this post below. In this topic, the user figured out their problem by removing the offending mozilla libraries in the system32 directory.
http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-11104-highlight-nspr+dll.html

[Allen Gaminde]

Greg,

Yes, I came across the post mentioned above while trying to figure out this problem. However, I do not have those DLLs in either /windows/system or /windows/system32. I do have Mozilla Firefox installed and those DLLs are in the firefox directory. In addition, I came across the same files in a few other places – Alias Maya (a 3D graphics package) contains all of the DLLs mentioned in the post and the my HP Deskjet Assistant install (I have a HP printer) contains a subset of those DLLs (to include nspr4.dll). And, of course, they are in the MyEclipse plugin.

Any other ideas?

I completely removed eclipse and myeclipse and installed Eclipse 3.1.1 and MyEclipse 4.1.0 GA (just in case this was an Eclipse 3.1.2 issue) but that had no effect. I still have the same results whether eclipse 3.1.2 or 3.1.1.

thanks,
Allen

[Greg]

To the best of my knowledge, what is happening is that when our web20 browser component requests a function that requires the xpcom.dll file, your system is loading another xpcom.dll file from somewhere else on your harddrive, and not the one that is located in our plugin. I am going to research a way to confirm this for you and I’ll get back to you as soon as we have more info. But in the mean time, could you perform that full system search for xpcom.dll files and let me know what you find? Thanks.

[Allen Gaminde]

A full search for xpcom.dll yields the following results:

c:\Program Files\Mozilla Firefox\
c:\Alias\Maya 6.0\bin\
c:\MyEclipse\eclipse\plugins\com.genuitec.javascript.debug.mozilla_4.1.0\XPCOM\mozilla\
c:\hp\drivers\printers\program files\Hewlett-Packard\hp deskjet assistant\bin\

Hope that helps.

thanks,
Allen

[Greg]

Allen,

I was talking with Brian, another support guy, about this topic and your dll problem. He suggested that for all of those xpcom.dll files that you have on your system, just temporarily rename them to something else like “xpcom.dll.bak”. Rename all of them except for the one in our plugin 🙂

Then try to open the browser and see if it is indeed a dll loading issue. If the browser loads correctly, then we know that something on your system is making those other xpcom.dll files load before ours. Then you can rename your other xpcom.dll files back so you don’t break those apps and then we can go from there.

[Allen Gaminde]

Okay – it’s more than just xpcom.dll.

I started with renaming xpcom.dll in each location.
Then, I tried renaming xpcom_compat.dll since new errors were generated with just xpcom.dll renamed.
Then I received errors on nprs4.dll. At that point, rather than renaming each file as errors were generated, I figured I would just rename the parent directories since this seems to be tied to the Window’s Registry.
After renaming each parent directory where any Mozilla files were located, the browser launched without a problem.

Next, I am going to rename each directory, one at a time, back to its regular name and try again to launch the browser. I am going to take a look at the registry too to try and figure something out. Could be there’s no relationship, but I thought I would take a look anyway.

[Greg]

Interesting… You have uncovered some very useful information. It seems that some of those programs have added their library directories into the system library path of some type. If you can find that out for sure and determine how it is doing it, that would be great. We will do some more research on our side as well. Thanks for helping us run down this problem.

[Allen Gaminde]

Okay – I started with the obvious culprit (Maya) and decided to go ahead and rename the HP and Mozilla folders back to their original name and . . . great, the browser still launched. I figured it was very unlikely that I am the only person using Firefox and/or an HP printer.

I figured it must be the system path (as you pointed out above). Looking at the system info/environment variables and Maya was the only one of the four (firefox, hp, maya, myeclipse) in the system path.

I removed the path entry for Maya, rebooted, checked Maya to make sure it and all of its add-ons worked fine without a path entry (it did) and fired up MyEclipse again – the browser worked fine.

Thanks for your help. In the end, the solution seems kinda obvious but it was still fun tracking it down.

take care,
Allen

[Greg]

Good deal, I’m glad you got it working. I have stickied this post to help others who have the same problem find this topic quickly.

[Author]

Posts