Known Problems in OnePoint Diagnostics 3.3.0001.

  1. Bad Output Characters
    Under some conditions malformed characters can be observed when viewing question output via the OnePoint Diagnostics portal. It has been observed to occur via Microsoft JVM for characters in the Latin Extended character set. For Sun JVM this might occur for Armenian characters. Processing at the intelligence center doesn't suffer from these problems.

  2. Uninstall Old Version
    The OnePoint Diagnostics 3.3 portal refuses to install on Windows when an older version is observed to be present. This older OnePoint Diagnostics version needs to be manually uninstalled first. Either use the Add/Delete Programs option from the Control Panel or execute the old OnePoint Diagnostics executable once more which will trigger the uninstall procedure.

  3. Potential Browser Problem
    It has been observed that using Firefox as browser initially can fail. The problem occurs only now and than. Logic has been added to detect the problem and generate a recognizable error message. See the example below. The only known recovery procedure is to terminate the browser and start it once more.

          

  4. Logout Forced
    It has been observed that using Firefox as browser initially can fail. The problem occurs only sometimes during login to the OnePoint Diagnostics portal. Logic has been added to detect this specific problem and generate a recognizable error message. After confirming this specific message, the portal forces a logout and another login is required.

Known Problems in OnePoint Diagnostics 3.2.0003.

An overview is given of problems that occurred in the OnePoint Diagnostics 3.2.0002 version. Since the availability of OnePoint Diagnostics 3.2.0003 no further complaints and/or details have been received regarding these problems. The information is repeated as guideline when some problem still occurs.

  1. Malformed Output Container
    Occasionally output containers with scan results have been received by the Intelligence Center for processing by the Expert System that included an invalid XML file. Only after manual interaction these output containers where suitable for further processing. Logic has been included to prevent these bad containers.
    Since reproduction of this specific problem has failed so far, it is not guaranteed that the cause of the problem is fully addressed. A pop-up message is generated most likely with the text:

         Internal Error [server <name of a server> not found]

    When this problem occurs, you are kindly requested to view the Java console and report all relevant details: both a copy of the data on the Java console as well as the contents of the configuration being used.

  2. Locked Help Window
    When the new button "Release Notes" is used by user admin (see New Features) the Help window is displayed. When using a SUN Java run-time version, the Help window (started via the "Release Notes" button) sometimes seems to be blocked. One example is an active Java console at the same time. Also the Java console cannot be accessed at that time.
    Simply close the Help window and view the Release Notes via another method such as using the Help button on the toolbar.

  3. Reporting Problems: use the Java Console

    In case of problems possibly information is present on the Java console that can help to understand the problem. Use the information on the Java console when reporting whenever applicable.

    While using Internet Explorer the Java console typically needs to be enabled beforehand. Select the Tools entry from the menu bar, choose Internet Options and select the Advanced TAB. Search for item Microsoft VM and check entry "Java console enabled". Apply a restart of IE when this item was not yet checked.
    Before connecting to the OnePoint Diagnostics portal, select the View entry from the menu bar and select "Java Console".
    Connect to the portal again and repeat the procedure of collecting output.

    The Java console can be activated independently: either the Java plug-in is visible on the system tray and the Java console can be activated via a right-mouse click or the Java console can be enabled via the Control Panel.