IV24204: SQL DATABASE ERROR: COMMUNICATION LINK FAILURE (08S01:0)

APAR status

• Closed as fixed if next.

Error description

• Environment:  TEM v8.2.1175 with LDAP (Active Directory)
  integration.
  
  While the BigFix TEM server is running, the MS SQL server
  service is restarted for whatever reason.  When attempting to
  log in from a TEM console using a local or LDAP user account,
  it fails will the Data Error: Communication link failure.   See
  screen shot attachment.
  
  Prior restarting the MS SQL Server service, everything was
  working fine.  I was finally able to recreate this problem in
  the lab after trying out a number of scenarios.
  
  As for the customer's environment, it seems to slowly affect
  some user accounts.  There are some user accounts which don't
  have the problem but they might eventually be affected.
  
  For example, one local user ID was working on June 18 (last
  login) and now receive this error.   Another LDAP user ID was
  working fine last Friday at 10:58AM and suddenly it stopped
  working afterward.
  
  So the workaround to fix this is to recycle the BES Root Server
  service.  Once that is done, the same user IDs are able to log
  in.
  
  Unfortunately, this type of MS SQL error is not being logged
  anywhere in FillDB.log, Gatherdb.log or MS SQL error log files.
  Therefore, it makes a big harder to diagnose.
  
  
  Internal bug created
  http://bugs.bigfix.com/bugzilla/show_bug.cgi?id=50821
  

Local fix

• Recycle the BES Root Server service.
  

Problem summary

• This issue will be addressed in the next release of Tivoli
  Endpoint Manager.
  
  General availability Q1 2013 (release date subject to change).
  

Problem conclusion

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

• R82W PSY

     UP