Parser Error 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 l
ASP.NET Community Standup Forums Help Home/ASP.NET Forums/Retired Forums/Migrating from Visual Studio .NET 2003 to Visual Studio 2005 (RETIRED.../parsing error: ambiguous match found parsing error: ambiguous match found RSS 20 replies Last post Sep 24, 2009 04:10 PM by mbaladi ‹ Previous Thread|Next Thread › Print Share Twitter Facebook Email Shortcuts Active Threads Unanswered Threads Unresolved Threads Support Options Advanced Search Reply newliya Member 1 Points 65 Posts parsing error: ambiguous match found Apr 18, 2006 01:03 PM|newliya|LINK The web application was migrated from 2003 to 2005. When I tryied to open one http://stackoverflow.com/questions/3520809/parser-error-message-ambiguous-match-found page, I got the error: Parser Error Message: Ambiguous match found. Source Error: Line 1: Line 2: <%@ Register TagPrefix="uc1" TagName="TabControl" Src="../TabControl.ascx" %> Line 3: <%@ Register TagPrefix="uc1" TagName="TreeView" Src="../MiscControls/Tree/TreeView.ascx" %> Source File: /xpede.net/TeamApproval/TeamApproval.aspx Line: 1 Could somebofay has any idea? Thanks a lot! Liya Liya Reply ScottGu Participant 1840 Points 2004 Posts MicrosoftModerator Re: parsing error: ambiguous match found Apr 19, http://forums.asp.net/t/983007.aspx?parsing+error+ambiguous+match+found 2006 03:27 AM|ScottGu|LINK Hi Liya, The problem is that there is now a "Treeview" control built-into ASP.NET 2.0 -- and so this user control class name is conflicting with it. Can you try renaming your control (specifically the class name)? That should fix it. Thanks, Scott Reply newliya Member 1 Points 65 Posts Re: parsing error: ambiguous match found Apr 19, 2006 11:00 AM|newliya|LINK Thanks for your reply. I changed the class name and the control name, but I still got the same 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 Error: Line 1: <%@ Register TagPrefix="uc1" TagName="TabControl" Src="../TabControl.ascx" %> Line 2: <%@ Register TagPrefix="uc1" TagName="MyTreeView" Src="../MiscControls/Tree/TreeViewWRC.ascx" %> Line 3: <%@ Page language="c#" Codebehind="TeamApproval.aspx.cs" AutoEventWireup="false" Inherits="WRC.ProjAcct.AspClient.TeamApproval.TeamApproval"%> Source File: /xpede.net/TeamApproval/TeamApproval.aspx Line: 1 What do you think the possible causes are? Thanks a lot, Liya Liya Reply newliya Member 1 Points 65 Posts Re: parsing error: ambiguous match found Apr 19, 2006 04:20 PM|newliya|LINK Hi Scott, The additional i
C# 4 Code Quality coffeescript ConcurrentDictionary Conference Configuration Continuous Delivery CTP/Beta customer service Database data design data dictionary DDD DDD https://colinmackay.scot/2010/08/23/parser-error-message-ambiguous-match-found/ Scotland DDD South West Debugging design patterns Entity Framework error handling express Extension Methods fun git GitHub Google Analytics hiring HTML IIS Installation Internet Explorer javascript http://invisiblesoftware.blogspot.com/2009/11/aspnet-runtime-error-ambiguous-match.html jQuery learning LINQ node.js object oriented design Parallel.ForEach parallelisation parallelization PHP presentation refactoring Scottish Developers security SES software development practices Source Control Spatial SQL SQL Injection Attack parser error SQL Server SQL Server 2005 SQL Server 2008 TFS unit testing virtual earth visual studio Visual Studio 2008 Visual Studio 2010 Windows 7 Windows Vista Xander.PasswordValidatorArchives Archives Select Month September 2016 July 2016 April 2016 February 2016 December 2015 September 2015 August 2015 July 2015 June 2015 May 2015 April 2015 March 2015 parser error ambiguous February 2015 November 2014 October 2014 July 2014 May 2014 April 2014 December 2013 October 2013 August 2013 July 2013 May 2013 April 2013 March 2013 January 2013 December 2012 November 2012 October 2012 September 2012 August 2012 July 2012 June 2012 May 2012 April 2012 March 2012 February 2012 January 2012 November 2011 October 2011 September 2011 August 2011 July 2011 June 2011 May 2011 April 2011 March 2011 February 2011 January 2011 October 2010 September 2010 August 2010 July 2010 June 2010 May 2010 March 2010 February 2010 January 2010 December 2009 October 2009 September 2009 August 2009 July 2009 June 2009 May 2009 April 2009 March 2009 February 2009 January 2009 December 2008 November 2008 October 2008 September 2008 August 2008 July 2008 June 2008 May 2008 April 2008 March 2008 February 2008 January 2008 December 2007 November 2007 October 2007 September 2007 August 2007 July 2007 June 2007 March 2007 February 2007 Dec
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 n