Solved Problems in OnePoint Diagnostics 3.4.0001

1. New Digital Certificates for Java (valid until May 2008) have been included.
2. A problem in the Java code when reading files retrieved from the server could lead to unexpected results or even a hang-up situation. This problem was noticed while using the connection wizard (preparing a Baan connection) when a large amount of Baan companies was existing.
3. When starting server components on Unix type systems, stdin is redirected to /dev/null ensuring that no activated process accidentally can read from stdin which would cause a hang-up in the involved question.
4. Reference to the old SSA name have been removed and adjusted to Infor whenever applicable. This specifically applies to:
   • The logon and about window are changed to Infor style.
   • References to old mail addresses (those ending with "ssaglobal.com") are adjusted.
   • The name of the ERP LN scan is automatically adjusted when the portal is opened.

Solved Problems in OnePoint Diagnostics 3.3.0003

When the hostname on which the OnePoint Diagsnostics server is running could not be resolved, an internal conflict in the administration was likely to occur resulting in not being able to start a service scan. This bad behavior can be observed after creating a configuration for a service and looking at this prepared configuration. When server names are listed (left most column) everything is in good shape whereas IP addresses illustrate that the name resolution problem occurred.

Solved Problems in OnePoint Diagnostics 3.3.0002

Some questions could generate output files with special characters causing problem during processing at the intelligence center.
Possible effect of this problem was that the output of the scan could not be processed at all and hence no report could be generated.
The update to OnePoint Diagnostics 3.3.0002 solves this problem, at least for the questions observed to suffer from this problem.

Solved Problems in OnePoint Diagnostics 3.3.0001

1. When a proxy server was defined and active for the browser, remote server handling could fail due to internal OnePoint Diagnostics configuraton settings or due to firewall settings. All requests to and from a remote server are now handled internally by OnePoint Diagnostics not requiring any longer the proxy setting of the browser.
   
   
2. When a new portingset of ERP LN (formerly Baan) was installed, the associated OnePoint Diagnostics connector failed to connect which has been resolved.
   
   
3. The OnePoint Diagsnostics Informix connector would fail if the informixserver and informix client software would have been installed in different directories. It is now possible to define two different directories in the profile of the Informix connector.
   
   
4. The OnePoint Diagsnostics service on Windows systems could timeout during startup phase of the OnePoint Diagsnostics Portal; this was most likely to happen on slow systems. The service startup method has been changed in such a way that this timeout should no longer occur.
   
   
5. On slow systems, the internal test connection timeout value of 45 second has proven to be to low to finish completing the connection test. The internal timeout has been increased to a value of 120 seconds to solve this problem.