Jump to content

Search the Community

Showing results for tags 'lterrors.txt'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

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

Categories

  • 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

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Location


Agent Count


INTERESTS


OCCUPATION


ICQ


WEBSITE


WLM


YAHOO


AOL


FACEBOOK


GOOGLEPLUS


SKYPE


TWITTER


YOUTUBE

Found 1 result

  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+
×