Parser Error Sharepoint 2007
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 in custom asp.net sharepoint page up vote 1 down vote favorite Can anyone help me with this error? full image here It happens usually once a day when trying to load any one of a number of custom asp.net pages in my sharepoint web site. If I recycle my application pool the error disappears (usually for the day). So far this is what I’ve tried to eliminate the error (which has helped reduce the number of occurrences, but not solved it) Set the IIS_WPG, Local Service and Network Service account to Full Control permission on the folder %windir%\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files Added
A few weeks ago I was updating the master page for a SharePoint 2007 (WSS) site. The client wanted the site updated to reflect the new look and feel that is being applied to another set of sites in the organization. I created a new theme and master page, which I already wrote about here and here. It worked well, except for a few pages on a subsite. On those pages, I got the following error: Server Error in '/' Application. Parser Error Description: An http://stackoverflow.com/questions/1102961/parser-error-in-custom-asp-net-sharepoint-page 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: Code blocks are not allowed in this file. I decided to go comb through my new master page and compare it to the existing master page that was already working. After http://geekswithblogs.net/kjones/archive/2010/03/30/139005.aspx going through them line by line several times, I had no clue what would be causing the error because they were basically the same! It turns out, it was a combination of two things. First, on a few of the pages in the site, there was some include code (basically an <% EVAL()%> snippet). This was the code that was triggering my error “Code blocks are not allowed in this file”. However, this code was working fine with the previous master page. I decided to then try doing a full deployment of the site with the new master page, and it worked fine! Apparently, if the master page is deployed using a Feature, then it is granted permission to allow code blocks, but if you upload pages either using web UI or SharePoint Designer, then the pages won’t be able to use code blocks. I haven’t been able to pin down the rules or official info about this, but I thought others might find it useful anyway.
dealt with before. When we tried to visit any System pages (those that use the default.master) in a SharePoint 2007 application, we got the following http://blog.tylerholmes.com/2011/09/sharepoint-2007s-most-common-and.html error. The DataSourceID of 'TopNavigationMenu' must be the ID of a control of type IHierarchicalDataSource. A control with ID 'topSiteMap' could not be found. More formally, it looked like this: When we http://www.ronaldwidha.net/2010/05/15/sharepoint-2007-parser-error-on-updating-page-layout/ tried to load other pages (where we were loading custom user controls from disk) we got another misleading error. An error occurred during the parsing of a resource required to service this parser error request. Please review the following specific parse error details and modify your source file appropriately. Believe it or not, this is one of SharePoint 2007's most well known red herrings. I post this in part because: A lot of the existing content on the web doesn't fully document this error and how to troubleshoot it (misleading). I've run into it enough times (and forgotten parser error sharepoint the solution) that I feel a need to document it somewhere that I can easily look it up. The Solution The first thing to know about this error is that it gets thrown for a wide variety of reasons. While most often it has something to do with the web.config of a SharePoint 2007 web application, the root cause can get pretty tangential to a simple web.config parser error. The first step to troubleshooting this, is to get an error message that actually speaks to the error at hand (the two above don't, so don't try to troubleshoot off of them). This genre of error seldom puts helpful details into the event log and so you should: Open up the latest log file in the 12 hive (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Logs). I usually go to the end of the file and search up for terms like "error" or "exception". You should be able to find some error. These can be quite varied from type/assembly resolution errors to parsing in the web.config. From here troubleshoots typically go one of two routes. Either the error itself will inform you
Type. After uploading the new aspx, I’m getting the following error: Server Error in ‘/' 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: Only Content controls are allowed directly in a content page that contains Content controls. Source Error:
...