When logging a case, it is important to accurately report the conditions under which the problem occurred. Details on relevant information will be supplied on short term. One major aspect is discussed below since it can help in judging that a severe problem occurred.
The OnePoint Diagnostics portal (running as part of the browser) is built in Java (so using the Java Virtual Machine). In case of malfunctioning Java code, the JVM often generates a stack trace. When the JVM detects a severe error that is not covered by the OnePoint Diagnostics code itself, the requested action (resulting in the severe error) is stopped and nothing seems to happen on your screen. Repeating the action (such as pressing a button) will over and over result in the same error without effect on your screen. Next to details about the type of operation being executed, also this stack trace of the JVM is a vital piece of information.
To check if such an error occurred, the Java console logic has to be enabled in your browser. Below is the screen shot belonging to Internet Explorer 6.0 that shows where to enable the Java console. The Internet Options window can be activated via the Tools option on the menu bar of Internet Explorer. Note that enabling the Java console requires a restart of your browser session.
To view the Java console, go to the View option on the menu bar of Internet Explorer and click Java Console. A new window with title "Java Console" will be opened. While starting up the OnePoint Diagnostics portal, two events are reported already which can be ignored. You can recognize the end of the two events by looking for the "Swing: checked access to system event queue". Any information thereafter possibly is related to unexpected behavior of the OnePoint Diagnostics portal. Select the text in the Java console and copy it into the information explaining the problem.