Jump to content

Search the Community

Showing results for tags 'iis'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • MSPGeek
    • Announcements
    • The Geek Cast
  • ConnectWise Automate / Labtech
    • ConnectWise Automate / LabTech
    • ConnectWise Automate / LabTech - Development


  • ConnectWise Automate
    • Scripts
    • Plugins
    • SQL Snippets
    • Role Definitions
    • Automate PowerShell Code
    • Reports
    • Internal Monitors
    • Remote Monitors
  • ConnectWise Manage
    • API Interacting Code

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



About Me


Agent Count













Found 2 results

  1. Is anyone else experiencing this issue (observable in LTErrors.txt agent log file)? In a client environment with a solid and stable network I have personally observed the impact of this (RMM server thought agent was offline even though I was remoted into another agent on the same network). In communication with ConnectWise, they did confirm that this could result in potentially missed alerts and data (the original focus of our issue). We have also checked three different RMM systems (one of which is our own on-prem, another which is cloud-hosted by ConnectWise, and the third in Azure) and found the same issue to exist in those environments, including on the Automate application server. Two systems we checked had no AV whatsoever, and we did not find anything misconfigured with DNS or network ports. Additional details: Azure RMM has less than 10 agents Cloud-hosted RMM has around 25 agents Our on-prem RMM has 10k+
  2. I've had an issue with our server at random times after the daily maintenance period cause IIS to stop responding. The error reads: "Sql Open Conn ErrorAuthentication to host 'localhost' for user 'asp_LabTech_1' using method 'mysql_native_password' failed with message: Access denied for user 'asp_LabTech_1'@'localhost' (using password: YES). I had a case with support back in October and after about a month they came to the conclusion that it was a Windows OS issue. I built a new server and migrated the database. I had no issues from the end of October to now mid-Feburary. Now I'm starting to have the same issue again. I opened another ticket and they suggested to go ahead and upgrade to the 2019.2 patch since it fixes a lot of issues (I was on 12 patch 12). Its been a week on the new patch and today my server threw the same error again. I would appreciate any suggestion as I do not want to go through another server rebuild. Thanks in advance!
  • Create New...