Home

 
 
 

Search Knowledge Base


Knowledge Base Web View
Total Records: 103
ID Title Type Of Article
582 
Hooters Hotel & Casino Las Vegas – Technology Upgrade and Rollup Case Study
1056 
How to backup and restore Taskbar Pinned Apps How To
1130 
How to create a Fillable PDF from Engage Check List How To
643 
How To Find PC Name How To
597 
Hyper-Converged Threat Initiative IT Security Strategy Case Study
569 
Importance of Company Organizational Chart Company Policy
116 
Install & Configure Sonicwall NSA 220 Lan Analyzer Software How To
113 
Internet Explorer Slow Support
411 
Introduction to Meraki Cloud Managed Switches Workflow
592 
Kaseya VSA Over Other Tools What it Means for Our Clients Case Study
580 
Managed Security Services recovers stolen medical equipment for client Case Study
722 
Managed Services Program Descriptions - Elite, Live, Guard How To
223 
Marketing Monthly Reporting Information Support
1108 
Microsoft Office Cheat Sheets Training Resources
132 
MS Access System Resources Exceeded Error Support
1144 
MS Teams How To Videos Training Resources
1177 
MS365 Updates March 2022 Document
221 
New Customer: Billing, Collecting, Memorized Transaction Support
1028 
New Feature for Quote Module ---- Quotation Expiration Notice: How To
273 
Offboarding Checklist New Client
723 
Office 365 Appointment Feature Meeting Poll How To
222 
Onboarding VMS check List New Client
204 
Outlook Connection Status Window Support
1106 
Outlook Training Tips and Tricks Training Resources
730 
Parallels Connection Mode Change How To
Add New  Records per page  3 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.