Saturday, February 12, 2022

Software Center Install Error Codes

Application do install thru Software Center however there are certain moments when apps fail to install & we see some error codes in Software Center.




Software Center Error Codes:

  • 0x1(1)
    • Incorrect function
    • Residuals found in device also app present in Appwiz, uninstall restart, check install , if still problem persist check registry
    • Deployment Failed
  • 0x87D00213(-2016411117) : Timeout occurred
  • 0x87D0027C (-2016411012) : CI Document download time out
  • 0x800705B4 (-2147023436) : Operation returned because timeout period expired
    • Install took longer than allowed.
    • Try install again usually associated with installs that require user input to complete.
    • Review Install logs
    • issue observed while reviewing DCMAgent log with bug in MS… I had to rename ccmstore.sdf or reinstall client.. complete video link https://www.youtube.com/watch?v=6qpphPO4AJ0
    • "Deployment Failed or "Requirments not met" or "Evaluation Failed" or "Failed to locate content"
  • 0x87D00324(-2016410844) 
    • Detection issue
    • The software package installed successfully, but a software detection rule was not found.
    • You can verify the application detection method mentioned also by checking install logs , appenforce can also give certain clue.

  • 0x87D00325(-2016410843) 
    • Detection issue
    • The software package uninstalled successfully, but a software detection rule was still found.
    • Review uninstall logs, check appwiz.cpl"
  • 112 : Not enough space on the disk
  • -2147024784 : Not enough space on the disk
  • -2147023080 : Not enough quota is available to process this command
  • 0x87d01201(-2016407039) : Out of space
    • Deployment Failed
    • Download fail, HDD out of space
    • Check HDD Space
    • CCMCache max size limitation check
  • 0x652 (1618) : Another installation is already in progress
  • -2147023278 : Another installation is already in progress
    • Deployment Failed
    • Another install in progress
    • Restart services or computer"
  • 0x80040154 (-2147221164)
    • Class not registered 
    • Evaluation Failed
    • CCMRepair, Client Reinstall
  • -2147010895
    • Deployment Failed
    • Application has failed to start because its config is incorrect.
    • Check event log

Additional Error Codes:

  • -2147023504
    • Deployment Failed
    • The file or directory is corrupted & unreadable
    • Clear CCMCache repository folder & Run Action cycle
  • -2016407040
    • No content request found with the given handle
    • Failed to download dependent contents
    • Clear CCMCache repository folder & Run Action cycle
    • 0x87D00607(-2016410105)
      • Content not found
      • Could be DP not assigned to Boundary Group Check CITaskMgr, Appdiscovery, appinitEval, appenforce, data transfer, content transfer, CI Agent, DCMagent,
    • 0x87D01106(-2016407290)
      • Content not available
      • Check if content is distributed to DP
    • -2147024809
      • The parameter is incorrect
      • Failed to verify the executable file is valid or to construct the associated CMD line
      • Failed to download dependent contents
      • Check content in CCMCache or clear ccmcache repository & run action cycles
    • 1619
      • This installation package could not be opened. 
      • Check content in CCMCache or clear ccmcache repository & run action cycles
    • 0x80041001(-2147217407)
      • Generic Failure
      • SMS Agent host service not running, restart service, else repair ccmclient or reinstall client
    • 0x80091007(-2146889721)
      • Hash value incorrect
      • Clear ccmcache & retry, check event log if something else is blocking
    • 0x64C (1612)
      • Deployment Failed
      • Installation source for this product is not available. Verify that source exists and you can access it
    • 0x643 (1603) : Fatal error during installation
    • 0x87D00443(-2016410557)
    • -1073741510 : Fatal error during installation
    • -1073741502 : Fatal error during installation
    • 424 : Fatal error during installation
      • Deployment Failed
      • One or more process are running & prevent enforcement action
      • Conflict of application, restart pc or review services , apps & close it.
    • 5 : Access denied
    • -2147217405 : Access denied
    • -2147024891 : Access denied
      • Deployment Failed or Evaluation Failed or Dependency Installation Failed
      • Check permission
    • 0x87D01107 (-2016407289)
      • Failed to access all provided program locations. 
      • Failed to locate content
    • 0x80004004 (-2147467260)
      • Operation aborted
      • Failed to download dependent contents
    • -214718113
      • Catastrophic failure
      • Evaluation Failed
    • -2147217389
      • Provider load failure
      • Evaluation Failed
    • 1625
      • Deployment Failed
      • Installation forbidden by system policy
    • 1400
      • Deployment Failed
      • Invalid Window handle
    • -2147023446
      • Deployment Failed
      • Insufficient System resource exit to complete the requested service
    • -2146959355
      • Evaluation Failed
      • Policy for this program does not exist or is invalid
    • -2016410105
      • Content not found
      • Failed to download dependent contents



























    Sunday, February 6, 2022

    Patch scanning fail GROUP POLICY issue linked with Registry.pol

    Troubleshoot to diagnose if Patch scanning is failing.

    1. Assignment of Patches
    2. Scanning of Devices
    3. Deploying of Patches



    Log Files to check: WUAHandler.log

    Common Error seen in log:

    Failed to run BeginSearch() on WUAgent. Error = 0x80070422
    It’s a WSUS update source type… adding it
    Existing WUA Managed server was already set (http://sup.domain:8530) , skipping Group Policy registration.
    Failed to run BeginSearch() on WUAgent. Error = 0x80070422

    OnSearchComplete – Failed to end search job. Error = 0x80248007
    Scan failed with error = 0x80248007
    GroupPolicyError.

    Error Code seen in logs:
    0x0005
    0x80004005
    0x87d00605
    0x87d00692
    0x800703EE
    0x80070422
    0x80070570
    0x80248007
    0x80080005
    0xC8000710
    0x80244017
    0x80040154
    0x80240FFF
    0x80240438


    FIX:
    1. To rename or delete REGISTRY.POL file located in 
    C:\windows\system32\Grouppolicy\Machine
    C:\windows\system32\Grouppolicy\User (Optional in certain devices)

    Explore Registry.pol thru notepad or thru third party software

    2. Gpupdate /force
    3. SoftwareupdateEvalCycle & Scan cycle thru ConfigManager Action items

    Post this scanning is successfully

    Saturday, January 29, 2022

    Microsoft 365 Apps Update Stuck at 50% Downloading error 0x87D0024A

    Referring to any Microsoft 365 Apps update getting stuck in Downloading (50% Complete)

    There could be multiple reason on Updates getting stuck..




    1. To get brief understanding on what does a KB or update do, review https://www.catalog.update.microsoft.com/ 

    Will get good information on a KB as well as old / new updates that are superseded or replaced



    2. Logs to Review:

    WUAHandler.logRecords details about the Windows Update Agent on the client when it searches for software updates.

    UpdatesDeployment.logRecords details about deployments on the client, including software update activation, evaluation, and enforcement. Verbose logging shows additional information about the interaction with the client user interface.

    UpdatesHandler.logRecords details about software update compliance scanning and about the download and installation of software updates on the client.

    UpdatesStore.logRecords details about compliance status for the software updates that were assessed during the compliance scan cycle.

    Microsoft Document link: https://docs.microsoft.com/en-us/mem/configmgr/core/plan-design/hierarchy/log-files

    Entry in UpdatesHandler.log:
    BeginDownload alternate update content failed. Error = 0x87d0024a
    CDeploymentJob – Failed to download update Error= 0x87d0024a

    Error in Software Center: 


    3. Error Definition:
    Office365 Updates failing with error 0x87D0024A The job is already connected

    4. Probabilities of solution:
    1. Reinstallation SCCM Client
    2. Repair SCCM Client
    3. Added devices exclusion, post scan cycle this will wipe info.. Remove exclusion
    4. Language pack.. multiple DP & Redistribute content
    5. Other blogs .. apiclient.dll is missing or corrupt.. 
      • C:\programfiles\Common Files\Microsoft Shared\ClickToRun\ApiClient.dll
      • Replacing this file from working machine can be tried

    5. Fix I have applied:
    • Software Center >> Installation Status >> Office 365 English (US) Language Pack >> Repair
    • 30 min down time..
    • Reinstalls office. Successful completion
    • Updates & Retry MS 365 App updates 
    • Completes Installs Successfully.
    • Pre Restart Client OS before repairing language pack.






    Sunday, January 23, 2022

    Devices Stuck in Waiting for Maintenance Window

    Question :: Why application deployment is not enforcing automatically ?





    Observation : In Appenforce.log no entry of enforcing visible.

    Workaround : In Software Center when click on Retry Application installs successfully.

    Or

    Click on app eval from action cycle during maintenance window

    Troubleshoot Application Deployment: https://docs.microsoft.com/en-us/mem/configmgr/apps/understand/deployment-policy-technical-reference


    Snapshot of Application deployment :

    1. Policy Creation:
      • ConfigMgr :: Policy Created SMSProv.log >> objreplmgr.log
    2. Application Deployment for Device / User Collection:
      • Client.log :: PolicyAgent.log >> Scheduler.log >> DCMAgent.log
    3. DCMAgent.log >> CIAgent.log (other logs too CCMessaging.log)
    4. CI Agent >> Downloading CI… metadata is downloaded CI Downloader.log , DataTransferService.log
    5. InvokingSdmMethod >> Application detection (Appdiscovery.log , AppIntEval.log)
    6. StateDownloadingContents >> CAS, ContentTransferManger,LocationService, DataTransferService
    7. StateEnforcing CI >> AppEnforce.log
    8. StateEnforcementReporting >> StateMessage.log

    Error observed in DCMAgent.log:
    DCMAgent error : The DCMAgent.log also contains an error resembling the following, recorded at the same time as the SCClient log entry.  The 0x87d00315 error code translates to "The CI version info data is not available."  



    FIX: 
    1. ccmstore.sdf >> rename / delete (Ccmstore.sdf is created) >> Run Action Cycle
    2. Uninstall SCCM Client & Reinstall

    Saturday, January 15, 2022

    FIX for CCMSETUP install error code 0x87d00227

     FIX for CCMSETUP install error code 0x87d00227



    While installing client if see error in installing client as 0x87d00227 CCMSetup error



    Can check metered connection settings:

    Go to Select Start  > Settings  > Network & Internet > Internet Properties

    Set as Metered Connection if its ON need to turn OFF

    Rerun CCMSetup should get CcmSetup is exiting with return code 0







    Sunday, January 9, 2022

    Enable Verbose / Debug Logging in SCCM / MECM Client Computers



    In case if we need more detail information while troubleshooting thru logs, we need to enable Verbose / Debug logging

    2 Ways we can enable Verbose Logging.

    1. Thru SCCM / MECM Client Computer 
    2. Thru SCCM / MECM Console


    1. Thru SCCM / MECM Client Computer 

    Go to regedit :: 
    • Registry path HKEY_LOCAL_MACHINE\Software\Microsoft\CCM\Logging\@GLOBAL\
    • LogLevel set as 0
    • By default value is 1, need to change to 0.
    • Below are different values of logging ranging from 0 to 3









    To enable debug logging set registry in below :

    • Create registry value as REG_SZ , name as Enabled with a value of True
    • HKEY_LOCAL_MACHINE\Software\Microsoft\CCM\Logging\DebugLogging\Enabled
    • If DebugLogging folder not present need to create it



    • Restart SMS Agent Host Service


    2. Thru SCCM / MECM Console 
    • Open Microsoft Endpoint Configuration Manager
    • Go to Devices >> Select Device 
    • Right Click >> Client Diagnostics >> Enable Verbose Logging


    • Restart SMS Agent Host Service on client computer


    More info on below Microsoft site:

    https://docs.microsoft.com/en-us/troubleshoot/mem/configmgr/enable-verbose-logging

    https://docs.microsoft.com/en-US/troubleshoot/mem/configmgr/turn-on-debuglogging-key



    Friday, December 31, 2021

    AUDIT STATUS MESSAGES .. Find out what activities carried out in MECM Console?

    Want to review audit information what all activities carried out in console like creation / deletion of collection, or application creation & deployment?

     Can work thru below steps to review Status Messages also video link is attached herewith:


     In the MECM console:

    1.      Select the Monitoring workspace,

    2.      Go to Overview > System Status > Status Message Queries.

    3.      Select All Audit Status Messages from a Specific Site.

    4.      Right-click and select Show Messages.

    5.      The All Audit Status Messages from a Specific Site window opens

    6.      In the Specify text box, type Site Code

    7.      In the Prompted value area, click Time.

    8.      In the Select date and time drop-down list, select 1 day / 1 hour ago as per requirement, and then click OK.

    9.      The Configuration Manager Status Message Viewer window shows the results of the query. Review the results.

     



    HOW TO DEPLOY SCCM / MECM CLIENT ON DEVICES ?

    To install SCCM / MECM client on devices: Precheck: 1. Installation Account is a member of Local Administration group 2. Site Server can ...