APAR status
Closed as program error.
Error description
Windows Application log events are received when certain TSM storage agent service operations occur. Certain events will be recorded to the event log without the proper context information, causing users to be confused about the state of the TSM storage agent services. Event ID 1: Event Type: Error Event Source: ADSMServer Event Category: None Event ID: 1 Date: 1/2/2005 Time: 1:23:45 AM User: N/A Computer: HOSTNAME Description: The description for Event ID ( 1 ) in Source ( ADSMServer ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: No compatible instance found for Storage Agent service: TSM Storage Agent, 1168. Event ID 2: Event Type: Information Event Source: ADSMServer Event Category: None Event ID: 2 Date: 1/2/2005 Time: 1:23:45 AM User: N/A Computer: HOSTNAME Description: The description for Event ID ( 2 ) in Source ( ADSMServer ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Storage Agent, StorageAgent1, Service, Administrator, 5.3.0.0. Event ID 3: Event Type: Information Event Source: ADSMServer Event Category: None Event ID: 3 Date: 1/2/2005 Time: 1:23:45 AM User: N/A Computer: HOSTNAME Description: The description for Event ID ( 3 ) in Source ( ADSMServer ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Storage Agent, StorageAgent1, Service, Administrator, 5.3.0.0. . If properly formatted, the messages should show something similar to the following instead: . Event ID 1: Event Type: Error Event Source: ADSMServer Event Category: None Event ID: 1 Date: 1/2/2005 Time: 1:23:45 AM User: N/A Computer: HOSTNAME Description: Fatal error trying to start the TSM server as a service. Location: No compatible instance found for Storage Agent service: TSM Storage Agent. RC: 1168 Event ID 2: Event Type: Information Event Source: ADSMServer Event Category: None Event ID: 2 Date: 1/2/2005 Time: 1:23:45 AM User: N/A Computer: HOSTNAME Description: A TSM Storage Agent has been successfully started. Instance: StorageAgent1 Type: Service Account: hostname Version: 5.x.x.x Event ID 3: Event Type: Information Event Source: ADSMServer Event Category: None Event ID: 3 Date: 1/2/2005 Time: 1:23:45 AM User: N/A Computer: HOSTNAME Description: A TSM Storage Agent has been successfully stopped. Instance: StorageAgent1 Type: Service Account: hostname Version: 5.x.x.x . This may potentially affect other Windows Application Event log messages, but the above messages were observed initially as problematic. . TSM Versions Affected: All 5.2 and 5.3 storage agents. . Initial Impact: Low
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All Windows TSM Storage Agent Users * **************************************************************** * PROBLEM DESCRIPTION: The Windows TSM Storage Agent is not * * including the event description in the * * Windows application event logging. * * The description should include the ANR * * error message. * **************************************************************** * RECOMMENDATION: Apply fixing level when available. This * * problem is currently projected to be fixed * * in levels 5.2.6 and 5.3.2 Note that this is * * subject to change at the discretion of * * IBM. * **************************************************************** The Windows TSM Storage Agent is not filling in the event description when viewing AdsmServer records from the Windows application event log. When an error is encountered by the Windows TSM Storage Agent, a record is added to the operating system's application event log. Like the TSM Server, this record should include the error message number and error text in the description field when viewed.
Problem conclusion
The TSM Storage Agent has been corrected to include error messages in Windows application event log records.
Temporary fix
Comments
APAR Information
APAR number
IC45726
Reported component name
TSM SERVER 510
Reported component ID
5698ISMSV
Reported release
53W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2005-04-11
Closed date
2005-06-09
Last modified date
2005-06-09
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
TSM SERVER 510
Fixed component ID
5698ISMSV
Applicable component levels
R52Z PSY
UP
R53Z PSY
UP
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"53W","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]
Document Information
Modified date:
09 June 2005