/build/static/layout/Breadcrumb_cap_w.png

Deploy Exit codes 3010,0xBC2

I cannot find these deploy exit codes in the documentation.     We just started patching servers we have many patches with a deploy exit code of   3010,0xBC2.  I presume these are two separate codes?  I searched the manual and it only has 8000 codes in it.  Can someone tell me what these exit codes mean and what to do about them?


thanks



0 Comments   [ + ] Show comments

Answers (2)

Posted by: KevinG 3 years ago
Red Belt
2

I believe 3010 is a Windows return code. ERROR_SUCCESS_REBOOT_REQUIRED          A restart is required to complete the install.

If unable to diagnose and resolve the issue, please run the KACE Agent Toolkit on one or more affected endpoints and submit a technical service request.  Include the logs from the KACE Agent Toolkit with the support ticket.

Posted by: barchetta 3 years ago
4th Degree Black Belt
1

I opened a ticket on this and apparently it means the server required a restart.  I dont understand this as kace should restart when required.  So far no answer from my ticket.


Furthermore, the patches are not installed and a restart does not install them but kace sma reports success on deploy and the patch as installed.


I have sent the kapture and screenshots to the ticket.  this is not going well at all.


Comments:
  • Hi Barchetta,
    Did you ever get behind this issue? We are experiencing the same problem and I haven't been able to get it resolved either. Thank you - SecurityCocktail 1 year ago
    • Did you ever figure it out? I see the same result codes. - lama01 2 months 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