4 Replies Latest reply on Jun 7, 2016 9:07 AM by mlaporte71

    Test patch Deployment stuck in Scheduled Status

    Rookie

      Hello,

       

      I have Shavlik Protect Standard 9.2.0 Build 5046.

       

      The patch Scan work perfectly for all my server.  The deployment is also working perfectly on all servers, but two of them does not work.

       

      I right-click on my server and choose "test Patch deployment".  The STTestPatch file is copied with success on the server and the installation package is created.  In Operations Monitor, the Status stays in Scheduled.  On the server, the patch does not install.

       

      From Shavlik server to my host, the following ports are open: 135, 445, 5120.

      From my host to Shavlik server, the following ports are open: 135, 445, 3121.

       

      The Windows firewall is stop and disable.

      The ST Remote Scheduler Service is Started.

       

      I have re-install the Scheduler service.

       

      I have tried to find the answer on the web, but didn't find anything to resolve that issue on my two servers.

       

      Someone can help me with this ?

       

      Thanks !

        • 1. Re: Test patch Deployment stuck in Scheduled Status
          cwinning CommunityTeam

          Hello,

           

          You could take a look in the deployment logs on the Protect server and the target machines and look for 'error' or 'failed':

           

          On the target server:

          1. Navigate to a machine that is being deployed to from the console.

          2. Stop the ST Remote Scheduler Service.

          3. Delete the entire C:\Windows\ProPatches folder.

          4. Attempt to reproduce your issue.

          5. You can take a look in the logs C:\Windows\ProPatches\Logs.  See any errors?

           

          Due to the nature (complexity) of deploying patches, it would be best to reproduce the issue, collect logs and then open a case with Support.

           

          If you open a case with support, you can save time by including this:

           

          Protect Server:

          1. If you are unable to set logging via the GUI see this doc: http://community.shavlik.com/docs/DOC-22938

          2. Close the Protect GUI.

          3. Stop the following services

               a. Shavlik Protect Console Service

               b. ST Remote Scheduler Service (In 9.2, the ST Remote Scheduler Service is no longer used on the console. You do not need to stop this service if using 9.2)

          4. Delete all the logs from

               a.  Windows Vista, 7, 8, 10, Server 2008, Server 2012: C:\ProgramData\LANDesk\Shavlik Protect\Logs

               b.  Earlier OS’s:  C:\Documents and Settings\All Users\Application Data\LANDesk\Shavlik Protect\Logs

          5. Start the console service and open the Protect GUI.

          6. Attempt to reproduce the issue. Please document steps to reproduce.

               a. Collect the logs from the Logs folder mentioned earlier in step 4 (please zip if possible)

               b. [Deployment issues only] On the target system please zip and send a copy of the entire C:\Windows\Propatches folder and its contents (you can leave out the Patches sub-folder).

          7. Zip and send all the logs.


          Target Machine:

          Protect 9.x Deployment Logs (For agentless deployment)

          1. Navigate to a machine that is being deployed to from the console.

          2. If you are unable to set logging via the GUI see this doc: http://community.shavlik.com/docs/DOC-23048

          3. Stop the ST Remote Scheduler Service.

          4. Delete or rename the entire C:\Windows\ProPatches folder.

          5. Attempt to reproduce your issue. Please note the steps to reproduce.

          6. Stop the ST Remote Scheduler Service.

          7. Copy all of the contents of the C:\Windows\ProPatches folder except for the Patches subdirectory into a new folder.

          6. Zip and send us the new folder.

           

          Thanks,

          Charles

          1 of 1 people found this helpful
          • 2. Re: Test patch Deployment stuck in Scheduled Status
            Rookie

            Thank you Charles I will follow your recommendation !

            • 3. Re: Test patch Deployment stuck in Scheduled Status
              cwinning CommunityTeam

              Great, let me know if you have any issues.

              • 4. Re: Test patch Deployment stuck in Scheduled Status
                Rookie

                Here's what I have found in the C:\Windows\ProPatches\Logs\dplyevts.log file on my host server (the one that I'm trying to installed the test patch).  I understand that my host server has some difficulties communicating with my Shavik server (WSPICSVK01) on port 3121.  Do I understand well ?  I have check again and this port is open from the host to Shavlik.

                 

                2016-06-07T14:43:43.6380530Z 1890 I PingBack.cpp:53 Sending data to 'https://WSPICSVK01:3121/ST/Console/Deployment/Tracker/V92'.

                2016-06-07T14:43:43.6536780Z 1890 E HttpDownload.cpp:1249 WinHttpOpen failed: 87.

                2016-06-07T14:43:43.6536780Z 1890 E HttpDownload.cpp:491 AttemptIEProxySession failed.

                2016-06-07T14:43:43.7474280Z 1890 E HttpDownload.cpp:1028 WinHttpSendRequest failed: 12175.

                2016-06-07T14:43:43.7474280Z 1890 E HttpDownload.cpp:499 AttemptStraightSession failed.

                2016-06-07T14:43:43.7474280Z 1890 E PingBack.cpp:63 Sending data to 'https://WSPICSVK01:3121/ST/Console/Deployment/Tracker/V92' failed: 12175.

                2016-06-07T14:43:43.7474280Z 1890 I PingBack.cpp:53 Sending data to 'https://WSPICSVK01.RES.BNGF.LOCAL:3121/ST/Console/Deployment/Tracker/V92'.

                2016-06-07T14:43:43.7474280Z 1890 E HttpDownload.cpp:1249 WinHttpOpen failed: 87.

                2016-06-07T14:43:43.7474280Z 1890 E HttpDownload.cpp:491 AttemptIEProxySession failed.

                2016-06-07T14:43:43.8099280Z 1890 E HttpDownload.cpp:1028 WinHttpSendRequest failed: 12175.

                2016-06-07T14:43:43.8099280Z 1890 E HttpDownload.cpp:499 AttemptStraightSession failed.

                2016-06-07T14:43:43.8099280Z 1890 E PingBack.cpp:63 Sending data to 'https://WSPICSVK01.RES.BNGF.LOCAL:3121/ST/Console/Deployment/Tracker/V92' failed: 12175.

                2016-06-07T14:43:43.8099280Z 1890 I PingBack.cpp:53 Sending data to 'https://10.64.93.13:3121/ST/Console/Deployment/Tracker/V92'.

                2016-06-07T14:43:43.8099280Z 1890 E HttpDownload.cpp:1249 WinHttpOpen failed: 87.

                2016-06-07T14:43:43.8099280Z 1890 E HttpDownload.cpp:491 AttemptIEProxySession failed.

                2016-06-07T14:43:43.8568030Z 1890 E HttpDownload.cpp:1028 WinHttpSendRequest failed: 12175.

                2016-06-07T14:43:43.8568030Z 1890 E HttpDownload.cpp:499 AttemptStraightSession failed.

                2016-06-07T14:43:43.8568030Z 1890 E PingBack.cpp:63 Sending data to 'https://10.64.93.13:3121/ST/Console/Deployment/Tracker/V92' failed: 12175.