none
Past due- Will be retired error in Software Center RRS feed

  • Question

  • Hi ,

    I deployed 2 application with Required Purpose and i am getting status - Past due- Will be retired  and such application not deployed .

    can you please suggest how can i correct, i have tested to install those application with same program/command line (that applied while creating application) on local machines its deployed without any error.


    Shailendra Dev

    Monday, February 16, 2015 5:31 PM

All replies

  • You will want to take a look at the AppIntentEval, AppDiscovery.log, and AppEnforce.logs on the device in c:\windows\ccm\logs\ to start troubleshooting why the installation is failing.

    I hope that helps,

     

    Nash


    Nash Pherson, Senior Systems Consultant
    Now Micro - My Blog Posts
    If you found a bug or want the product to work differently, share your feedback.
    <-- If this post was helpful, please click the up arrow or propose as answer.

    Monday, February 16, 2015 5:40 PM
  • thanks in Appdiscovery and Appenforce.log am getting below error, but through the same program of Adobe reader 11.0 am able to install this on local machine without any issue... 

    AppDiscovery.log

    Method EnforceApp failed with error 87D01106                AppDiscovery    2/16/2015 6:05:16 PM    1040 (0x0410)

    CAppProvider::ExecMethodAsync failed. Error 87d01106              AppDiscovery    2/16/2015 6:05:16 PM    1040 (0x0410)

    Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_7137E3B4-D98E-4592-880E-608C741BFFB7/DeploymentType_abf7408d-6b70-4abe-b646-b0c5f25a3b91" AND Revision = 8)"    AppDiscovery    2/16/2015 6:05:16 PM    1040 (0x0410)

        Performing detection of app deployment type Adobe Reader 11.0(ScopeId_7137E3B4-D98E-4592-880E-608C741BFFB7/DeploymentType_abf7408d-6b70-4abe-b646-b0c5f25a3b91, revision 8) for system.         AppDiscovery                2/16/2015 6:05:16 PM    1040 (0x0410)

    +++ Application not discovered. [AppDT Id: ScopeId_7137E3B4-D98E-4592-880E-608C741BFFB7/DeploymentType_abf7408d-6b70-4abe-b646-b0c5f25a3b91, Revision: 8]               AppDiscovery    2/16/2015 6:05:17 PM          1040 (0x0410)

    +++ Did not detect app deployment type Adobe Reader 11.0(ScopeId_7137E3B4-D98E-4592-880E-608C741BFFB7/DeploymentType_abf7408d-6b70-4abe-b646-b0c5f25a3b91, revision 8) for system.         AppDiscovery                2/16/2015 6:05:17 PM    1040 (0x0410)

    Method EnforceApp failed with error 87D01106                AppDiscovery    2/16/2015 6:05:22 PM    1040 (0x0410)

    CAppProvider::ExecMethodAsync failed. Error 87d01106              AppDiscovery    2/16/2015 6:05:22 PM    1040 (0x0410)


    AppEnforce.log


    +++ Starting Install enforcement for App DT "Adobe Reader 11.0" ApplicationDeliveryType - ScopeId_7137E3B4-D98E-4592-880E-608C741BFFB7/DeploymentType_abf7408d-6b70-4abe-b646-b0c5f25a3b91, Revision - 8, ContentPath - C:\Windows\ccmcache\6, Execution Context - System   AppEnforce        2/16/2015 6:05:22 PM    1040 (0x0410)

        A user is logged on to the system.        AppEnforce        2/16/2015 6:05:22 PM    1040 (0x0410)

        Performing detection of app deployment type Adobe Reader 11.0(ScopeId_7137E3B4-D98E-4592-880E-608C741BFFB7/DeploymentType_abf7408d-6b70-4abe-b646-b0c5f25a3b91, revision 8) for system.         AppEnforce                2/16/2015 6:05:22 PM    1040 (0x0410)

    +++ Application not discovered. [AppDT Id: ScopeId_7137E3B4-D98E-4592-880E-608C741BFFB7/DeploymentType_abf7408d-6b70-4abe-b646-b0c5f25a3b91, Revision: 8]               AppEnforce        2/16/2015 6:05:22 PM          1040 (0x0410)

        App enforcement environment:

                    Context: Machine

                    Command line: AdbeRdr11010_en_US.exe /sall

                    Allow user interaction: No

                    UI mode: 0

                    User token: null

                    Session Id: 1

                    Content path: C:\Windows\ccmcache\6

                    Working directory:          AppEnforce        2/16/2015 6:05:22 PM    1040 (0x0410)

        Prepared working directory: C:\Windows\ccmcache\6               AppEnforce        2/16/2015 6:05:22 PM    1040 (0x0410)

    Invalid executable file AdbeRdr11010_en_US.exe            AppEnforce        2/16/2015 6:05:22 PM    1040 (0x0410)

    CMsiHandler::EnforceApp failed (0x87d01106).  AppEnforce        2/16/2015 6:05:22 PM    1040 (0x0410)

    AppProvider::EnforceApp - Failed to invoke EnforceApp on Application handler(0x87d01106).    AppEnforce        2/16/2015 6:05:22 PM          1040 (0x0410)

    CommenceEnforcement failed with error 0x87d01106.  AppEnforce        2/16/2015 6:05:22 PM    1040 (0x0410)

    Method CommenceEnforcement failed with error code 87D01106           AppEnforce        2/16/2015 6:05:22 PM    1040 (0x0410)

    ++++++ Failed to enforce app. Error 0x87d01106. ++++++             AppEnforce        2/16/2015 6:05:22 PM    1040 (0x0410)

     

     

     


    Shailendra Dev

    Monday, February 16, 2015 5:47 PM
  • If you open the folder specified as the deployment type's content source, is there a file named "AdbeRdr11010_en_US.exe"?  (If there is, is it possible it was added after the deployment type was created, and therefore you need to Update Content to get the new file on the distribution point?)

    The logs look like that file is not there.

     

    I hope that helps,

     

    Nash


    Nash Pherson, Senior Systems Consultant
    Now Micro - My Blog Posts
    If you found a bug or want the product to work differently, share your feedback.
    <-- If this post was helpful, please click the up arrow or propose as answer.

    Monday, February 16, 2015 6:01 PM
  • I think the AdbeRdr11010_en_US.exe /sall is wrong.
    Friday, August 28, 2015 5:44 PM
  • @ Shailendracan you recall the fix for this issue, could you please share it ?

    Tuesday, July 18, 2017 2:17 PM
  • Just recreate the deployment. Works every time. 
    Friday, September 29, 2017 1:42 PM
  • Correction.  NEVER works.
    Friday, February 2, 2018 8:34 PM
  • I had this issue in a single machine. None of the logs/internet blogs helped in finding the issue. I spent my entire day to find the cause for this, but unable to fix this.

    Finally as a try uninstalled and reinstalled Configuration Manager Client, that worked!!!

    Friday, September 27, 2019 4:34 AM
  • For me it was the detection method. 

    Get-WmiObject -Class win32_product | where {$_.name -like 'Appname*' | select name, identifyingnumber

    In my case, after an update SnagIT 2019 got an additional ProductGUID. Fixed the detection method and it working now.

    Cheers

    Raghu


    Raghu Sharma

    Tuesday, October 8, 2019 12:47 AM