IZ94733: BDT SERVICE CRASHES AND DESKTOP EXITED WHEN INSTALLING PATCHES OR SOFTWARE USING TIVOLI DESKTOP.

Tivoli Framework Patch 4.3.1-TMF-0025
Tivoli Framework Patch 4.1.1-TMF-0123
Tivoli Framework Patch 4.1.1-TMF-0129

APAR status

• Closed as program error.

Error description

• History:
  
  9 out of 10 times when customer is trying to install a product
  or patch,
  the BDT service crashes as can be seen in the log files. And the
  GUI
  keeps displaying  dots forever (.........). Customer has to
  restart the
  TMR server and sometimes the Managed Node.
  
  Evn:
  TMF 4.3.1 patch 0012
  TCM 4.3.1 patch 002
  Windows 2008 R2 server
  
  Error msg:
  
  TMR oservlog:
  2010/12/23 17:27:22 -02: ^Helper
  D:\Tivoli\bin\\w32-ix86\TMF\LCF\bdt_service.exe
  (method:216-query,
  PID:840) exited unexpectedly, status=14, hd_retry_count=0
  2010/12/23 17:27:28 -02: ^Helper
  D:\Tivoli\bin\\w32-ix86\TMF\LCF\bdt_service.exe
  (method:226-query,
  PID:748) exited unexpectedly, status=14, hd_retry_count=0
  2010/12/23 17:27:56 -02: ^Helper
  D:\Tivoli\bin\\w32-ix86\TMF\LCF\bdt_service.exe
  (method:384-query,
  PID:952) exited unexpectedly, status=14, hd_retry_count=0
  
  
  TMR BDTlog:
  2010/12/23 17:27:22 -02: ^OpenEvent failed @
  ../../../../../src/substrate/oserv/lib/winsock_comm.c 1810 The
  system
  cannot find the file specified.
  2010/12/23 17:27:22 -02: bdt_accept_thread: ipc_accept error
  <42>
  received
  2010/12/23 17:27:22 -02: bdt_accept_thread: thread ABORT -
  listener
  shutdown - Service in ERROR mode.
  2010/12/23 17:27:22 -02: query: BDT service has problem:
  port=6001
  status=2
  2010/12/23 17:27:22 -02: STOPPING BDT SERVICE: service will
  restart on
  demand
  

Local fix

• Test fix pmr62134_debug2.zip provided by L3 engineer solved the
  issue.
  

Problem summary

• On Windows Server 2008 R2, the consecutive socket handles become
  the same number. The wclient command calls the BDT communication
  API in multi threads. In this case, the BDT communication API
  can not handle the socket status correctly.
  

Problem conclusion

• The problem will be fixed in next 4.1.1 and 4.3.1 GA patch.
  

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

  MGMT. FRAMEWORK

• Fixed component ID

  5698FRA00

Applicable component levels

• R411 PSY

     UP

• R431 PSY

     UP