Symptom:
If an iConsole search returns an event containing Unicode event metadata (such as Chinese, Japanese, Korean and Russian characters), this metadata does not display correctly. Instead, these characters are replaced with question marks. For example, if the trigger name or search text was defined using Korean characters in the user policy, these items display as '????' strings in the iConsole search results page.
In addition, if a reviewer searches for events by Unicode trigger name, the search fails to return events where the Unicode metadata was not captured. For example, an email trigger has a Korean trigger name. When this trigger fires on a computer running an English version of Windows, the email is captured but the trigger name is lost. Consequently, when a reviewer searches for emails associated with this trigger name, the search fails to find the email captured on this computer.
Note: This problem is rare. It primarily affects events captured on endpoint computers running a Western version of Windows and where policy triggers include settings that use Unicode characters, such as Chinese, Japanese, Korean or Russian text.
Solution:
Implement Unicode support on all CA DataMinder endpoint computers running non-double byte character set versions of Windows (that is, non-DBCS Windows) and which are likely to capture events containing Unicode characters. For example, this applies to Japanese email trigger details captured on a computer running an English version of Windows.
To implement Unicode support:
net stop wgninfra
db.charset=UTF-8
net start wgninfra
Important! Do not make this change to startup.properties on CA DataMinder computers running Japanese, Korean or Chinese versions of Windows.
|
Copyright © 2014 CA.
All rights reserved.
|
|