Fixes are available
APAR status
Closed as program error.
Error description
Abstract: Agentless Monitoring Agent for Windows Operating system cannot be configured on Japanese/Chinese DBCS systems. Approver: CM Environment: Windows ONLY and seems to occur when Languages that use Double Byte Character sets are installed . The configur ation dialog box appears in the language the customer i s using, but after configuration the Agent will not s tart. So far Japanese and Chinese have been verified to fail. The error appeared in ITM release 6.2.1 but may exist in other releases. The error appeared for the Win dowless Agent but may apply to other agents as well. Problem Description: On Windows when the Agentless Monitoring for Windows Op erating System is installed and a language pack is inst alled to support a Double Byte Language (Japanese or Ch inese) configuring the agent appears in the language of choice, but after configuration the Agent will not star t.A popup appears with the following text: KCICF5100E - Unable to start service. What should occur is the Agent should start and no popup should appear. On some system s the popup may only contain the error message number w ith no text in the correct language. Detailed Recreation Procedure: To recreate: 1) Install TEMS, TEPS using C1MP6EN with the default se ttings on an Win2k3 box. 2) Install "Agentless Monitoring for Windows Operating System" using C1MQ0EN with the default settings. 3) Install Japanese Language Pack or any DBCS Language as default for the workstation. 4) From MTEMS, right click "Monitoring Agent for Agentl ess Windows OS" and select "Advanced"-"Configure Adv anced".Then specify the following values. -Host name or IP Address for TEMS : TEMS_Name --> (Single Byte) -Port number for TEMS : 1918 --> (Single Byte) -Connection Type: Windows API Connection --> "Connection" is Double Byte. But that was just selected from pull down menu. -Remote Windows Password: This is filled with Single Byte -Managed System Name : ProperName --> (Single Byte) -Remote Windows host : Name --> (Single Byte) -Remote Windows Domain UserName : Administrator --> (Single Byte) -Advanced : Select a section to override values --> This string is Double Byte. But was just selected from pull down menu. Click "OK" to complete the configuration. It looks like that obviously some DBCS characters are used during the configuration.However, they were selected from the pull down menu and cannot be changed from DBCS to SBCS. 5) After configuring it, from MTEMS, right click "Monitorin g Agent for Agentless Windows OS" and select "Start" 6) The following error will appear and the Agent will not start. KCICF5100E - Unable to start service Related Files and Output: The agent cfg file has mixed DBCS and SBCS codes in the same file.
Local fix
Remove the language pack and configure the agents in English. Another possible workaround is to edit the agent cfg file and remove the DBCS codes and replace with SBCS (ASCII) codes. This may allow the agent to start.
Problem summary
When the Agentless Monitoring for Windows OS agent is installed and a language pack is installed to support a double byte language, configuring the agent displays correctly in the native codepage, but after configuration, the Agent will not start. A popup appears with the following text: KCICF5100E -Unable to start service.
Problem conclusion
Agentless Monitoring agents maintain their configuration information using the system's native codepage rather than UTF-8. The code was changed to set the codepage of the configuration file to UTF-8 and all functions that write to and read from the configuration file were changed to support UTF-8. The fix for this APAR is contained in the following maintenance packages: | fix pack | 6.2.2-TIV-ITM-FP0003
Temporary fix
Remove the language pack and configure the agents in English. Another possible workaround is to edit the agent cfg file and remove the DBCS codes and replace with SBCS (ASCII) codes. This may allow the agent to start.
Comments
APAR Information
APAR number
IZ45226
Reported component name
OMEG DIST INSTA
Reported component ID
5608A41CI
Reported release
621
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-03-05
Closed date
2010-02-26
Last modified date
2010-10-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
OMEG DIST INSTA
Fixed component ID
5608A41CI
Applicable component levels
R622 PSY
UP
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTFXA","label":"Tivoli Monitoring"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"621"}]
Document Information
Modified date:
30 December 2022