Home

 
 
 

Search Knowledge Base


Knowledge Base Web View
Total Records: 105
ID Title Type Of Article
583 
Aaneel Infotech VDI Programmers Project – How to use local USA resources and leverage oversees talent Case Study
517 
500 colours by colour name, Hex value, RGB value and Microsoft Access code number Support
993 
5 things customers want from their salesperson Sales and Marketing
660 
3CX Client How to setup Auto Status Change on Workstation Idle How To
195 
3CX Adding BLF Settings across multiple extensions in the Management Console Support
Add New  Records per page  5 of 5   
Engage Knowledge Base Web View         How To          Print
Title Engage SQL Errors and find a stuck user session means RDP Server needs to be rebooted      
Resolution Engage Application Server is showing SQL Errors and the Engage Application is not working properly.

Check for Stuck Users in the Task Manager under Users Tab. 
Sign Out any Disconnected Sessions. 
If a Session can't be Sign Out and is stuck, the server needs to be rebooted. 

When you see this issue on a Terminal Server it means the server needs to be rebooted to clear it.

A stuck session like this can create File Locks on Engage, as well as other applications, so that user session needs to be cleared. 

Note: Sometimes the file lock created creates an issue on the SQL Server so it may need to be rebooted as well but not always. 
Vendor Engagement Software, LLC
Web Link
Date Entered 3/13/2024
You Tube Link
Type Of Article How To
Article ID 1439


  Copyright   Lietz Development, Inc. 1996. All Rights Reserved.