Monday, June 14, 2010

The maximum nametable character count quota (16384) has been exceeded

Some of our services were growing and the other day it hit the quote, I could not update the service references, nor was I able to run the WCFTest client. An error is diplayed saying "The maximum nametable character count quota (16384) has been exceeded "
The problem was with the mex endpoint, where the XML that was sent was too much for the client to handle, this can be fixed by do the following.
Just paste the lines below within the configuration section of the devenve.exe.config and the svcutil.exe.config files found at the locations

C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE,
C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin

Restart IIS and you are done.
The detailed error that you get is the following :

Error: Cannot obtain Metadata from net.tcp://localhost:8731/Services/SecurityManager/mex If this is a Windows (R) Communication Foundation service to which you have access, please check that you have enabled metadata publishing at the specified address. For help enabling metadata publishing, please refer to the MSDN documentation at Exchange Error URI: net.tcp://localhost:8731/Services/SecurityManager/mex Metadata contains a reference that cannot be resolved: 'net.tcp://localhost:8731/Services/SecurityManager/mex'. There is an error in the XML document. The maximum nametable character count quota (16384) has been exceeded while reading XML data. The nametable is a data structure used to store strings encountered during XML processing - long XML documents with non-repeating element names, attribute names and attribute values may trigger this quota. This quota may be increased by changing the MaxNameTableCharCount property on the XmlDictionaryReaderQuotas object used when creating the XML reader.


  1. i'm in same prolem. but can't sort out that at all. i've changed all the files according to your description. but it doesn't working. Same problem. will i post my code to you?


  2. Hey Ruhso,
    After you do those changes, restart Visual Studio, it should work now

  3. Why a screenshot?... text would have been so much more convinient

  4. Thanks, man! Works for me very well!

  5. Big thanks from Moldova!
    Its fucking works :) !