Kaseya Community

Script succeeded but client never reported update success

  • We are preparing a hotfix to address a problem with the service that will be identified by profiles, scans, and updates failing. Most noticeable is the verseion number never getting updated. You can check in the log to see a "Script succeeded but client never reported update success"


    The scenario:
    On some machines the Kaseya AntiVirus service (The service that connects to the AVG services) has gotten unregistered and is not running. We believe there is a race condition / timing issue during the service update process that has gotten it unregistered.

    The fix:
    We'll release a hotfix that addresses this issue by
    - fixing the way we update the Kaseya AV service
    - detecting the script timeout and re-updating the service.

    Legacy Forum Name: Script succeeded but client never reported update success,
    Legacy Posted By Username: Jeff.Keyes
  • Any idea when this hotfix will be released? I have several cases in with support in regards to KES issues, and I'm hoping this hotfix (along with moving to KES 2.1) with address some of these issues.

    Legacy Forum Name: KES,
    Legacy Posted By Username: bjfreeman
  • This was released last weekend on KES 2.0. We haven't included it yet in the KES 2.1 builds (but coming shortly).

    Jeff

    Legacy Forum Name: KES,
    Legacy Posted By Username: Jeff.Keyes