Work arounds for remaining bugs / issues in ConsoleWorks 3.7-0u3

From TDiWiki

We realize not all customers can upgrade to ConsoleWorks 4.x on our schedule. For the few remaining issues in ConsoleWorks 3.7-0u3 we offer these workarounds: (The bulleted items indicate that these issues have been resolved in ConsoleWorks 4.1-0u2)

* Windows Event Forwarder (WEF) now supports all known message formats, so it no longer fails when it encounters an unsupported format.

We can still provide you with the updated WEF via this URL http://support2.tditx.com/support/evaluations/dl/winntagt.exe

Your TDI provided Username and Password will be required. The new WEF will run with prior versions of ConsoleWorks. See your 3.7 users guide for installation instructions.

* A socket leak was discovered and closed.

N/A

* ConsoleWorks no longer crashes while compiling reports that include special characters.

Avoid creating reports that use special characters as part of your search criteria

* Several memory leaks in Reports have been closed.

Keep an eye on ConsoleWorks memory usage and restart ConsoleWorks when it gets too high

* ConsoleWorks no longer crashes when running a Console Messages report with a Display Lines Below value greater than zero.

Avoid running the Console Messages report with 'lines below' set to anything above zero.

* Java-Caused Console Disconnects Fixed

The bug introduced by Java™ release 1.6.0_10 that caused Console connections to open and then immediately close has been fixed.

- Roll back to a previously supported version of Java. The version prior to 1.6.0_10 that worked successfully was 1.6.0_07

- Try using the CWTProx program to enable using a 3rd party terminal emulator of your choice, such as Reflection, PuTTy, etc. This will remove Java from the problem entirely. Instructions can be found here: http://support2.tditx.com/conwrks/third.pdf

- Use the older version of the Java Terminal Emulator: Do this by going to the >Change >Connection Settings menu and selecting the “Use the Java 1.1x run-time environment…”

This method requires right clicking on the Terminal Icon, or connect link, and selecting “Open in New Window”.