System.InvalidOperationException: Stack empty

Question

Once running ASP.NET 4.x application built in Visual Studio 2013 I am getting the below exception.

I have tried to disable the PageInspector by removing page inspect

Answer 1

There are multiple reasons why the

System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was thrown. -
System.InvalidOperationException: Stack empty.
Microsoft.VisualStudio.Web.PageInspector.Runtime.WebForms.SelectionMappingRenderTraceListener.EndRendering(TextWriter writer, Object renderedObject)
...

After adding as proposed:

 <appSettings>
   <add key="PageInspector:ServerCodeMappingSupport" value="Disabled"/>
   ...
 </appSettings>

I noticed I had duplicate selected item on a dropdown list creating the issue.

Answer 2

In my case (ASP.NET 4.6, Visual Studio 2015) I commented an asp text control and added a new asp drop down list but did not updated the AssociatedControlID of the associated label.

on changing the AssociatedControlID to newly added asp drop down list ID my problem was fixed.

Answer 3

I had the same exception, but in my case the problem was the following was missing:

<form runat="server">
</form>

Answer 4

I disabled browser link in VS 2013 and was able to see the actual cause of the error. It is usually something underlying when browser link is set. You can see how to disable it here: http://www.poconosystems.com/software-development/how-to-disable-browser-link-in-visual-studio-2013/

Answer 5

In my case, because I had so many issues migrating a website from VS2002 to VS2015, I decided to create a new project on VS2015 and transfer all webforms from the old project (VS2002) to the new one (VS2015).

The new project had a Site.Master page, which already has a tag. Because I was transferring old webforms without modification, they already had a tag too, so each page trying to load had two tags inside.

When I removed the tag on each page, leaving only the one on Site.Master page, the problem was solved.

I hope this helps.

Answer 6

This can happen if the AssociatedControlID on a label is associated with a control which can't be found.