This is the title of my first article for http://www.sharepointmagazine.net/ where I introduce some of the troubleshooting utilities and tools that can really make a SharePoint developer’s life easier since troubleshooting can really be a nightmare for those who are new to the sharepoint platform.
Waiting for your feedback 🙂
http://sharepointmagazine.net/technical/development/getting-started-with-sharepoint-programming-simplifying-sharepoint-debugging-by-creating-the-troubleshooting-toolbox
Monthly Archives: March 2009
Restricted Read Permission Level
When you create a site collection from MOSS publishing site template , you get an OOB permission level called “Restricted Read” . The description of Restricted Read in SharePoint is “Can view pages and documents, but cannot view historical versions or review user rights information.”
This is true. But, you can also use this permission level to give users permission to open items in a list without letting them to navigate to the list and enumerate the list items. For example, if you have a document that you want to share with all the portal users, you can upload it to a document library and provide a link from the home page to it and you can still prevent the portal users from browsing the document library directly.
Nice and easy 🙂
Cannot access SSP administration site collection
Me and my colleagues @ ITWorx came across this weird issue on different environments when trying to access the SSP administration site collection.
Symptoms : When we try to navigate to the SSP administration site default page, we receive the error highlighted in red below. However, we were able to access other SSP administrative pages by typing the URL in the browser.
“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: The base type
‘Microsoft.Office.Server.Internal.UI.SharedServicesAdminDefaultPage’ is not allowed for this page. The type is not registered as safe.”
Resolution: Add the following line to the SafeControls Section in the web.config of the SSP web application.
<SafeControl Assembly=”Microsoft.Office.Server.UI, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” Namespace=”Microsoft.Office.Server.Internal.UI” TypeName=”*” />
It’s also worth mentioning that my friend Amir ElKady bought me a Pepsi Can for solving him this issue 🙂
Thanks Amir
Ayman El-Hattab's Technology Blog 