/build/static/layout/Breadcrumb_cap_w.png

Disappearing ospx file Causing Handshake Fails

Twice now, I have seen where an ospx file has gone missing in the C:\Program Files (x86)\Quest\KACE directory on one of our servers, running Server 2016. It is actually a fairly new server, spun up only a few months ago. I have had to copy back the windependencies.ospx file at least twice from another server. Has anyone ever seen where an ospx file has just gone missing? I would like to stop this from occurring since we use KACE for windows patching, and those ospx files are necessary, or else you get a handshake fail. Thank you.

(Additional Edit) I just noticed that the windependencies.ospx.checksum also went missing in both cases and had to be copied back over.


3 Comments   [ + ] Show comments
  • You might want to review this article:

    https://support.quest.com/kb/111785/which-directories-and-files-do-i-need-to-whitelist-for-the-sma-agent- - Channeler 4 years ago
  • I will give that a try. Thank you. - jmorton 4 years ago
  • I found out that it is not an issue with my AV. I found that if I do specifically a deploy schedule, then the windependencies.ospx and windependencies.ospx.checksum files go missing almost as soon as I pull the trigger. What I saw occur is that the windependencies.ospx file kept coming back with "windependencies.ospx.part" (notice the added .part), and then disappeared for good after three attempts. The checksum file keep disappearing and reappearing, but went away for good after the third attempt to deploy failed.

    Any idea why a deployment would cause this to happen? I exractred the following from the Access log on K100. Where you see the X's is where I have masked the IP address.

    [2019-06-10 12:22:40 -0400] XX.XX.X.XX - "GET /service/patchhandshake.php?kuid=49334936-9399-4a01-8e8f-0923c38f1cfb&path=windows/ HTTP/1.1" 200 714 332 1367 0
    [2019-06-10 12:22:40 -0400] XX.XX.X.XX - "GET /patches/windependencies.ospx HTTP/1.1" 200 21354795 278 21355483 1
    [2019-06-10 12:23:48 -0400] XX.XX.X.XX - "GET /patches/windependencies.ospx HTTP/1.1" 200 21354795 278 21355483 1
    [2019-06-10 12:24:56 -0400] XX.XX.X.XX - "GET /patches/windependencies.ospx HTTP/1.1" 200 21354795 278 21355483 1
    [2019-06-10 12:26:04 -0400] XX.XX.X.XX - "GET /service/patchhandshake.php?kuid=49334936-9399-4a01-8e8f-0923c38f1cfb&path=windows/ HTTP/1.1" 200 714 332 1367 0
    [2019-06-10 12:26:04 -0400] XX.XX.X.XX - "GET /patches/windependencies.ospx HTTP/1.1" 200 21354795 278 21355483 1
    [2019-06-10 12:27:12 -0400] XX.XX.X.XX - "GET /patches/windependencies.ospx HTTP/1.1" 200 21354795 278 21355483 1
    [2019-06-10 12:28:20 -0400] XX.XX.X.XX - "GET /patches/windependencies.ospx HTTP/1.1" 200 21354795 278 21355483 1
    [2019-06-10 12:29:28 -0400] XX.XX.X.XX - "GET /service/patchhandshake.php?kuid=49334936-9399-4a01-8e8f-0923c38f1cfb&path=windows/ HTTP/1.1" 200 714 332 1367 0
    [2019-06-10 12:29:29 -0400] XX.XX.X.XX - "GET /patches/windependencies.ospx HTTP/1.1" 200 21354795 278 21355483 1
    [2019-06-10 12:30:37 -0400] XX.XX.X.XX - "GET /patches/windependencies.ospx HTTP/1.1" 200 21354795 278 21355483 1
    [2019-06-10 12:31:45 -0400] XX.XX.X.XX - "GET /patches/windependencies.ospx HTTP/1.1" 200 21354795 278 21355483 1 - jmorton 4 years ago

Answers (1)

Posted by: SMal.tmcc 4 years ago
Red Belt
1

Sounds like you may want to create an exception in your AV for that file


Comments:
  • I found out that it is not an issue with my AV. I found that if I do specifically a deploy schedule, then the windependencies.ospx and windependencies.ospx.checksum files go missing almost as soon as I pull the trigger. What I saw occur is that the windependencies.ospx file kept coming back with "windependencies.ospx.part" (notice the added .part), and then disappeared for good after three attempts. The checksum file keep disappearing and reappearing, but went away for good after the third attempt to deploy failed.

    Any idea why a deployment would cause this to happen? I exractred the following from the Access log on K100. Where you see the X's is where I have masked the IP address.

    [2019-06-10 12:22:40 -0400] XX.XX.X.XX - "GET /service/patchhandshake.php?kuid=49334936-9399-4a01-8e8f-0923c38f1cfb&path=windows/ HTTP/1.1" 200 714 332 1367 0
    [2019-06-10 12:22:40 -0400] XX.XX.X.XX - "GET /patches/windependencies.ospx HTTP/1.1" 200 21354795 278 21355483 1
    [2019-06-10 12:23:48 -0400] XX.XX.X.XX - "GET /patches/windependencies.ospx HTTP/1.1" 200 21354795 278 21355483 1
    [2019-06-10 12:24:56 -0400] XX.XX.X.XX - "GET /patches/windependencies.ospx HTTP/1.1" 200 21354795 278 21355483 1
    [2019-06-10 12:26:04 -0400] XX.XX.X.XX - "GET /service/patchhandshake.php?kuid=49334936-9399-4a01-8e8f-0923c38f1cfb&path=windows/ HTTP/1.1" 200 714 332 1367 0
    [2019-06-10 12:26:04 -0400] XX.XX.X.XX - "GET /patches/windependencies.ospx HTTP/1.1" 200 21354795 278 21355483 1
    [2019-06-10 12:27:12 -0400] XX.XX.X.XX - "GET /patches/windependencies.ospx HTTP/1.1" 200 21354795 278 21355483 1
    [2019-06-10 12:28:20 -0400] XX.XX.X.XX - "GET /patches/windependencies.ospx HTTP/1.1" 200 21354795 278 21355483 1
    [2019-06-10 12:29:28 -0400] XX.XX.X.XX - "GET /service/patchhandshake.php?kuid=49334936-9399-4a01-8e8f-0923c38f1cfb&path=windows/ HTTP/1.1" 200 714 332 1367 0
    [2019-06-10 12:29:29 -0400] XX.XX.X.XX - "GET /patches/windependencies.ospx HTTP/1.1" 200 21354795 278 21355483 1
    [2019-06-10 12:30:37 -0400] XX.XX.X.XX - "GET /patches/windependencies.ospx HTTP/1.1" 200 21354795 278 21355483 1
    [2019-06-10 12:31:45 -0400] XX.XX.X.XX - "GET /patches/windependencies.ospx HTTP/1.1" 200 21354795 278 21355483 1 - jmorton 4 years ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ