I upgraded to 1.7 and happened to have Trace set to true in a page in my c# deployment of the CMS using the CMSMenu control. I found that this generated an error similar to that found below.


Multiple controls with the same ID 'CMSMenu1' were found. Trace requires that controls have unique IDs.


With trace set to false the page is fine, initially I tried renaming any similar IDs I had and I even replicated this error by changing the setting on the controls example from the boiler plate Corporate example deployment and the same issue occurred.

For further error message information see below:

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: Multiple controls with the same ID 'CMSMenu1' were found. Trace requires that controls have unique IDs.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[HttpException (0x80004005): Multiple controls with the same ID 'CMSMenu1' were found. Trace requires that controls have unique IDs.]
System.Web.TraceContext.AddNewControl(String id, String parentId, String type, Int32 viewStateSize) +312
System.Web.UI.Control.BuildProfileTree(String parentId, Boolean calcViewState) +201
System.Web.UI.Control.BuildProfileTree(String parentId, Boolean calcViewState) +263
System.Web.UI.Control.BuildProfileTree(String parentId, Boolean calcViewState) +263
System.Web.UI.Control.BuildProfileTree(String parentId, Boolean calcViewState) +263
System.Web.UI.Page.ProcessRequestMain() +1683


Tessa