When CATIA or any application is executed from a Network share like \\server\share\folder\app.exe,
AppUsage and Recorder.exe are unable to recognize the Application details which are being read from
the version information embedded in the exe. There were two problems:

1. An error in the parsing code which failed to parse the file paths with the above mentioned
format. This has been fixed.

2. Permission issues. Since AppUsage runs under LOCALSYSTEM account, it is unable to access the
version information by opening the file. This is because when a user connects to a network share,
only applications that run under that user's session will be able to access the network share.
Since this is the way Windows works and is caused by the security constraints imposed by the
Operating system, the correct way to workaround this, is to run OpeniT Client under an user account,
that has the required permissions to access the network share from which the application is being
executed. This user account should also have administrative and debug privileges as AppUsage needs
this to function properly.
Another alternative is to install the application locally on the hosts.

If AppUsage misses the stop event of a process, that process will continue to be logged as running.
This version, after logging process data, checks and removes processes that are not running anymore.

But this means AppUsage Elapsed time can be inaccurate by 1 hour (or a period equal to log interval)
in the worst case for any process whose stop event is missed.

Handling wrong start/stop time reported by the Native Event Logger has been improved.

This patch fixes some errors caused by the event tracer reporting wrong start
and end times. It also fixes a crash caused during logging data and a crash
that occured when
performance monitoring was turned on.
Visual C++ 2005 SP1 Redistributable Package (x86) required for Appusage is included in Patch 1094.

This patch fixes some errors caused by the event tracer reporting wrong start
and end times. It also fixes a crash caused during logging data and a crash that occured when
performance monitoring was turned on.

AppUsage was crashing on some hosts when opening the appusage_counters file.
This has been fixed and execption handling has been improved.