Notes.exe won't show interface

HCL Domino Domino Forum
1

Hello, I thought I would use the holiday slow time to upgrade from 8.02 to 8.5.1. There were some errors during install and afterward when I start notes, I am prompted for my credentials and then after some loading, the window disappears, never to return. A nlnotes.exe process is however running. So I use nsd -kill as I am so familiar with to stop notes. The only thing that lets me it to check my email now is running nlnotes.exe instead of notes.exe.

The error during install was:

Partial installation and setup occurred. Below are the details about the features that failed to set up.

CWPPR0080W: Feature com.ibm.langware.v5.dic.da_DK.feature.5.3.0.0-200706251329 was not found on the update site.

(there were to other very similar lines)

Unexpected results had occurred during the provisioning operation.

And from the trace-log-0.xml file:

2009-12-22T10:37:32.537-08:00 CONFIG

eclipse.buildId=20090925-1604

java.fullversion=J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr4ifx-20090729_39787 (JIT enabled, AOT enabled)

J9VM - 20090729_039787_lHdSMr

JIT - r9_20090213_2028

GC - 20090729_AA

BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US

Framework arguments: -dir ltr -NPARAMS /authenticate -RPARAMS -plugincustomization C:/notes/framework/rcp/plugin_customization.ini

Command-line arguments: -os win32 -ws win32 -arch x86 -dir ltr -NPARAMS /authenticate -RPARAMS -data C:\notes\data\workspace -plugincustomization C:/notes/framework/rcp/plugin_customization.ini

com.ibm.rcp.core.internal.logger.frameworkhook	com.ibm.rcp.core.internal.logger.frameworkhook .writeSession	0

2009-12-22T10:37:32.584-08:00 SEVERE

Application error

java.lang.RuntimeException: No application id has been found.

at org.eclipse.equinox.internal.app.EclipseAppContainer.startDefaultApp(Unknown Source)



at org.eclipse.equinox.internal.app.MainApplicationLauncher.run(Unknown Source)



at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Unknown Source)



at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Unknown Source)



at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)



at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)



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.equinox.launcher.Main.invokeFramework(Unknown Source)



at org.eclipse.equinox.launcher.Main.basicRun(Unknown Source)



at org.eclipse.equinox.launcher.Main.run(Unknown Source)



at com.ibm.rcp.core.internal.launcher.Main.startLaunch(Unknown Source)



at com.ibm.rcp.core.internal.launcher.Main.main(Unknown Source)



at com.ibm.rcp.core.internal.launcher.Main.run(Unknown Source)





org.eclipse.osgi	 	1
2

Subject: I hope this will help you

http://www-10.lotus.com/ldd/nd85forum.nsf/5f27803bba85d8e285256bf10054620d/fb9042bf357522878525764f0043b45f?OpenDocument

http://www-10.lotus.com/ldd/nd85forum.nsf/DateAllThreadedWeb/3cdbd1580e6d4e7f852575690030bde7?OpenDocument

3

Subject: Same issue here - Fixed by removing JAVA… environment vars

We ran into the same issue. All of my effected users are developers. The Notes Basic version worked fine.

After some searching I found this SPR# SJOB7TYNYW…

(Sign-in required)

…that references that some JAVA related environment variables that would cause issues with the Eclipse version of Notes.

I found that they these users all had QuickTest Pro v10.0 application from HP which adds a number of “JAVA…” system environment variables. One entry in particular was causing issues with Eclipse which is used for the Standard client. It appears to intecept java calls that are required by the standard client.

We can resolve this issue by removing the variable “JAVA_TOOL_OPTIONS” entirely or by just deleting the variable’s value “-agentlib:jvmhook” by change it to blank. When this variable is removed or is set to nothing the standard client will start properly. This change did not appear to cause issues with the HP tool.