Hi - I've inherited support of an umbraco site, hosted on Azure Web Roles using the now depreciated accellerator. I do plan on migrating this to the new Azure Preview Websites feature, although that will take some time / coordination with the site contributors.
Last weekend *something* happened to the site causing it to report a 'HTTP Error 503 Service Unavailable Error'.
I restarted the web roles, which brought the service back online, however, when trying to add any new content via the cms, we received a YSOD exception: 'Multiple controls with the same ID 'prop_title' were found. FindControl requires that controls have unique Ids.'
After some googling, I found a thread that suggested renaming the duplicate aliases in the cmsPropertyTable. Inspecting the cmsPropertyTable showed that duplicate rows had indeed been created, and renaming the alias for those seemed to resolve the issue.
I'm very keen to understand how the duplicate rows could have been created in the first place, and whether this would have resulted in the loss of service? That table doesn't appear to have any audit history as to when / who created the rows - is there any way of capturing that information? Looking in the CMS > Settings > DocumentTypes, I can identify the Property that's causing the issue, although again there doesn't appear to be any audit data associated with who added it etc.
If the duplicate rows wouldn't have caused the loss of service, how do I go about identifying what might have?
I noticed that the umbracoLog table is incredibly large (~89%) compared to the rest of the site - it's possible that this was approaching the Azure DB size limit and may have caused the loss of service?
Looking at the IIS logs on the Web Roles doesn't reveal anything - in fact (and oh so helpfully), no logs were created for 03/02/13, presumably because the service had already crashed.
Any help / pointers that people can suggest would be greatly appreciated.
Duplicate entries in cmsPropertyType
Hi - I've inherited support of an umbraco site, hosted on Azure Web Roles using the now depreciated accellerator. I do plan on migrating this to the new Azure Preview Websites feature, although that will take some time / coordination with the site contributors.
Last weekend *something* happened to the site causing it to report a 'HTTP Error 503 Service Unavailable Error'.
I restarted the web roles, which brought the service back online, however, when trying to add any new content via the cms, we received a YSOD exception: 'Multiple controls with the same ID 'prop_title' were found. FindControl requires that controls have unique Ids.'
After some googling, I found a thread that suggested renaming the duplicate aliases in the cmsPropertyTable. Inspecting the cmsPropertyTable showed that duplicate rows had indeed been created, and renaming the alias for those seemed to resolve the issue.
I'm very keen to understand how the duplicate rows could have been created in the first place, and whether this would have resulted in the loss of service? That table doesn't appear to have any audit history as to when / who created the rows - is there any way of capturing that information? Looking in the CMS > Settings > DocumentTypes, I can identify the Property that's causing the issue, although again there doesn't appear to be any audit data associated with who added it etc.
If the duplicate rows wouldn't have caused the loss of service, how do I go about identifying what might have?
I noticed that the umbracoLog table is incredibly large (~89%) compared to the rest of the site - it's possible that this was approaching the Azure DB size limit and may have caused the loss of service?
Looking at the IIS logs on the Web Roles doesn't reveal anything - in fact (and oh so helpfully), no logs were created for 03/02/13, presumably because the service had already crashed.
Any help / pointers that people can suggest would be greatly appreciated.
is working on a reply...