Parser Error Message Ambiguous Match Found Asp.net
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Parser Error Message: Ambiguous match found up vote 2 down vote favorite Im running a web application in visual studio 2008.. i got this error when particular page was loaded.. help me to proceed.... Thank u..... Server Error in '/PSS.NET' Application. Parser Error Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately. Parser Error Message: Ambiguous match found. Source Error: <%@ Register TagPrefix="uc1" TagName="CtrlButtonControl" Src="../../WebControls/CtrlButtonControl.ascx" %> <%@ Page language="c#" Codebehind="SPSearchFromToDtStorLocMatTypRank.aspx.cs" AutoEventWireup="false" Inherits="Sdi.Pss.Reports.SP.SPSearchFromToDtStorLocMatTypRank" %> Source File: /PSS.NET/Reports/SP/SPSearchFromToDtStorLocMatTypRank.aspx Line: 1 Version Information: Microsoft .NET Framework Version:2.0.50727.3615; ASP.NET Version:2.0.50727.3614 asp.net share|improve this question edited Aug 19 '10 at 10:27 Nick Craver♦ 433k8410611013 asked Aug 19 '10 at 10:24 John 56782138 add a comment| 5 Answers 5 active oldest votes up vote 2 down vote accepted try these two links - http://forums.asp.net/p/983007/1265347.aspx http://weblogs.asp.net/pjohnson/archive/2006/08/11/Ambiguous-match-found.aspx share|improve this answer answered Aug 19 '10 at 10:29 Sachin Shanbhag 32.6k65989 Really thank u alllllll.... there is two declaration in codebehind file as lblMaterialtype and lblMaterialType.. I just deleted one that im not using.. it works great... thanks a lot.. –John Aug 20 '10 at 9:12 add a comment| up vote 4 down vote I've the same problem and it solved and the s
problem, retracing every change you made, every source control update you performed, attempting to track down the offending bug in code. Days like yesterday, for example. I was working on a fairly nondescript ASP.NET web page, but every time I would attempt to run it I would get the following error: Parser Error Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately. Parser Error Message: Ambiguous match found. Source File: /Default.aspx Line: 1 The only thing that is http://stackoverflow.com/questions/3520809/parser-error-message-ambiguous-match-found typically on Line 1 of any ASP.NET web page is the Page declaration, which specifies the CodeBehind and Inherits properties, so naturally my first thought was that perhaps the class name for the page conflicted with another class in the same namespace. But this was an erroneous assumption, and after renaming the file several times I decided that was probably not the case. After a few hours http://www.nicholascloud.com/2010/02/ambiguous-match-really-is-ambiguous-in-asp-net/ of searching, I realized that I had a button on my page declared something like this:
a spurious error when viewing a few specific pages. The error was occurring during the runtime compilation of these specific aspx pages. Parser Error Description: An error http://www.adrianbanks.co.uk/?p=39 occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately. Parser Error Message: Ambiguous match found. To http://invisiblesoftware.blogspot.com/2009/11/aspnet-runtime-error-ambiguous-match.html make this error more confusing, the error was reported on line 1 of the aspx page which contained nothing more than the page directive tag. After a bit of searching, I found parser error the cause of the problem. The cause was that there were two member variables declared with names that differed only by case (one was an ASP.Net PlaceHolder control, the other an int). Simply renaming one of the variables solved the compilation error. Eran Sandler has also encountered this problem, but delves a lot deeper into what is going on. Entry Filed Under: ASP.Net, .Net 2 Comments parser error message Add your own 1. Sumedha Obeysekera | March 10th, 2010 at 5:21 Thank you very much. You saved my day.. i was struggling with the same problem and this was the answer. Thanks! 2. irish | April 5th, 2011 at 9:48 thank's buddy Leave a Comment Name Required Email Required, hidden Url Comment Please enter the following word: Some HTML allowed:
Subscribe to the comments via RSS Feed Calendar October 2016 M T W T F S S « Oct 12 3456789 10111213141516 17181920212223 24252627282930 31 Most Recent Posts Setting a culture for all threads in an application Alternatives To .Net Reflector F# Links Temporarily Disabling ReSharper Extracting MSI Files (Revisited) MSDN Lightweight View MSDN Low Bandwidth View SQL Server 2005 SP3 Released Useful Diagnostic Tools Setting A Proxy Server For Windows Updates On Vista Related Posts No related posts found. Feeds Entries (RSS) Comments (RSS) Visitors I can't remember where I read it…. ©2006-2016 Adrian Banks Home Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer's view in an
it is almost unimaginable to develop without it! I hope my experiences will prove helpful to others too. Thursday, November 5, 2009 ASP.NET runtime error: ambiguous match found The solution to this turned out to be far from obvious, and once again posts by other bloggers came to the rescue. (If you want the executive summary: it was due to variables defined with different cases.) I just converted a .NET web project to a VS2008 web application, also changing the .NET Framework used (both in the Project, and the IIS website) from 1.1 to 2.0. The conversion went quite smoothly using the VS Convert To Web Application wizard, but one page had the problem below. Other pages using the exact same control and TagPrefix line compiled and worked without complaint. Parser Error Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately. Parser Error Message: Ambiguous match found. Source Error: Line 1: <%@ Register TagPrefix="axp" Namespace="Axezz.WebControls" Assembly="AxpDBNet" %> Line 2: <%@ Register TagPrefix="cr" Namespace="CrystalDecisions.Web" Assembly="CrystalDecisions.Web, Version=11.0.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304" %> Line 3: <%@ Page language="c#" Codebehind="UpdateEventQueue.aspx.cs" AutoEventWireup="false" Inherits="CANBTV.UpdateEventQueue" %> Source File: /CANBTV_3_0_0/UpdateEventQueue.aspx Line: 1 Version Information:Microsoft .NET Framework Version:2.0.50727.3603; ASP.NET Version:2.0.50727.3082 There were no errors reported by Visual Studio. Not finding anything wrong in the code, I exchanged the positions of Line 1 and Line 2 ... the warning remained on Line 1, it did not follow the Axezz.WebControls line. So it isn't about the TagPrefix lines themselves, but something else. Due to changes in customer requirements, some lines had been removed from the .aspx and the aspx.cs source files, but those did not seem to be implicated and the HTML tags were still balanced and well-formed. I did have some trouble with the Designer ("Error creating control: Unknown server tag 'axp:AxpDataGrid'). Removing the TagPrefix line completely changed the error message shown where the control should be ("This control cannot be displayed because its tag prefix is not registered in this web form") - makes sense - so I put back the TagPrefix line, the error message returned to the "unknown server tag" one. What? Is this a problem with the TagPrefix line, third party controls, or as Peter Johnson's Blog implies, variable naming problems - use of inconsistent case? I started looking at the la