IBM Support

IV92927: TACMD CONFIGURESYSTEM CANNOT SET WIN32_STARTUP

A readme is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Attempting to modify the Windows _WIN32_STARTUP_ configuration
    parameters using the configuresystem command does not change
    the current configuration settings.
    
    RECREATE INSTRUCTIONS:
    1. Install ITM 630 FP6 TEMS/TEPS
    2. Install ITM 630 FP6 Windows OS Agent on target system.
    3. Using the Tivoli Enterprise Portal Desktop remotely install
    an Instance of the KR2 Agent on the Windows target system.
    Specifying
    _WIN32_STARTUP_.LocalSystem=1
    _WIN32_STARTUP_.InteractWithDesktop
    as the initial configuration parameters.
    4. After the KR2 Agent is connected to the Monitoring Server
    issue the tacmd configuresystem command to alter the KR2 Agent
    startup parameters using the following command,
    
    tacmd configuresystem -m <ManagedSystemName:R2> -p
    INSTANCE=InstanceName
    _WIN32_STRATUP_.Username=Administrator
    _WIN32_STARTUP_.Password=il0veitm
    _WIN32_STARTUP_.LocalSystem=0
    
    5. Observe that the Agent service does not startup. Rather the
    user is returned a message:
    
    Error line(1772): unable to set user to run service as.
    
     The specified return code was received from the two way
    translator.
    

Local fix

  • Configure the KR2 Agent locally.
    

Problem summary

  • If the user specifies  _WIN32_STARTUP_.  values as command line
    parameters for the configuresystem command, the command ignores
    the user specified values.  Under all circumstances, the command
     will ignore the user specified values and set the
    _WIN32_STARTUP_ Agent startup parameters to invalid values.  As
    a result, when the Agent is started it will not be able to log
    in as a Windows Service and will therefore fail to start.
    
    
    The configuresystem commmand incorrectly modifies the
    _WIN32_STARTUP_.Username and _WIN32_STARTUP_.Password parameters
    to the values "Username" and "Password" respectively, regardless
    of the user's input parameter values.  As a result, when the
    Windows Agent is started as a Service, the Operating System will
    prevent the Service (Agent) from starting.
    

Problem conclusion

  • The configuresystem command incorrectly substitutes the
    _WIN32_STARTUP_.  parameter values with the wrong variable
    value.  As a result, the Property Name (Username, Password) are
    used to fabricate the User Name and Password that are used to
    start the Agent rather than the user's parameter values.
    
    
    The fix for this APAR is contained in the following maintenance
    packages:
    
       | service pack | 6.3.0.7-TIV-ITM-SP0001
    

Temporary fix

  • Either remotely modify the Agent's configuration using the TEP,
    or locally modify the Agent's configuration using the Manage
    Tivoli Monitoring Enterpise Service console.
    

Comments

APAR Information

  • APAR number

    IV92927

  • Reported component name

    TEMS

  • Reported component ID

    5724C04MS

  • Reported release

    630

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-01-31

  • Closed date

    2018-07-26

  • Last modified date

    2019-05-07

  • 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

    TEMS

  • Fixed component ID

    5724C04MS

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTFXA","label":"Tivoli Monitoring"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"630","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
08 March 2023