IZ78064: SSM hung/crashing on Windows 2K/XP/2003 due to fragmented virtua l address space

IBM Tivoli 4.0.0-TIV-SSM-FP0010
IBM Tivoli 4.0.0-TIV-SSM-FP0011
IBM Netcool System Service Monitor SSM 4.0 Fix Pack 12 README 4.0.0-TIV-SSM-FP0012
IBM Netcool System Service Monitor SSM 4.0 Fix Pack 13 README 4.0.0-TIV-SSM-FP0013
IBM Netcool System Service Monitor SSM 4.0 Fix Pack 14 README 4.0.0-TIV-SSM-FP0014
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 1 README 4.0.0.14-TIV-SSM-IF0001
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 2 README 4.0.0.14-TIV-SSM-IF0002
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 3 README 4.0.0.14-TIV-SSM-IF0003
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 4 README 4.0.0.14-TIV-SSM-IF0004
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 5 README 4.0.0.14-TIV-SSM-IF0005
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 6 README 4.0.0.14-TIV-SSM-IF0006
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 7 README 4.0.0.14-TIV-SSM-IF0007
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 8 README 4.0.0.14-TIV-SSM-IF0008
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 1 README 4.0.0.15-TIV-SSM-IF0001

APAR status

• Closed as program error.

Error description

• This can be observed/measured using Windows perfmon (Performance
  Monitor) tool;
  Object = Process
  Counter = Virtual Bytes
  Instance = ssmagent
  Virtual Bytes will be observed to reach a gigabyte or two before
  the SSM hangs/crashes. No abnormal values will be seen in Task
  Manager however.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users of SSM 4.0 on Windows 2000, XP or Server 2003.
  ****************************************************************
  PROBLEM DESCRIPTION:
  SSM hung/crashing on Windows 2K/XP/2003 due to fragmented
  virtual address space
  ****************************************************************
  RECOMMENDATION:
  Upgrade to Fix Pack 10 for SSM 4.0.
  ****************************************************************
  

Problem conclusion

• The SSM will try to enable the Windows low fragmentation heap
  (LFH) on startup. If it fails, a warning will be in
  ssmagent.log.
  
  The fix for this APAR is contained in the following maintenance
  packages:
  | fix pack | 4.0.0-TIV-SSM-FP0010
  

Temporary fix

Comments

APAR Information

• 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

  NETCOOL SYS SVC

• Fixed component ID

  5724P4300

Applicable component levels

• R400 PSN

     UP