Exception configuring failed request tracing rule

Question

Exception configuring failed request tracing rule

Mick Lang 1

Getting the following error clicking finish on the Add Failed Request Tracing Rule in IIS v10.0.17763.1...

There was an error while performing this operation.

Details:

Exception from HRESULT: 0xC00CEF03

Stripped down to just the offending section, the web.config looks like this...

<?xml version="1.0" encoding="UTF-8"?>  
<configuration>  
  <system.serviceModel>  
    <bindings>  
       <ws2007FederationHttpBinding>  
        <binding name="fred">  
          <security mode="TransportWithMessageCredential">  
            <message establishSecurityContext="false">  
              <tokenRequestParameters>  
                <trust:SecondaryParameters xmlns:trust="http://docs.oasis-open.org/ws-sx/ws-trust/200512">  
                </trust:SecondaryParameters>  
              </tokenRequestParameters>  
            </message>  
          </security>  
        </binding>  
      </ws2007FederationHttpBinding>  
    </bindings>  
  </system.serviceModel>  
</configuration>

Deleting lines 10 & 11 (the <trust:SecondaryParameters> tags) resolves the issue.

I can't see anything wrong with the XML causing the issue. Is this a bug?

I can confirm we're not experiencing this issue in earlier versions of IIS.

1 answer

Your answer

Answer 1

Sam Wu-MSFT 7,561 Microsoft External Staff

@Mick Lang

0xC00CEF03 error code translates to WR_E_NSPREFIXWITHEMPTYNSURI which refers to "Writer: It is not allowed to declare a namespace prefix with empty URI"(Reference).

This error occurs when there is something wrong with the web.config file. It’s probably corrupted or there are incompatible tags and parameters. As a result of this corruption and incompatibility, IIS is not able to read this file. Therefore, it can’t make a change.

The issue mostly happens after migration because a piece of configuration that works in the older version of IIS (and .NET Framework) probably became unsupported in the newer version.

Solution for the 0xC00CEF03 error is find what part of the web.config is causing the issue is to remove sections one by one and test, this seems to be the method you are trying.

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Mick Lang 1 Reputation point

2021-10-21T04:34:16.51+00:00

You have the web.config above. If it's corrupted tell me where and how it's corrupted
Mick Lang 1 Reputation point

2021-10-22T07:41:00.433+00:00

IIf this thing had a down arrow on the score for the comment I'd click it. My question basically inferred I already knew this error is associated with a corrupted web.config, yet you tell me ... 'ah your config is probably corrupt' without even bothering to try the config supplied in the question which I said reproducing the issue. I'd suggest don't even bother answering questions if this is the quality of your response.
Sam Wu-MSFT 7,561 Reputation points Microsoft External Staff

2021-10-22T10:14:16.533+00:00

@Mick Lang I analyze the problem based on the error message you posted. I don’t have the relevant configuration information in your iis to reproduce your problem. I answered above that this is likely to be caused by incompatible versions, if you need more help, I suggest you open a case via : https://support.microsoft.com. In addition, this is an exchange community. Anyone who expresses their own opinions should not ask others for answers as a matter of course. you need to do it yourself more.
Mick Lang 1 Reputation point

2021-10-24T23:16:44.53+00:00

I've replicated it on multiple machines, the configuration listed above does reproduce the issue on the specified version of IIS running on Windows Server 2019
Sam Wu-MSFT 7,561 Reputation points Microsoft External Staff

2021-10-25T01:20:58.13+00:00

@Mick Lang It is difficult to reproduce your problem based on your description, I suggest you open a case via: https://support.microsoft.com.
Mick Lang 1 Reputation point

2021-10-25T05:18:43.177+00:00

I can also replicate it on Windows 10 IIS 10.0.19041.1... The above config reproduces the issue. And I'm not asking for help, I'm reporting a bug and trying to help Microsoft, make its software better,
Mick Lang 1 Reputation point

2021-10-25T05:24:36.84+00:00

To replicate it, copy and paste the top configuration block into a Web.config in an empty folder, create a new website in IIS, attempt to add a rule for failed request, I've given you detailed steps and replicated the issue on three different machines. I do not have a support contract with Microsoft, nor should I need one to report a bug.
Sam Wu-MSFT 7,561 Reputation points Microsoft External Staff

2021-10-25T08:19:16.283+00:00

I have reported this problem to the relevant Microsoft team, you can follow the iis update announcement.

Share via

Exception configuring failed request tracing rule

1 answer

Your answer