question

MickLang-8011 avatar image
0 Votes"
MickLang-8011 asked SamWu-MSFT commented

Exception configuring failed request tracing rule

142311-image.png
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.


windows-server-iiswindows-wcf
image.png (247.6 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

SamWu-MSFT avatar image
0 Votes"
SamWu-MSFT answered SamWu-MSFT commented

@MickLang-8011

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.



· 8
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

You have the web.config above. If it's corrupted tell me where and how it's corrupted

0 Votes 0 ·

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.

0 Votes 0 ·

@MickLang-8011 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.

0 Votes 0 ·

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

0 Votes 0 ·
Show more comments