SharePoint Permission Dependency Chart

This Image speaks for Itself .. If you want more Visit this link.

Adding Server Side code to the Publishing Page Layouts - PageParserPaths

This article is to give a brief introduction for the Functionality of PageParserPaths tag in the Web.Config file of SharePoint. (It serves as a Reference for me In future and for someone out there looking for a similar implementation).

All the Layout pages in the SharePoint 2007 are derived from the class

Microsoft.SharePoint.Publishing.PublishingLayoutPage .

This works very well for most of the cases and customization. But there will be very chance that for some reason you want the actual page instance to have a completely different class. Might be a case where you are using a third part tool or a component. In this case if you try to change the base class or put in some custom server side code in to the page layout file, SharePoint will complain you with a parser error.

This Article describes the approach that will help you to put in the code for the layout pages. It works like charm.

On additions to the above article is that in case if you are concerned about allowing all the pages having the server code as defined by below tag

<PageParserPath VirtualPath="/_layouts/masterpage/*" CompilationMode="Auto" AllowServerSideScript="true"

IncludeSubFolders="true"/>

You can make a particular page to have server side code as below

<PageParserPath VirtualPath="/_layouts/masterpage/yourpage.aspx" CompilationMode="Auto" AllowServerSideScript="true"

IncludeSubFolders="true"/>

While configuring a single page, make sure that you remove the attribute IncludeSubFolders="true". If you leave this tag as it is, all you are going to get is a plain HTTP 500 error code which is hard to debug. Validation that SharePoint makes here is IncludeSubFolders="true" can be present only if the attribute VirtualPath ends with /*.

STSADM command – Quick Reference

This Poster will help you as Quick Reference for STSADM Command tool.

http://blogs.msdn.com/sharepoint/archive/2008/05/12/posters-for-sharepoint-stsadm-command-line-parameters-now-available.aspx

SQL Server and SQL Reporting Server SSRS - Quick Reference –FAQ’s

SQL Server

1. Add a Database user to a Database role:
   EXEC sp_addrolemember 'db_owner', 'yourdbusername'
   More here
   http://technet.microsoft.com/en-us/library/ms187750.aspx?PHPSESSID=rr1g5nuj29l79hrpjk7k0g1461
   
2. When you rename the SQL Server name:

In case if you have renamed the SQL Server recently and find a trouble to connect to the server using code. Try the below items.

• Use Query Analyzer and Connect to the SQL Server.
  
• Execute the command SELECT @@SERVERNAME AS 'Server Name'
  
• You will find the old name reflecting there.
  
• First run the command sp_dropserver 'old server name'
  
• And then run sp_addserver 'new server name', 'local'
  
• You should be good to go
  

SSRS Reporting Servers:

1. To change the User Name or the Server name of the Reporting Server instance [SSRS].
   
2. When you get rsreportserverdatabaseunavailable error when connecting to SQL Server Reporting server.
   

For the above case you have to use the tool rsconfig that will change the user and server details.

http://msdn.microsoft.com/en-us/library/ms162837.aspx

Unable to Create new SSP – Created new Web Application not getting listed in the list.

When you try to create a new SSP you might run in to surprise that the newly created web application will not get listed in the list web application of new SSP page.
One quick check you need to perform in this case is to check the App Pool account of the Web Application. If it is Network Services then that the issue. You can find the answer in same New Shared Services Provider page.

J

SharePoint – Quick Help Commands!!!

Process ID for the Web Application:

While debugging SharePoint application mainly SharePoint Workflow you will need to find the Process ID of the Web Application you are trying to Debug. If each of the web application runs in same user account its tough to find the same.

Run the below command that will list all the Application Pool and Its Process ID

c:\windows\system32\cscript.exe c:\windows\system32\iisapp.vbs

Run To access STSADM from any directory in command Prompt:

Add the 12Hive\Bin path to the Windows Environment PATH Variable.

More: Here

InfoPath Form Services 2007

It was hard for me to understand how the InfoPath form services licensing work and how it is related to SharePoint server 2007 (MOSS 2007). I stumbled to find the link "Manage InfoPath Form Templates" in my local Development environment which is a Standard SharePoint CAL installation. Today I Googled it and managed to get few information regarding it.

• We know that InfoPath can be viewed in the browser without InfoPath Client.
• How? Well InfoPath Form Services help you to render the InfoPath form in the Browsers without InfoPath client installed in your machine.
• You can get the InfoPath Form Services in two ways (Assuming that you have a Standard SharePoint 2007 Installation or WSS 3.0 Installation).
  
  • Buy a License for Microsoft Office Forms Server 2007 and install it in your SharePoint / (WSS 3.0) Server Farm. [This is the only option in case if you have the WSS 3.0 Installation]
    
  • Upgrade your SharePoint Server farm to the Enterprise License. [Form Services Features are supported in Enterprise Version].
    

If you still want to get confused more J . Please refer to the below links that give you the information on the various SharePoint licensing favors.

http://office.microsoft.com/en-us/formsserver/FX101865111033.aspx http://littletalk.wordpress.com/2008/02/07/where-is-infopath-forms-services-section/
http://littletalk.wordpress.com/2008/04/24/this-form-template-is-browser-compatible-but-it-cannot-be-browser-enabled-on-the-selected-site/