Guest

Preview Tool

Cisco Bug: CSCum43456 - TES 6.1./Certain LDAP users are not getting the full client screen built

Last Modified

Apr 05, 2016

Products (18)

  • Cisco Workload Automation
  • Cisco Tidal Enterprise Adapter for VMware
  • Cisco Tidal Enterprise Adapter for Oracle Database
  • Cisco Tidal Enterprise Adapter for SAS
  • Cisco Tidal Enterprise Adapter for Oracle E-Business Suite
  • Cisco Tidal Enterprise Adapter for Web Services
  • Cisco Tidal Enterprise Adapter for Cognos
  • Cisco Tidal Enterprise Adapter for SAP
  • Cisco Tidal Enterprise Adapter for Informatica
  • Cisco Tidal Agent for Windows
View all products in Bug Search Tool Login Required

Known Affected Releases

6.1.0

Description (partial)

Symptom:
Customer has reported that certain LDAP users when logging in to the client, only get the top horizontal bar and an error box that says, 'Ok'. 

This happened to three certain LDAP users who were assigned to three separate LDAP groups.

Additional Notes around History Purge and CM Purge:

Upon completion of the master db purge process using any purge method such as Windows command line, historyPurge using tesmcmd or sacmd and master built-in/automatic daily purge, the purge operation needs to trigger a CM event to kick off the purge on the CM so the data remains in sync.

========================================
Master kicks off automatic history purge: needs in-memory cleanup of usrmst and usrsession records
Tescmd kicks off history purge: needs in-memory cleanup of usrmst and usrsession records AND CM purge call
saCmd kicks off history purge: needs in-memory cleanup of usrmst and usrsession records AND CM purge call

=========================================
Even the following is taken care of per Doug - This is exactly the same as running it from tesmcmd, so the fix in the master command line processor will address this.

Java.exe -DTIDAL_HOME=<Tidal Master Directory> -classpath "<Tidal Master Directory>\lib\Scheduler.jar;<JDBC Drivers>" -Duser=SuperUser com.tidalsoft.scheduler.script.CommandProcessManager historyPurge (YYYYMMDD) (YYYYMMDD)

Conditions:
Users are part of an LDAP group
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.