I know this error shows up several places, but everything we have tried has not fixed the issue.We use Umbraco as our main web site, which is mostly informational with links to lots of different pages. On one particular page, we have a login that authenticates to AD and requires a username and password. This is one of the few pages that does anything outside of a link to another page. On this one page, we have recently started getting an error saying "mutliple controls with the same ID" along with a stack trace and a message that says "trace requires that controls have unique ID's."This page only has two fields on it (username and password) along with the button the user clicks to log in. We've tried every suggestion we can think of. Setting the cache period on the Macro to 0. Making sure the trace is turned off in the web.config.The odd thing is, this is intermittent. Sometimes it works fine, five minutes later you get the error message. Sometimes you can refresh the page several times and it works. It's very frustrating to our users and seems to have come out of nowhere. We do almost everything "out of the box" in Umbraco, meaning, we don't really do any customization. This one page was done by another company a long time ago. We do have a large template around all of the pages and it does occasionally change, but not often. Is there anywhere in Developer tools or somewhere in Umbraco that can pinpoint what the issue is? It seems like some sort of problem with a cache because of the way it clears up sometimes, but we can't seem to resolve it.
You can set the time of cache period on your macro, by go to the developer section macros find the macro that contains your login form and set the period to e.g 60 and change it back to 0 and see if the error is disappears.
Thanks Dennis. We tried setting the cache period and are still getting the error. It actually seems to get worse the more load we have on the system. Not sure why that is. Unfortunately, I'm not very familiar with Umbraco. Our web designer uses it and she inherited it from someone else. I am familiar with DotNet applications and I've seen the error before, but in pure web applications where you are the designer, it's easier to see "where" the error is occurring. I looked at the HotFix from Microsoft and it looks like it's for Framework 1.1. I thought this Umbraco software was running against Framework 4, so not sure the HotFix would help us.
The funny thing is, this page is old as dirt. It's got to be at least 3 or 4 years old. I don't think it's the actual login page that is the problem. I feel like it's something in the Master page, because that would be the only thing that would change. Plus, we have a couple of other forms we've recently created that have user input and they are also getting the error. So, it only happens on pages that cause a Post Back, because there is a submit button on them. I'll get with the content manager and see if we can look into the documenttypes for duplicates. I also suggested maybe putting a different master page around just the login screen to see if that might fix it. It's just an intermediate step for users and doesn't even need navigation or any other boiler plate around it. We appreciate any help we can get on this. We are a community college and are in the middle of registration. We can't really take the site down, so we are scrambling to try and figure this out.
Additional information after doing more research. Again, I'm not an Umbraco expert. I'm simply trying to resolve this issue as the Applications Manager. We normally have very few issues with this site. I was looking at the "main" Master Page and did notice two areas taht have the same Alias Name as shown below. Could something like this cause the problem? We don't do anything custom and I'm not even sure how I would change those names, but that was one of the things that was suggested might cause this problem.
Trace requires that controls have unique ID's
I know this error shows up several places, but everything we have tried has not fixed the issue.We use Umbraco as our main web site, which is mostly informational with links to lots of different pages. On one particular page, we have a login that authenticates to AD and requires a username and password. This is one of the few pages that does anything outside of a link to another page. On this one page, we have recently started getting an error saying "mutliple controls with the same ID" along with a stack trace and a message that says "trace requires that controls have unique ID's."This page only has two fields on it (username and password) along with the button the user clicks to log in. We've tried every suggestion we can think of. Setting the cache period on the Macro to 0. Making sure the trace is turned off in the web.config.The odd thing is, this is intermittent. Sometimes it works fine, five minutes later you get the error message. Sometimes you can refresh the page several times and it works. It's very frustrating to our users and seems to have come out of nowhere. We do almost everything "out of the box" in Umbraco, meaning, we don't really do any customization. This one page was done by another company a long time ago. We do have a large template around all of the pages and it does occasionally change, but not often. Is there anywhere in Developer tools or somewhere in Umbraco that can pinpoint what the issue is? It seems like some sort of problem with a cache because of the way it clears up sometimes, but we can't seem to resolve it.
Hi Tom, and welcome to our, :-)
Perhaps you have a documenttype that had two properties with the same alias, or maybe you need to set the cache period 0 if it has a time set on it, if you are using macros, this solved issue for Chad. Try to see this post about it, http://our.umbraco.org/forum/developers/api-questions/5511-Multiple-controls-with-the-same-ID-were-found-Trace-requires-that-controls-have-unique-IDs
You can set the time of cache period on your macro, by go to the developer section macros find the macro that contains your login form and set the period to e.g 60 and change it back to 0 and see if the error is disappears.
http://support.microsoft.com/kb/834608
Hope this helps,
/Dennis
Thanks Dennis. We tried setting the cache period and are still getting the error. It actually seems to get worse the more load we have on the system. Not sure why that is. Unfortunately, I'm not very familiar with Umbraco. Our web designer uses it and she inherited it from someone else. I am familiar with DotNet applications and I've seen the error before, but in pure web applications where you are the designer, it's easier to see "where" the error is occurring. I looked at the HotFix from Microsoft and it looks like it's for Framework 1.1. I thought this Umbraco software was running against Framework 4, so not sure the HotFix would help us.
The funny thing is, this page is old as dirt. It's got to be at least 3 or 4 years old. I don't think it's the actual login page that is the problem. I feel like it's something in the Master page, because that would be the only thing that would change. Plus, we have a couple of other forms we've recently created that have user input and they are also getting the error. So, it only happens on pages that cause a Post Back, because there is a submit button on them. I'll get with the content manager and see if we can look into the documenttypes for duplicates. I also suggested maybe putting a different master page around just the login screen to see if that might fix it. It's just an intermediate step for users and doesn't even need navigation or any other boiler plate around it. We appreciate any help we can get on this. We are a community college and are in the middle of registration. We can't really take the site down, so we are scrambling to try and figure this out.
Thanks,
Tom
Additional information after doing more research. Again, I'm not an Umbraco expert. I'm simply trying to resolve this issue as the Applications Manager. We normally have very few issues with this site. I was looking at the "main" Master Page and did notice two areas taht have the same Alias Name as shown below. Could something like this cause the problem? We don't do anything custom and I'm not even sure how I would change those names, but that was one of the things that was suggested might cause this problem.
<asp:Content ContentPlaceHolderId="Logo" runat="server">
<a class="logo" href="/"><img src="/elements/skin/logo-print-large.jpg" alt="GTCC - Guilford Technical Community College" /></a>
</asp:Content>
<asp:Content ContentPlaceHolderId="Navigation" runat="server">
<umbraco:Macro Alias="WSC.Navigation.Interior" runat="server"></umbraco:Macro>
<div class="section-header">
<asp:ContentPlaceHolder Id="Section" runat="server">
<div class="tear"> </div>
<umbraco:Macro showHome="1" separator=" &gt; " Alias="WSC.Breadcrumb" runat="server"></umbraco:Macro>
<umbraco:Macro area="1" Alias="WSC.Navigation.Interior.Subnav" runat="server"></umbraco:Macro>
<umbraco:Macro Alias="WSC.Section" runat="server"></umbraco:Macro>
</asp:ContentPlaceHolder>
</div>
</asp:Content>
<asp:content ContentPlaceHolderId="Body" runat="server">
<asp:ContentPlaceHolder Id="Body" runat="server">
<umbraco:Macro area="2" Alias="WSC.Navigation.Interior.Subnav" runat="server"></umbraco:Macro>
<umbraco:Item field="bodyText" runat="server"></umbraco:Item>
</asp:ContentPlaceHolder>
</asp:content>
is working on a reply...