locked
UDI not discovering applications anymore, error is generic "33554432"... RRS feed

  • Question

  • About a year back I developed a UDI with 40 or so applications and dependencies, at this point I decided to shelve it. In any case, I am back to considering it and though I haven't changed anything in my environment besides Windows 10 version (now on 1607 build) and SCCM version (now on 1702), it no longer works. instead when run, I get a warning on the Discovery part, which is listed in the log as ("33554432" Text="Critical problems were encountered while processing the Application Master List. The appropriate applications may not be selected."). Someone suggested  the XML was corrupt which I wrestled with before finally creating a new one with a SINGLE item, which produced the same error. I then built a Windows 10 Enterprise 1511 from ISO and installed SCCM and tried to run the TS and it failed with the same error. I'm at a loss for the issue, not that many replies came to those that listed this error in other threads, anyone have an idea here or face this issue and successfully remediate?

    Jack

    Friday, April 28, 2017 4:44 AM

All replies

  • Application Discovery works when I run the UDI via command line but when run from script in a TS, just generates and error, log file below indicates the output file can't be found;

    05:37:31.645 04-27-2017 2 AppDiscovery 
    05:37:31.645 04-27-2017 2 AppDiscovery ----------------------------------------------------------
    05:37:31.645 04-27-2017 2 AppDiscovery Determine Architecture
    05:37:31.645 04-27-2017 2 AppDiscovery ----------------------------------------------------------
    05:37:31.645 04-27-2017 2 AppDiscovery Checking if registry OS architecture is 64-bit
    05:37:31.661 04-27-2017 2 AppDiscovery Check result (is 64?) : [true]
    05:37:31.661 04-27-2017 2 AppDiscovery Obtaining CM version from registry.
    05:37:31.661 04-27-2017 2 AppDiscovery Found Product Version : [5.00.8498.1000]
    05:37:31.661 04-27-2017 2 AppDiscovery Initializing COM
    05:37:31.661 04-27-2017 2 AppDiscovery 
    05:37:31.676 04-27-2017 2 AppDiscovery ----------------------------------------------------------
    05:37:31.676 04-27-2017 2 AppDiscovery Process Input Configuration(s)
    05:37:31.676 04-27-2017 2 AppDiscovery ----------------------------------------------------------
    05:37:31.692 04-27-2017 2 AppDiscovery 
    05:37:31.692 04-27-2017 2 AppDiscovery ----------------------------------------------------------
    05:37:31.707 04-27-2017 2 AppDiscovery Processing input configuration parameter [C:\WINDOWS\CCM\Logs\SMSTSLog\OSDSetupWizard.xml.app]
    05:37:31.723 04-27-2017 2 AppDiscovery ----------------------------------------------------------
    05:37:31.770 04-27-2017 2 AppDiscovery Initializing DOM/XML
    05:37:31.770 04-27-2017 2 AppDiscovery Opening file [C:\WINDOWS\CCM\Logs\SMSTSLog\OSDSetupWizard.xml.app]
    05:37:31.786 04-27-2017 3 AppDiscovery Error 1: File open failed
    05:37:31.786 04-27-2017 2 AppDiscovery XML Error Parser Reason : [
    Line: 0
    Reason: The system cannot locate the object specified.

    Source: ]
    05:37:32.270 04-27-2017 2 AppDiscovery 
    05:37:32.270 04-27-2017 2 AppDiscovery ----------------------------------------------------------
    05:37:32.270 04-27-2017 2 AppDiscovery Application Results
    05:37:32.270 04-27-2017 2 AppDiscovery ----------------------------------------------------------
    05:37:32.270 04-27-2017 3 AppDiscovery Error 33554432: Fatal error while processing master list:
    05:37:32.270 04-27-2017 3 AppDiscovery Error 16: --| Failure while opening master list file.
    05:37:32.270 04-27-2017 3 AppDiscovery Error 33685504: --| Failure to open file.
    05:37:32.270 04-27-2017 2 AppDiscovery 
    05:37:32.270 04-27-2017 2 AppDiscovery ----------------------------------------------------------
    05:37:32.286 04-27-2017 2 AppDiscovery Application Exit
    05:37:32.301 04-27-2017 2 AppDiscovery ----------------------------------------------------------
    05:37:32.301 04-27-2017 2 AppDiscovery Exit Code          : [33685520] (0x2020010)
    05:37:32.332 04-27-2017 2 AppDiscovery Final Exit Code    : [33554432] (0x2000000)

    Jack

    Friday, April 28, 2017 4:46 AM
  • I believe I have this solved! I will post the URL to my initial thread on the issue so there's not too much cross posting;

    https://social.technet.microsoft.com/Forums/en-US/8678fbe0-2580-4d0c-a7ce-85bca9f0367d/udi-not-discovering-applications-anymore-error-is-generic-33554432?forum=configmanagerosd

    Jack

    Saturday, April 29, 2017 4:08 AM