Chris May

We are getting these stupid errors every now and then on our site.

I still have no idea. I think it is a combo of the fact that we are: 1) using frames, 2) using smart nav, and 3) dynamically loading controls, probabaly in the wrong spot in the life cycle.

Some dude posted that he fixed the problem with an added closing "/" on some of his server control tags, but I don't think this is our issue:

basicly the problem arises when you fail to in sert the closing "/" in custom component tag for instance <mynamespace:mycomponent > will produce the error but <mynamespace:mycomponent /> will not. Despite the fact that this error is so simple it held me up for some time and the error message produced was of course useless in finding the solution.

I will investigate this though.