none
Exit code 3010 suddenly considered as failure RRS feed

  • Question

  • Hello,

    SCCM CB 1906 in use. Suddenly packages that return exit code 3010 is now considered a failure, as they of course should be a "success but reboot required". Below some applicable information extracted from execmgr.exe . This happens in both full desktop and Task sequence environment. Tested with a few different packages that use Reboot=ReallySuppress switch, all fail.

    - - - -

    Running "C:\WINDOWS\system32\msiexec.exe" /i "PackageX.msi" /qn /L*V c:\Somewhere\install.log REBOOT=REALLYSUPPRESS with 32bitLauncher

    ...

    Program exit code 3010

    Looking for MIF file to get program status

    Script for Package:ABC00000, Program: install failed with exit code 3010

    ...

    Execution is complete for program install. The exit code is 3010, the execution status is FailureNonRetry

    - - - -

    Packages "After running" action is "no action required".

    Any suggestions what could have broken? Last time these same packages worked correctly was about 2 weeks ago.


    Friday, September 6, 2019 10:00 AM

Answers

  • Just to verify, has "someone" altered the site control file?

    To check, if you run the below query in SQL Management studio, expand the returned XML (by clicking on it) and then look for the Reboot Return Codes property, what codes are listed for the Value 2 attribute? 

    SELECT SiteControl 
    FROM vSMS_SC_SiteControlXML 
    WHERE SiteCode = '<SITECODE>'

    See the HOW TO VIEW THE SITE CONTROL ( SITECTRL ) FILE section at https://www.anoopcnair.com/how-to-edit-sccm-site-control-sitectrl-file/ for screenshots and a brief description on this.


    Jason | https://home.configmgrftw.com | @jasonsandys

    • Marked as answer by no_access Wednesday, September 11, 2019 10:15 AM
    Friday, September 6, 2019 12:28 PM

All replies

  • Just to verify, has "someone" altered the site control file?

    To check, if you run the below query in SQL Management studio, expand the returned XML (by clicking on it) and then look for the Reboot Return Codes property, what codes are listed for the Value 2 attribute? 

    SELECT SiteControl 
    FROM vSMS_SC_SiteControlXML 
    WHERE SiteCode = '<SITECODE>'

    See the HOW TO VIEW THE SITE CONTROL ( SITECTRL ) FILE section at https://www.anoopcnair.com/how-to-edit-sccm-site-control-sitectrl-file/ for screenshots and a brief description on this.


    Jason | https://home.configmgrftw.com | @jasonsandys

    • Marked as answer by no_access Wednesday, September 11, 2019 10:15 AM
    Friday, September 6, 2019 12:28 PM
  • Thanks Jason for your reply!

    Checked the values, listed codes are the proper ones: 1604,1641,3010,3011

    I managed to reproduce the problem with packages returning exit code 1641 too.

    Very strange... additional suggestions very welcome :)

    EDIT: We have identified that clients receive faulty policies, resulting incorrect values in "RebootReturnCodes" field. So this is a client side issue, we´re investigating what is causing this.

    FIX: temporarily disabled "Client Cache settings" from all distributed client policies except default policy, then enabled back -> exit codes now back in order.



    • Edited by no_access Tuesday, September 10, 2019 5:28 AM Added fix
    Friday, September 6, 2019 2:36 PM
  • Strange. You should report your findings and evidence to Microsoft using a frowny face in the console.

    Jason | https://home.configmgrftw.com | @jasonsandys

    Wednesday, September 11, 2019 2:58 PM