none
Only Applications fails on SOME computers, error 0x0(0) - Unable to make changes to your software RRS feed

  • Question

  • Tricky situation, I used all my Google power ;)

    Situation:

    - Some, problematic Computers fails to install any/all Applications. Right away, without any policy or content download, this error appears: Unable to make changes to your software - 0x0(0)

    - There problematic Computers are capable of executing Packages.

    - Test Computers and other machines are capable of install same Apps.

    - No Appenforce.log is generated

    Troubleshot done:
    - client re-installed
    - latest client version (1902 with latest hotfix rollup) is pushed to production long time ago
    - boundaries are described as subnet range and added to DP.
    - site status all is green up, component status are green, DPs are okay

    Found this line in Scclient_Domain_@User.log
    Failed to build instance path for ScopeId_279EEB60-38BF-4FAF-9391-6ED34DEAB535/Application_2714ad00-ece5-4e34-acc2-9e71e6e7a0eb   (Microsoft.SoftwareCenter.Client.Data.WmiConnectionManager at GetInstance) SCClient 2019-09-02 10:47:34 17 (0x0011)


    MCSE Mobility 2018. Expert on SCCM, Windows 10, ALOVPN, MBAM.



    • Edited by yannara Monday, September 2, 2019 9:22 AM
    Monday, September 2, 2019 8:39 AM

All replies

  • Look at the SCClient* log file. That should tell you why the app install won't start.

    Monday, September 2, 2019 8:56 AM
  • Look at the SCClient* log file. That should tell you why the app install won't start.

    Yep, just did, here is the entire set of 1 failed app install attempt:

    Getting a WMI instance for ScopeId_279EEB60-38BF-4FAF-9391-6ED34DEAB535/Application_6074b519-95ba-49f4-9a96-3be3f68ae64b   (Microsoft.SoftwareCenter.Client.Data.WmiConnectionManager at GetInstance) SCClient 2019-09-02 10:49:08 6 (0x0006)
    Failed to build instance path for ScopeId_279EEB60-38BF-4FAF-9391-6ED34DEAB535/Application_6074b519-95ba-49f4-9a96-3be3f68ae64b   (Microsoft.SoftwareCenter.Client.Data.WmiConnectionManager at GetInstance) SCClient 2019-09-02 10:49:08 6 (0x0006)
    Using endpoint Url: http://XXXXXXXXXXXXXXXXXXXXXXXXXX.COM:80/CMUserService_WindowsAuth, Windows authentication   (Microsoft.SoftwareCenter.Client.Data.ACDataSource+<>c at <RefreshLocalSettingsAsync>b__16_0) SCClient 2019-09-02 10:49:09 6 (0x0006)
    Using endpoint Url: http://XXXXXXXXXXXXXXXXXXXXXXXXXX:80/CMUserService_WindowsAuth, Windows authentication   (Microsoft.SoftwareCenter.Client.Data.ACDataSource+<>c at <RefreshLocalSettingsAsync>b__16_0) SCClient 2019-09-02 10:49:10 15 (0x000F)
    Call to ExecuteMethod failed, WMI MethodName "ApplyPolicyEx", MethodClass "CCM_SoftwareCatalogUtilities", called by , error code -2016411097   (Microsoft.SoftwareCenter.Client.Data.WmiConnectionManager at ExecuteMethod) SCClient 2019-09-02 10:49:11 17 (0x0011)
    Exception caught in ExecuteMethod, line 407, file E:\bt\876161\repo\src\DataAbstractionLib\WmiDataProvider\WmiConnectionManager.cs - Type System.Runtime.InteropServices.COMException:    (Microsoft.SoftwareCenter.Client.Data.WmiConnectionManager at ExecuteMethod) SCClient 2019-09-02 10:49:11 17 (0x0011)
    StackTrace:    at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
       at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
       at Microsoft.SoftwareCenter.Client.Data.WmiConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, String callerMethodName) SCClient 2019-09-02 10:49:11 17 (0x0011)
    Found exception of type System.Runtime.InteropServices.COMException; wrapping in type Microsoft.SoftwareCenter.Client.Data.WmiException   (Microsoft.SoftwareCenter.Client.Data.WmiException at .ctor) SCClient 2019-09-02 10:49:11 17 (0x0011)
    Returning COM exception -2016411097.   (Microsoft.SoftwareCenter.Client.Data.WmiException at get_ErrorCode) SCClient 2019-09-02 10:49:11 17 (0x0011)
    Exception caught in ApplyPolicy, line 883, file E:\bt\876161\repo\src\DataAbstractionLib\WmiDataConnector.cs - Type Microsoft.SoftwareCenter.Client.Data.WmiException: , error code -2016411097   (Microsoft.SoftwareCenter.Client.Data.WmiDataConnector+<ApplyPolicy>d__53 at MoveNext) SCClient 2019-09-02 10:49:11 17 (0x0011)
    StackTrace:    at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
       at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
       at Microsoft.SoftwareCenter.Client.Data.WmiConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, String callerMethodName) SCClient 2019-09-02 10:49:11 17 (0x0011)
    Exception caught in InstallCatalogApplication, line 671, file E:\bt\876161\repo\src\DataAbstractionLib\WmiDataConnector.cs - Type System.Management.ManagementException: Call to ApplyPolicyEx Failed.   (Microsoft.SoftwareCenter.Client.Data.WmiDataConnector+<InstallCatalogApplication>d__48 at MoveNext) SCClient 2019-09-02 10:49:11 17 (0x0011)
    StackTrace:    at Microsoft.SoftwareCenter.Client.Data.WmiDataConnector.<ApplyPolicy>d__53.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.SoftwareCenter.Client.Data.WmiDataConnector.<InstallCatalogApplication>d__48.MoveNext() SCClient 2019-09-02 10:49:11 17 (0x0011)
    Generating event AppCatalogInstallationFailed for application ScopeId_279EEB60-38BF-4FAF-9391-6ED34DEAB535/Application_6074b519-95ba-49f4-9a96-3be3f68ae64b   (Microsoft.SoftwareCenter.Client.Data.WmiDataConnector at SendEvent) SCClient 2019-09-02 10:49:11 17 (0x0011)
    The application Google Chrome 75.0.3770.100 64bit v100 has no UI experience,  it will not be displayed in the UI   (Microsoft.SoftwareCenter.Client.Data.UtilityClass at IsSoftwareAvailable) SCClient 2019-09-02 10:49:11 17 (0x0011)
    The application is not available, this wont show in the status view.   (Microsoft.SoftwareCenter.Client.Data.UtilityClass at ApplicationShouldShowInStatus) SCClient 2019-09-02 10:49:11 17 (0x0011)
    A notification was received for an application that should not be shown in the list view. Ignoring notification and removing application if present.   (Microsoft.SoftwareCenter.Client.ViewModels.SoftwareListViewModel+<HandleSoftwareStatusNotificationsAsync>d__135 at MoveNext) SCClient 2019-09-02 10:49:11 17 (0x0011)
    AppDetails received Event Unknown, state 4, causing a state display value of Failed. The Action Button says _Retry and its enabled state is True   (Microsoft.SoftwareCenter.Client.ViewModels.ApplicationDetailsViewModel+<WmiDataConnection_WmiNotificationEvent>d__136 at MoveNext) SCClient 2019-09-02 10:49:11 17 (0x0011)


    MCSE Mobility 2018. Expert on SCCM, Windows 10, ALOVPN, MBAM.

    Monday, September 2, 2019 9:04 AM
  • Is the deployment still active for the problematic machine? 

    Did you configure any requirements for the deployment type?

    Is there any particular status reported in the Monitoring -> Deployments list for that application / machine?

    Is the application mentioned in appdiscovery.log and if so, what does it say?
    And does the revision mentioned there match the current revision of the application?

    You can also try resetting the client policies on the problematic machine:

    $cn = 'ProblematicComputerName'
    
    write-output "Performing hard policy reset on [$cn]."
    iwmi -ComputerName $cn -Namespace root\ccm -Class SMS_CLIENT -Name ResetPolicy 1 
            
    write-output "Running Machine Policy Agent Cleanup on [$cn]."
    iwmi -ComputerName $cn -Namespace root\ccm -Class SMS_CLIENT -Name TriggerSchedule "{00000000-0000-0000-0000-000000000040}"
            
    write-output "Request Machine Assignments on [$cn]."
    iwmi -ComputerName $cn -Namespace root\ccm -Class SMS_CLIENT -Name TriggerSchedule "{00000000-0000-0000-0000-000000000021}"

    Then wait about 15 minutes for it to refresh and check again.


    Monday, September 2, 2019 9:23 AM
  • Let me be clear, that there is only some group/amount of computers which has this problem. Requirements are not present.

    I found very similar thread which indicates a bug problem in 1902 but it was fixed with hotfix rollup. It has been applied to this enviroment too, but no help:

    https://www.reddit.com/r/SCCM/comments/b8breu/1902_fr_software_center_cannot_retrieve_from_the/?st=k02qs8hm&sh=b0fc8dad

    Not sure, should we just upgrade to 1906 then? 


    MCSE Mobility 2018. Expert on SCCM, Windows 10, ALOVPN, MBAM.

    Monday, September 2, 2019 6:36 PM
  • Hi,

    Have you checked CCMSDKProvider.log? Is there any clue? It records the activities of the application management SDK.


    Best regards,
    Larry

    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Tuesday, September 3, 2019 8:52 AM
  • We are about to upgrade the SCCM to 1906 version today. I will confirm, what the status will be the after this.

    MCSE Mobility 2018. Expert on SCCM, Windows 10, ALOVPN, MBAM.

    Tuesday, September 3, 2019 9:24 AM
  • Hi,

    Have you checked CCMSDKProvider.log? Is there any clue? It records the activities of the application management SDK.


    Best regards,
    Larry

    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    No errors there.

    Upgrading to 1906 and client side as well did not resolve this issue.


    MCSE Mobility 2018. Expert on SCCM, Windows 10, ALOVPN, MBAM.

    Wednesday, September 4, 2019 12:33 PM
  • Also, re-creating the deployment to User Collection did not help. App appeared as NEW in SC, but same failure.

    MCSE Mobility 2018. Expert on SCCM, Windows 10, ALOVPN, MBAM.

    Wednesday, September 4, 2019 12:47 PM
  • I found a workaround for this issue, and the main thing is to get the Computer record deleted and re-generated in a database. So it goes like this;

    1. No app can be installed on Computer
    2. Delete resource recrord from console
    3. Wait to Computer be re-generated
    4. Push client install with uninstallation option
    5. In some time, client greens-up and apps are again installable

    Only problem is, that this takes too much time per-case.... 


    MCSE Mobility 2018. Expert on SCCM, Windows 10, ALOVPN, MBAM.

    Thursday, September 5, 2019 3:10 PM
  • Does the resource record in SCCM show as no client installed before you delete it by any chance?

    I had a similar issue before where machines would only get packages and no applications, times I had to re-create the application due to the revisions or something like that, but this may not be the issue you have.

    have you tried seeing if the resource record has any duplicates in the console or in the SQL database doing a quick " select * from vsms_r_system where Name0 = '' "


    Website: www.walshamsolutions.com Technical Blog: https://www.walshamsolutions.com/technical-blog Personal Blog: https://www.walshamsolutions.com/personal-blog Twitter: Dwalshampro

    Thursday, September 5, 2019 3:16 PM
  • Does the resource record in SCCM show as no client installed before you delete it by any chance?

    Client is YES and green up, policy request has fresh date. No dublicates. Thanks for commenting :)

    MCSE Mobility 2018. Expert on SCCM, Windows 10, ALOVPN, MBAM.


    • Edited by yannara Friday, September 6, 2019 5:30 AM
    Friday, September 6, 2019 5:30 AM
  • Some sites/countries are worst than others. Manual delete and client install push for Service Desk is too hard. But re-generating the client here seems to be the key to success. Also, in this enviroment, then moving from Win7 to Win10, the sccm client is not deleted, but moved to a Collection, which points it to the Task Sequence. 

    I am just wondering, is there a script or other automated solution which could be pushed via Package?

    I also started to read about Certificates in SCCM, because this might have something to do with it; and current Security settings for the site is;

    - HTTPS or HTTP is used
    - Use PKI client certificate is ticked OFF
    - Clients checks the certification revocation list for site systems is ON
    - Trusted Root Certification Authority is not specified
    - Windows Authorization (AD) is used for authentication method
     


    MCSE Mobility 2018. Expert on SCCM, Windows 10, ALOVPN, MBAM.

    Monday, September 9, 2019 5:35 AM
  • I am just asking, could the be a known issue /problems with a process, where Computer account is not deleted from the SCCM database before starting TS wipe and load? Usually, we do always delete Computer from sccm, but not in this case/Project. 

    MCSE Mobility 2018. Expert on SCCM, Windows 10, ALOVPN, MBAM.

    Friday, September 13, 2019 7:41 AM