1 Reply Latest reply on Oct 19, 2015 6:26 AM by cwinning

    Shavlik won.t deploy, URGENT issue, can.t patch

    alexwu Rookie

      Hello,

       

      I have this issue :

      Capture.JPG

      On the console in case i have multiple clients (>100 servers) and on all of them i can only deploy 10% of the patches, on the rest of them i have that error.

      When i do a Test Deploy i get this :

       

      capture 2.JPG

      I already tried to reinstall the ST Remote Scheduler Service with this, but without success

      How To: Uninstall & Reinstall The Shavlik (ST) Remote Scheduler Service On A Single Machine

       

      Also, reinstalled the console, tried to restart services/server etc. I need some suggestions quickly, i.m in the middle of patching and nothing works.

       

      URGENT URGENT

        • 1. Re: Shavlik won.t deploy, URGENT issue, can.t patch
          cwinning CommunityTeam

          Hello,

           

          It's a guessing game without logs for these types of issues.. For any urgent issues, you should create support case including logs or contacting via phone.  I could request logs on the community, but that isn't safe practice since they would be available to the public.

           

          1. Open the Protect GUI and then go to Tools > Options > Logging and change logging to “All” for both user interface and services.

          2. Close the Protect GUI.

          3. Stop the following services

              a.Shavlik Protect Console Service

                b. ST Remote Scheduler Service

          4. Delete all the logs from

              a.  Windows 7, 8, 2008, 2012 & Vista: 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. I would suggest trying another scan and deployment against one machine that you can grab the \ProPatches from in step 6b below.

          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 to reduce size).

          7. Zip the logs from the Protect server and from one of the target machine that failed to deploy,  Attach the logs to the case or have them ready when you call support.

           

          Once you have logs, you should create a case using the Support Portal or call Support directly: 1-866-407-5279 (24/7).

          Please reference this community post in the case.


          Let me know if you have any questions.


          Thanks,

          Charles