Saturday, June 21, 2014

xPages in Notes client fails with XPCOM error 0xcf1f30001 after upgrade to Notes 9.0.1

I have upgraded my Notes Client from 8.5.3 FP2 to 9.0.1 FP1 and after this upgrade no xPage based application works in the notes client. In the trace of the client i found an "CLPDN0031E: org.eclipse.swt.SWTError: XPCOM error 0xc1f30001"  error with the stack trace:

org.eclipse.swt.SWTError: XPCOM error 0xc1f30001 at org.eclipse.swt.browser.Mozilla.error(Mozilla.java:2663) at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:732) at org.eclipse.swt.browser.Browser.<init>(Browser.java:99)......

Actually no XULRunner (Mozilla rendering engine which is used by XPiNC) based functionality of the client is working. I have analyzed the problem and found that the rcpinstall.properties file in the workspace does not point to the XULRunner plugin which has been updated for Notes 9.0.1.

To solve this problem close every instance of your Notes client and open the rcpinstall.properties file in the "workspace\.config" path in your data directory with your favorite editor (notepad.exe will work) and change the line



-Dorg.eclipse.swt.browser.XULRunnerPath=${rcp.home}/rcp/eclipse/plugins/com.ibm.rcp.xulrunner.runtime.win32.x86_9.0.1.20131002-1404/xulrunner

to

-Dorg.eclipse.swt.browser.XULRunnerPath=${rcp.home}/rcp/eclipse/plugins/com.ibm.rcp.xulrunner.runtime.win32.x86_9.0.1.20140318-1700/xulrunner

Maybe IBM will provide Fix Packs with newer versions of XULRunner in the Future. So maybe it is worth to double check if the above path is still correct. The easiest way to find the version number is to Open the "Info" Dialog of Notes and choose "Plugin Details" and search for the XULRunner plugin. Then use the version number shown for the change in the rcpinstall.properties.


After the correction of the rcpinstall.properties file xPages in Notes should work again.

No comments:

Post a Comment

ad