Cisco Bug: CSCsz43516 - Scripted.exe does not close properly due to sadlib thread.
Dec 29, 2016
- Cisco Unified Contact Center Enterprise
Known Affected Releases
7.2(3) 7.2(4) 7.2(5) 7.2(6)
Symptom: Unable to launch a new session of scripted.exe after closing an existing one Conditions: After performing certain functions like importing a script, exporting a script, or saving a trace using call tracer in Script Editor, when the user exits the program the scripted.exe process is still stuck in Task Manager. The result is that the use cannot subsequently start a new Script Editor session.
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)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases