IT09287: ISD Online documentation to recover from IBM Platform Agent Crash.

APAR status

• Closed as documentation error.

Error description

• When using IBM System Director (ISD) on a Windows Operating
  System (OS), there may be reports in the application logs, that
  show most of the Platform Agent (PA) services are crashing.
  These services have the following names: ibmpawatchdog.exe,
  wmiprvse.exe, wmicimsv.exe, cimlestener.exe, wmicpa.exe along
  with Windows Management Instrumentation (WMI).
  These symptoms indicate that the  WMI repository is corrupted.
  Repairing the WMI and then restarting the PA services will allow
  recovery.
  The ISD online documentation will be updated to include steps to
  repair WMI corruption, as listed in the Local Fix sec-tion of
  this APAR.
  Impact: - Users are not able to recover from PA crash.
  

Local fix

• Steps to recover from PA Crash.
  
  WINDOWS 2003, WINDOWS XP:
  Note: This example is written for installations that use the
  default 'C' drive
  
  1 - Create a script called WMI_Repair.bat with the following :
  
  SET wbemdir=C:\WINDOWS\system32\WBEM
  IF EXIST C:\WINDOWS\SysWOW64 SET
  wbemdir=C:\WINDOWS\SysWOW64\WBEM
  
  echo wbemdir=%wbemdir%
  
  #REM set the Winmgmt service to be disabled upon startup
  sc config winmgmt start= disabled
  
  %wbemdir%\winmgmt /clearadap
  %wbemdir%\winmgmt /kill
  %wbemdir%\winmgmt /unregserver
  %wbemdir%\winmgmt /regserver
  %wbemdir%\winmgmt /resyncperf
  
  net stop winmgmt /y
  
  regsvr32 /s %systemroot%\system32\scecli.dll
  regsvr32 /s %systemroot%\system32\userenv.dll
  
  for /F "usebackq delims==" %%s in (`dir /b /s %wbemdir%\*.dll`)
  do regsvr32 /s %%s
  for /F "usebackq delims==" %%s in (`dir /b /s %wbemdir%\*.mof`)
  do mofcomp %%s
  for /F "usebackq delims==" %%s in (`dir /b /s %wbemdir%\*.mfl`)
  do mofcomp %%s
  
  #REM set the Winmgmt service to auto start upon startup
  sc config winmgmt start= auto
  
  net start winmgmt
  %wbemdir%\wmiprvse /regserver
  %wbemdir%\winmgmt /regserver
  
  2 - put the script on the failing machine
  3 - from command line run:
  
  > WMI_Repair.bat
  
  If the issue is still not resolved, then we need to use the
  following command to detect and
  repair a corrupted WMI Repository :
  
  4 - WINDOWS 2003:
  
  > rundll32 wbemupgd, RepairWMISetup
  
  WINDOWS XP:
  
  > rundll32 wbemupgd, UpgradeRepository
  
  5 - After the above step the server needs to be restarted.
  
  
  Note that none of the above two methods restore the missing
  files related to Windows Management Instrumentation (WMI). So,
  below is a comprehensive repair procedure that restores all the
  missing WMI modules.
  
  In case of missing WMI modules, you may use the following
  method.
  
  
  Comprehensive Rebuild Method
  
  Important Note:  If you have installed a Service Pack, you need
  to insert your Windows CD with Service Pack integra-tion.
  
  If you do not have one, you may point to the
  %Windir%\ServicePackFiles\i386 folder for a recent version of
  the system files required during WMI repair.
  
  Click Start, click Run, type the following command, and press
  Enter:
  
  rundll32.exe setupapi,InstallHinfSection WBEM 132
  %windir%\inf\wbemoc.inf
  
  Repair process should take few minutes to complete.
  
  Then restart Windows for the changes to take effect.
  
  
  WINDOWS VISTA, WINDOWS 7, WINDOWS Server 2008, and WINDOWS
  Server
  2008 R2
  
  Click Start, click Run, type the following command, and press
  Enter:
  
  > Winmgmt /salvagerepository
  
  Note this command will take the content of the inconsistent
  repository and merge it into the rebuilt repository, if it is
  readable.
  
  If the above does not work, then run the following command:
  
  > Winmgmt /resetrepository
  
  Note this will reset the repository to the initial state when
  the OS was first installed.
  
  Warning: Rebuilding the WMI repository has resulted in some
  third-party products not working until their setup is re-run and
  their MOF is re-added back to the repository.
  
  Restart PA Services
  
  1. net stop ibmpawatchdog
  2. net stop wmicimserver
  3. taskkill /f /im wmicpa.exe
  4. net stop winmgmt
  5. REM wait 5 minutes
  6. net start winmgmt
  7. net start wmicimserver
  8. net start ibmpawatchdog
  

Problem summary

• Repairing the WMI and then restarting the PA services will allow
   recovery from a PA Crash.
  The information listed in the Local Fix section of this APAR
  will be added to the troubleshooting section of the IBM Online
  documentation.
  https://www-01.ibm.com/support/knowledgecenter/SSAV7B_635/com.ib
  m.director.tbs.helps.doc/fqm0_r_tbs_solving_problems.html
  Platforms:
  All supported Windows platforms.
  Versions:
  All Supported IBM Platform Agents
  

Problem conclusion

• NA
  

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

Applicable component levels