Windows MDM - Custom provider error response.

Question

I'm trying to return a error to the Settings screen upon failed enrollment, but the event viewing keeps showing:
MDM Enroll: Server Returned Fault/Code/Subcode/Value=(NULL) Fault/Reason/Text=(NULL).

The xml I'm sending down is:

<s:envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"
            xmlns:a="http://www.w3.org/2005/08/addressing">
    <s:header>
        <a:action s:mustunderstand="1">http://schemas.microsoft.com/windows/pki/2009/01/enrollment/rstrc/wstep</a:action>
        <activityid correlationid="2493ee37-beeb-4cb9-833c-cadde9067645"
                    xmlns="http://schemas.microsoft.com/2004/09/servicemodel/diagnostics">2493ee37-beeb-4cb9-
            833c-cadde9067645</activityid>
        <a:relatesto>urn:uuid:urn:uuid:0d5a1441-5891-453b-becf-a2e5f6ea3749</a:relatesto>
    </s:header>
    <s:body>
        <s:fault>
            <s:code>
                <s:value>s:receiver</s:value>
                <s:subcode>
                    <s:value>s:authorization</s:value>
                </s:subcode>
            </s:code>
            <s:reason>
                <s:text xml:lang="en-us">device cap reached</s:text>
            </s:reason>
            <s:detail>
                <deviceenrollmentserviceerror xmlns="http://schemas.microsoft.com/windows/pki/2009/01/enrollment">
                    <errortype>devicecapreached</errortype>
                    <message>device cap reached</message>
                    <traceid>2493ee37-beeb-4cb9-833c-cadde9067645</traceid>
                </deviceenrollmentserviceerror>
            </s:detail>
        </s:fault>
    </s:body>
</s:envelope>

Answer 1

@Dan Meier-Conroy Thanks for posting in our Q&A.

For this issue, we appreciate your help to explain it more clearly:

1. What did you mean that "return an error to the Settings screen" ?
2. For the XML, how did you send the XML?

And for the event viewer's error message, it shows "NULL". We didn't get the reason of this error message.

If there is anything update, feel free to let us know.