Security for Web part connections

It is possible to enable security for web parts from the Central Administration. Enabling or disabling this option will establish the webpart connections in the Page.

Navigate to Central Administration-> Application Management - > Application Security

In the "Security for WebPart Pages" page, Select the web application for which the web part connections need to be disabled,

In the Web part connections sections enable the Prevents users from creating connections between webparts, and helps to improve security and performance.

The webparts connections will not be enabled and the users are prevented from creating webpart connections

Before Enabling:

After Enabling:

Disable Right Click in SharePoint Site

You can prevent users from right-clicking in your sharepoint site. Add a content editor web part and add the following piece of code in the source editor of the content editor web part.

Save the content editor web part. Users are now prevented from the right click option on the page. Happy coding

Creating custom links in the Quick Launch bar

Quick launch bar is the left panel in the SharePoint site that is used for navigation.

1. Navigate to the Site Actions Menu to the Site Settings Page of your site

2. In the Quick Launch page the Add Heading is used to create a new Group in the Quick launch, and new link can also be added in the already existing Headings

3. To create a new Heading, click on the New Heading link which will open the following page,

4. To create a new link, click on the New Link and add the new link with the group header for the link

5. The new link is now created under the Heading Yahoo and the link is now visible in the Quick Launch bar

WhitePaper for SQL Storage and Performance for SharePoint

Microsoft has released a whitepaper that provides recommendations on the database architecture, Network Topology recommendations and the Physical storage recommendations. The whitepaper also provides information on monitoring, maintaining and troubleshooting storage issues. The whitepaper can be downloaded from, http://technet2.microsoft.com/Office/f/?en-us/library/ca472046-7d4a-4f17-92b1-c88a743a5e3c1033.mspx

Workflow Permissions in SharePoint 2007

Workflows are designed under the security concept that they run as System Account in the Windows SharePoint Services and the App Pool Identity on the server computer and domain. In Windows SharePoint Services the workflows always have administrator privileges, whatever privileges the App Pool has. This makes it possible for the workflows to perform actions routing of documents etc.

Workflows running under administrator privileges enable users who are not administrators to elevate their own privileges by running a workflow to perform actions they ordinarily could not. This setting cannot be changed, it is up to the workflow to detect user actions and decide whether or not to continue or rollback changes or impersonate a user to mimic their permissions.

When associating a workflow, the Start Options, allow users to manually start a workflow with edit permissions which is enabled by default. This means that any authenticated Windows SharePoint Services user with edit permissions on the list can start an instance of this workflow association. If the administrator checks the “Require Manage List Permissions to start the workflow”, then only the list administrators can start an instance of the workflow’s association. Administrators can use restrict users enabling user defined workflows associated to the site. This option is available in the Central Administration.





The enable user-defined workflows for this site option in the workflow settings of the application management of Central Administration, will enable custom workflows to be associated with the particular site. This option is enabled by default. Settings for alert notifications can also be changed for alert notifications need to be sent or not for internal users who do not have site access when they are assigned a workflow task, and also for sending alert notifications to external users to participate in workflow by sending them a copy of the document.

Programmatically retrieving Site Usage in SharePoint 2007

Site Usage reports can be retrieved programmatically by using the GetUsageData method from the SPWeb class. This method would return a Data Table that contains information about the usage of the site based on the specified type of report, interval, number of columns and the last day to display. The GetUsageData method can be obtained from the Microsoft.SharePoint Namespace.

Alternatively site usage reports can also be viewed from the site settings menu. However this option is available when it is enabled from the Central Administration's Usage Analysis Logging. The log file is located by default in the 12 hive of SharePoint in the LOGS folder. However there is an option available in central administration to change the logging path.

Summary Link Web Part

Summary Link Webpart can be used to provide a summary of links from both inside of your SharePoint site and also from outside for SharePoint. The Summary link webpart provides an easy way to build a page of links to various resources. This webpart is an out of the box webpart available in SharePoint. The Summary link webpart can be added to any page that supports the following welcome page layouts,

1. Advanced Search
2. Intranet Home
3. News home
4. People search results page
5. Search page
6. Search results
7. Site directory home
8. Welcome page with Table of contents

The summary link webpart can be configured to contain styles, headers, and groups. The links provided in this webpart can also contain images.

Activating Intellisense for CAML

XML files developed for Windows SharePoint Services 3.0 can be modified or new xml files for WSS 3.0 can be created using CAML. However by default Microsoft Visual Studio does not provide intellisense for CAML development. It is possible to enable intellisense for CAML based xml files in the following manner,
Create a new text file and name it as CAML.xml and add the following code,

targetNamespace="http://schemas.microsoft.com/sharepoint/"/>


Save the CAML.xml in the following path, C:\Program Files\Microsoft Visual Studio 8\XML\Schemas\CAML.xml

Shutdown and restart Visual Studio, intellisense will begin to work that rely on the following schema of CAML, http://schemas.microsoft.com/sharepoint/namespace

Intellisense can be enabled for any schema in a similar method, however visual studio will only detect the schema, only when after restarting the same as visual studio examines the xml files in the directory at startup to determine which xml schema to be loaded to drive intellisense.

CAML

CAML is Collaborative Application Markup Language (CAML) is an XML based language that is used in Windows SharePoint Services to define the fields and views used by sites and lists. CAML is also used to define tables in the Windows SharePoint Services database during site provisioning.

Site Customization using CAML
CAML can be used in various ways to customize a SharePoint site, including the following,

• In script or code that implements members of the Windows SharePoint Services object model, where CAML strings are passed through method parameters, assigned to properties, or returned by methods and properties
• In SOAP messaging that passes CAML strings to a Windows SharePoint Services Web service to interact remotely with a deployment
• In front-end site definitions used to instantiate SharePoint sites
• In Features to add specific functionality within a particular scope

SharePoint Errors

The following are some articles that are useful in identifying SharePoint errors. SharePoint errors are logged in the event viewer and in SharePoint logs located in the 12 hive in the following path. C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS

Error codes logged in the Event viewer
http://www.brienposey.com/kb/troubleshooting_sharepoint_errors.asp

Single SignOn Error codes and what they mean
http://blogs.msdn.com/harsh/archive/2007/03/21/single-signon-error-codes-and-what-they-mean.aspx

WebPart error
“A Web Part or Web Form Control on this Web Part Page cannot be displayed or imported because it is not registered on this site as safe”
http://www.bluedoglimited.com/SharePointThoughts/ViewPost.aspx?ID=189

To turn on Custom Errorhttp://www.andrewconnell.com/blog/archive/2007/02/01/5935.aspx

Feature Element in Feature.xml

The Feature Element tag in a feature.xml file defines the feature and specifies the location of assemblies, files, dependencies or properties that support the Feature.

Some of the attributes that can be defined in a Feature Element are,

1. ActivateOnDefault - This attribute when set to true states that the feature is activated by default during installation of the feature. This attribute is provided at the web application scope and does not work at the site collection or web level.
2. AlwaysForceInstall - This attribute can be set to true if the feature is installed by force, even if the feature is installed already.
3. AutoActivateInCentralAdmin - This attribute can be set to true if the feature is activated by default in Administrative Web site, site collection or central administration. This attribute does not apply to Farm Scoped features.

Though these attributes are optional they prove very useful at times.

Form Services Limitations

Infopath 2007 has many new features and controls, however the following are the controls and features of Infopath 2007 that are not supported by Infopath Form services.

The controls that are not supported in Infopath Form Services are,
1.ActiveX control
2.Bulleted list control
3.Choice group
4.Choice section
5.Combo box
6.Horizontal repeating table
7.Horizontal region
8.Ink picture control
9.Master/detail control
10.Multiple-selection list box
11.Numbered list control
12.Picture control
13.Plain list control
14.Repeating choice group
15.Repeating recursive section
16.Scrolling region
17.Vertical label

The business logic features that are not supported in Infopath Form Services are,
1.Userroles

The security related features that are not supported in Form services are,
1.Restricted Security Level
2.Form Design Protection
3.Information Rights Management

The data connection features that are not supported in Infopath Form Servcies,
1.Query data from a Microsoft Office Access database
2.Submit data to a Microsoft Office Access Database
3.Submit data to a Microsoft SQL server database

The filling out forms features that are not supported by Infopath Form services,
1.Merge data from multiple forms
2.Export data to Microsoft Office Excel
3.Export data to Web
4.Ink support
5.Offline support
6.Spell checking
7.AutoSave, AutoRecover, or crash detection features
8.Custom task panes
9.Add-in menus

The view related features that are not supported in Infopath Form Services
1.Word print views
2.Multiple print views at once
3.Print Page breaks, headers or footers

The programming features that are not supported in Infopath Form services
1.Scripting
2.COM add-ins

WSS 3.0 and MOSS SP1 has been released

You can get the latest of the SharePoint 2007 service packs from the following links,
Windows SharePoint Services 3.0 Service Pack 1 (SP1)
2007 Microsoft Office Servers Service Pack 1 (SP1)

Microsoft's SharePoint Capacity Planning Tool Beta

Microsoft has released the beta version of the SharePoint Capacity Tool. This tool as the name says it all is will guide you on the kind of infrastructure needs and farm topology design based on the number of users, network bandwidth, hardware availability etc.

You can get the tool from this Link

Change the Welcome Page in Publishing template of SharePoint

To change the welcome page of a SharePoint site based on the publishing template to a custom aspx page,

1. Place your aspx page in the _layouts folder of the 12 hive of SharePoint
2. Navigate to the Site Settings page from the Site Actions menu of your site
3. Under the Look and feel section, click on the welcome page option
4. Type the url of the custom welcome page in the _layouts folder
5. Click ok

w3wp associated with your SharePoint application

To find which w3wp is associated with your SharePoint application,

1. Open command prompt
2. Navigate to C:\Windows\System32
3. Type CScript iisapp.vbs

The iisapp.vbs is a vbscript file that lists all the worker processes along with their process ids running in the IIS

Reschedule or Change the interval of a SharePoint custom Timer Job

To reschedule or change the interval of a SharePoint custom Timer Job

1. Change the schedule interval in the custom code using the SPDailySchedule class of the SharePoint object model


2. Build and deploy in the GAC.


3. IISRESET


4. Go to the command prompt and navigate to the 12 hive of SharePoint


5. Uninstall the existing Timer feature, for example, stsadm.exe –o uninstallfeature –filename yourfeaturename\feature.xml


6. Install the new Timer feature, for example, stsadm.exe –o installfeature –filename yourfeaturename\feature.xml


7. Go to the windows services and restart the Windows SharePoint Services Timer

Unknown error during check in or check out

If you get an unknown error when you try to check in or check out your document in Microsoft Office SharePoint Server 2007, then it is possible that you have an incorrect installation of MOSS in your server.

Try the following KB article, for a detailed study for the symptoms and the workaround.
http://kbalertz.com/556031/Unknown-Error-SharePoint.aspx