Code blocks are not allowed in this file.

In Moss 2007 or SharePoint 2010, most of the times we need to create the custom master pages. In order to perform certain actions/functions, we need to insert code within those master pages.

Main problem comes into arena, when we try to use upload that master page into the master page gallery or copying into the file system, and use as system master page or site master page. Since the custom master page contains code with in it, so we used to get the below screen.

In order to solve this problem, we need to make entries into the corresponding web.config file by following the below steps.

1) Go to corresponding web.config file location which is located at the below location ( under c drive)

2) Open the web.config file , and under the <SafeMode><PageParserPaths> tag make the below entries.

< PageParserPath VirtualPath="/_catalogs/masterpage/*" CompilationMode="Always" AllowServerSideScript="true" IncludeSubFolders="true"/>

VirtualPath attribute should contains location where the master page is located. "/*" at the end of the /_catalogs/masterpage" in the virtual path attribute indicates to also include the subfolders.

Window could not start the SharePoint 2010 Timer service on Local Computer.

In SharePoint 2010, while starting the SharePoint 2010 Timer service, we get Error 1069 : The service did not start due to a logon failure like the below screen.

The main cause of this problem is that password of the account under which the SharePoint 2010 Timer service is running has been changed. So, we need to update this password in SharePoint 2010 Timer properties.

Steps to update password for timer service

1) Right click the SharePoint 2010 Timer service > properties

2) Click on Log On tab and enter password under This account option.

3) Click apply > Ok > restart the SharePoint 2010 Timer service.

 

 

 



 

 



 

This page allows a limit of 200 controls, and that limit has been exceeded.

In Moss/Sharepoint, some while playing with placeholders in the master pages we face the error like the below screen.

 



The above screen shows that the number of placeholders that can be included in a master page has been exceeded.

Solution

The solution for the above problem is that either
1) To remove placeholders from the master page or
2) (Best One) Increase the value of the MaxControls attribute in the web.config of the corresponding web application as highlighted below.