IT knowledge sharing - SharePoint (MOSS 2007 and 2010 )

Client Object Model - retrieve document library permission

2011-11-18T00:10:00.001-08:00

public void CheckPermission(string siteUrl, string ListName)

{
ClientContext clientContext = new ClientContext(siteUrl);
List curList = clientContext.Web.Lists.GetByTitle(ListName);

clientContext.Load(curList.RoleAssignments);
clientContext.ExecuteQuery();

foreach(RoleAssignment ra in curList.RoleAssignments)

{
var p = ra.Member;
clientContext.Load(p);
var q = ra.RoleDefinitionBindings;
clientContext.Load(q);
clientContext.ExecuteQuery();

foreach (RoleDefinition subq in q)
{
Console.WriteLine(p.Title+"=="+subq.Name);

}

}

}

client code : check all the Sharepoint 2010 group Owner

2011-10-12T05:09:00.001-07:00

static void Main(string[] args)
{

           String sURL = "http://xxxxx/sites/yyyyy";


           ClientContext clientContext = new ClientContext( sURL);
           GroupCollection collGroup = clientContext.Web.SiteGroups;

clientContext.Load(collGroup);

           clientContext.Load(collGroup);
               //groups => groups.Include(
                //   group => group.Owner));

clientContext.ExecuteQuery();

           foreach (Group oGroup in collGroup)
           {
               Console.WriteLine(oGroup.Title +"== "+ oGroup.OwnerTitle);

           }

Console.ReadLine();

}

Retrieve all document library View method with console c#

2011-10-06T07:15:00.001-07:00

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using Microsoft.SharePoint.Client;
using SP = Microsoft.SharePoint.Client;

namespace ExtractView
{
    class SPView
    {
        public void allview(string siteUrl , string doclib )

        {

ClientContext clientContext = new ClientContext(siteUrl);
Web site = clientContext.Web;

List targetList = site.Lists.GetByTitle(doclib);
ViewCollection collView = targetList.Views;

ViewCreationInformation viewInfo = new ViewCreationInformation();

clientContext.Load(collView);
clientContext.ExecuteQuery();

Console.WriteLine("this is for document lib" + doclib);

foreach (View oneView in collView)
Console.WriteLine(oneView.Title);

}

public void alldoc(string siteUrl)
{

             ClientContext clientContext = new ClientContext(siteUrl);
            ListCollection collList = clientContext.Web.Lists;

            clientContext.Load(collList);
            clientContext.ExecuteQuery();

foreach (SP.List olist in clientContext.Web.Lists)

{

                allview(siteUrl, olist.Title);

            }

}

}
}

=============================================================================================================

to call this method please create static void main to call it.

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using Microsoft.SharePoint.Client;

namespace ExtractView
{
    class Program
    {
        static void Main(string[] args)
        {
               SPView listview = new SPView();

listview.alldoc(args[0]);

}

}
}

=================================================================================================================

run the xxx.exe parameter(URL)

Code to retrieve all the list item detail

2011-09-14T07:44:00.001-07:00

using System;
using System.Linq;
using Microsoft.SharePoint.Client;
using SP = Microsoft.SharePoint.Client;

namespace Microsoft.SDK.SharePointServices.Samples
{
    class RetrieveListItemsInclude
    {
        static void Main()
        {
            string siteUrl = "http://MyServer/sites/MySiteCollection";

            ClientContext clientContext = new ClientContext(siteUrl);
            SP.List oList = clientContext.Web.Lists.GetByTitle("Announcements");

            CamlQuery camlQuery = new CamlQuery();
            camlQuery.ViewXml = "<View><RowLimit>100</RowLimit></View>";

            ListItemCollection collListItem = oList.GetItems(camlQuery);

            clientContext.Load(collListItem,
                 items => items.Include(
                    item => item.Id,
                    item => item.DisplayName,
                    item => item.HasUniqueRoleAssignments));

            clientContext.ExecuteQuery();

            foreach (ListItem oListItem in collListItem)
            {
                Console.WriteLine("ID: {0} \nDisplay name: {1} \nUnique role assignments: {2}",
                    oListItem.Id, oListItem.DisplayName, oListItem.HasUniqueRoleAssignments);
            }Console.ReadLine();
        }
    }
}

source code from here

my first client object testing with the windows form :)

2011-09-05T09:14:00.001-07:00

follow the step here : http://www.sharepointkings.com/2011/07/client-object-model-part-1.html

please remember to add the Microsoft.Sharepoint.Client and Microsoft.Sharepoint.Client.Runtime to References.

*my small step over the cilent obkect model over sp2010

using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Windows.Forms;
using Microsoft.SharePoint.Client;

namespace SP2010
{
    public partial class Form1 : System.Windows.Forms.Form
    {
        public Form1()
        {
            InitializeComponent(); //not sure this is for what
        }

      public void LoadData()
        {
            string webUrl = "http://xxxxx/sites/content/support"; //replace this with your site URL

ClientContext context = new ClientContext(webUrl);

Web web = context.Web;

context.Load(web);

context.ExecuteQuery();

this.label1.Text = web.Title + " " + web.Description;

this.label2.Text = webUrl;

}

private void button1_Click(object sender, EventArgs e)
{

              LoadData();
        }
    }
}

Metadata navigation > new SharePoint Server 2010 feature that enables users to dynamically filter lists

2011-08-25T08:06:00.001-07:00

Metadata navigation is a new SharePoint Server 2010 feature that enables users to dynamically filter lists so they can find what they need. Metadata navigation enables users to select filter options, and it handles performing the query in the most efficient manner possible. Metadata navigation consists of two parts. One part is a set of navigation controls that let a user filter a list that has navigation hierarchies and key filters. The second part is a mechanism for rearranging and retrying queries.

Metadata navigation has retry and fallback logic that attempts to perform queries efficiently by using indexes. If a query will return too many results, the query falls back and returns a subset of the results for better performance. If no appropriate query can be made, fallback occurs and the filters are performed on a limited set of results. Metadata navigation automatically creates indexes. Together retry, fallback, and index management make metadata navigation a very important part of working effectively with large lists. There are two kinds of filtering mechanisms: navigation hierarchies and key filters.

Navigation hierarchies use a tree control to navigate hierarchies of folders, content types, choice fields, or managed metadata term sets. This enables users to use a tree control to pivot on a metadata hierarchy, much as how they navigate folders. When users select an item in a hierarchy for a managed metadata column, all items that match the specified term or any of its descendant child terms are displayed. This is called descendant inclusion, and it can be used on fields that are tied to a managed metadata term set. Users can select the item again to filter on only that particular term and not include the descendant child terms. All metadata navigation queries are recursive and display results from all the folders in the list.

Key filters can be configured to perform additional filtering of results within the hierarchy. For example, you can add the Modified By column as a key filter and then type a user name to obtain results where Modified By matches the entered user. For more information, see Metadata navigation and filtering (http://go.microsoft.com/fwlink/?LinkId=219154). The following figure shows an example of metadata navigation hierarchies and key filters.

from : http://technet.microsoft.com/en-us/library/cc262813.aspx

First step at sharepoint2010 Client object model

2011-08-05T07:14:00.001-07:00

information from : http://msdn.microsoft.com/en-us/library/ee857094(office.14).aspx#Y4347

my first small step

To build the application

Start Microsoft Visual Studio 2010.
On the File menu, point to New, and then click Project.
In the New Project dialog box, in the Recent Template pane, expand Visual C#, and then click Windows.
To the right of the Recent Template pane, click Console Application.
By default, Visual Studio creates a project that targets .NET Framework 4, but you must target .NET Framework 3.5. From the list at the upper part of the File Open dialog box, select .NET Framework 3.5.
In the Name box, type the name that you want to use for your project, such as FirstClientApiApplication.
In the Location box, type the location where you want to place the project.
Figure 2. Creating a solution in the New Project dialog box
Click OK to create the solution.

To add references to the Microsoft.SharePoint.Client assembly and Microsoft.SharePoint.Client.Runtime assembly

The classes that you use in a client object model application are located in Microsoft.SharePoint.Client.dll and Microsoft.SharePoint.Client.Runtime.dll. As I mentioned, before you add the references, you must copy those assemblies from the server that runs SharePoint Foundation to the client development computer.
On the Project menu, click Add Reference to open the Add Reference dialog box.
Select the Browse tab, navigate to the location where you put the Microsoft.SharePoint.Client.dll and Microsoft.SharePoint.Client.Runtime.dll. Select both DLLs, and then click OK as shown in Figure 3.
Figure 3. Adding references to the assemblies

To add the sample code to the solution

In Visual Studio, replace the contents of the Program.cs source file with the following code.

using System;
using Microsoft.SharePoint.Client;

class DisplayWebTitle
{
    static void Main()
    {
        ClientContext clientContext = new ClientContext("http://intranet.contoso.com");
        Web site = clientContext.Web;
        clientContext.Load(site);
        clientContext.ExecuteQuery();
        Console.WriteLine("Title: {0}", site.Title);
    }
}
Replace the URL in the ClientContext constructor with the URL to the SharePoint site. Build and run the solution. The example prints the title of the site.

Just as with the SharePoint Foundation server object model, you create a context for the SharePoint site that you want to access. You can then retrieve a reference to the site from the context.

The call to the ExecuteQuery method causes the SharePoint Foundation 2010 managed client object model to send the request to the server. There is no network traffic until the application calls the ExecuteQuerymethod.

An important point to make about this example is that the call to the Load method does not actually load anything. Instead, it informs the client object model that when the application calls the ExecuteQuery method, you want to load the property values of the siteCollection object.

This is the model that all interactions with the server take:

You inform the SharePoint Foundation 2010 managed client object model about the operations that you want to take. This includes accessing the values of properties of objects (for example, objects of the Listclass, ListItem class, and Web class), CAML queries that you want to run, and objects such as ListItem objects that you want to insert, update or delete.
Then you call the ExecuteQuery method. No network traffic occurs until you call the ExecuteQuery method. Until that point, your application is only registering its requests.

As you can see from this example, at its simplest, you first set up a query, and then you execute the queries. This causes the client object model to send traffic to the server and receive a response from it. This next section reviews the model in detail and shows why it is designed the way it is, and finally, how you can build applications by using the model.

The days don't have access to SharePoint server

2011-08-03T06:51:00.001-07:00

After change the Role from System Engineer to Web design advisor (Content Management ) , no more privilege to log in server to run STSADM and so on ... :(

ha ha, sometime even site collection admin privilege also don't have ....ask me how to do make mine work automated? Look like is the time to start on Using the SharePoint 2010 Managed Client Object Model

Blog about this area:

http://blogs.msdn.com/b/ericwhite/archive/2009/11/20/using-the-sharepoint-2010-managed-client-object-model.aspx

http://msdn.microsoft.com/en-us/library/ee857094(office.14).aspx

is time to start learn how to edit coding!! ha ha :P this is good start from me to start involve in sharepoint developer area.

Dream target : create migration tools...ha ha..

Change the name of the button name on SharePoint list

2011-07-06T20:02:00.001-07:00

http://www.mindfiresolutions.com/Renaming-the-menu-items-in-SharePoint-Site-Libraries-and-Lists-for-a-Specific-Site-209.php

Renaming the menu items in SharePoint Site Libraries and Lists for a Specific Site

Author: Samarendra Swain

In SharePoint document Library/List we find menu items like New, Uploads, Actions and Settings etc. At times there might be requirements to rename these menu items for a specific site. The following Javascript function can be used to achieve the objective.

The code snippet shown below can be called from inside the specific SharePoint Page.

e.g AllItems.aspx page inside a Document Library/List.

This javascript function needs to be called on Page load event using _spBodyOnLoadFunctionNames.push method.

_spBodyOnLoadFunctionNames.push("renameMenuItem('New', 'My New')");

_spBodyOnLoadFunctionNames.push("renameMenuItem('Settings', 'My Settings')");

</script>

How to update list item from Collect Data from user at workflow

2011-05-24T20:39:00.001-07:00

learn new knowledge on how to update on of the column at list item from the collect data from user.

when user received the alert from the workflow , user will go to update the task. we can customize the data we need with using Collect Data from user Actions from workflow.

below is the step to return the data have input to task and update on the list item.

http://office.microsoft.com/en-us/sharepoint-designer-help/collect-data-from-a-user-in-a-workflow-HA010209808.aspx?CTT=5&origin=HA010240415

When you design a workflow, you often want to collect information from a participant in the workflow, and then use that information for making further decisions. For example, you might want a workflow to ask a participant to review a document, and then have the workflow perform different actions depending on whether the reviewer approves or rejects the document.

To accomplish this, you add the Collect Data from a User action to your workflow. This action assigns a task to the participant, prompting them to provide the needed information in a custom task form. The information from the custom task form is stored in an item in the Tasks list. At a decision point in a later step, the workflow retrieves the stored information and evaluates it to decide which branch to run.

This article shows you how to collect data from a workflow participant, and then how to use that data in your workflow for making further decisions.

In this article

Which action should I use to create a task?

Tasks are the primary way for a workflow to interact with participants in the workflow. If you want your workflow to require work from people or to get information from them, you can have the workflow create and assign a task. Each time a workflow assigns a task, the workflow pauses until that task is completed. The workflow resumes only when a participant clicks the Complete Task button on the task form.

There are three different actions that create a task, and each action is designed for a specific kind of situation:

Collect Data from a User This action assigns a task to a single user or group and returns the unique ID of the task item that stores the user's answers, so that the workflow can later look up this information by using the ID. With this action, you use the Custom Task Wizard to design a custom task form that collects the information you want. This action creates a task that can be assigned only to a single user or group. If you assign this task to a group, each member of the group receives a task notification, but only one task item is created, and the workflow pauses only until the first person to respond completes the task.
Assign a Form to a Group This action assigns a form to one or more users, and then stores the responses as values in the Tasks list. Unlike the previous action, this action can assign a task separately to multiple people, and the workflow pauses until each person completes their task before it resumes. Also unlike the previous action, this action does not return the ID of the task item for any of the responses, so the workflow cannot look up and use that information later as the basis for making comparisons or decisions. With this action, you also use the Custom Task Wizard to create a custom task form. For more information, see the articleAssign a form to a group in a workflow.
Assign a To-do Item Unlike the other two task actions, this action creates a task form that has no form fields to fill out but instead uses a form where the user simply clicks a Complete Task button when the task is finished. This task can be assigned separately to multiple people, and the workflow pauses until each person marks their task as complete. This action does not return the ID of the task item — and doesn’t really need to because the task does not collect any information that you might want to reference later. For more information, see the article Assign a to-do item in a workflow.

The following table summarizes this information.

ACTION
RETURNS THE TASK ID FOR WORKFLOW LOOKUPS?
CREATES MULTIPLE TASKS?
ENABLES YOU TO DEFINE FIELDS ON THE TASK FORM?

Collect Data from a User
Yes
No
Yes

Assign a Form to a Group
No
Yes
Yes

Assign a To-do Item
No
Yes
No

In addition, several limitations apply to all three task actions:

When a workflow assigns a task to a group that is identified by a single alias or address, the workflow creates only one task item, which is then shared by the entire group. Any member of the group can edit that single task form and click the Task Complete button. To assign individual tasks to multiple users (only possible with the Assign a Form to a Group or Assign a To-do Item action), enter each user individually in the Select Usersdialog box.
All of the tasks assigned by a single workflow action must be completed before the workflow can continue. If the workflow action assigns individual tasks to six participants, for example, you cannot direct the workflow to continue after only three of the six tasks are completed.
After a task is assigned to a participant by the workflow, that task cannot be transferred to any other participant (by delegation, forwarding, etc.). However, anyone with the default Contribute permission level to the Tasks list can edit the task item and thus allow the workflow to continue.
A workflow can use each task only once. After you create a task by using the Custom Task Wizard, there is no way to reuse that task later in the workflow. You can create another task that performs the same function, but the task's name will have to be different and unique.

TOP OF PAGE

What is a custom task form?

Each time that you use one of the three task actions to create a task, Microsoft Office SharePoint Designer 2007 automatically generates a custom task form for that task. The custom task form is the page that is presented to the workflow participant when they edit the task in the browser.

When you create a task by using the Collect Data from a User or Assign a Form to a Group action, the custom task form can have as many form fields as you choose to create. This example asks the user to enter information in only one field named "Review status".

In Office SharePoint Designer 2007, the custom task form appears as an .aspx page in the folder for that workflow. The file name of the custom task form corresponds to the name that you give the task in the Custom Form Wizard.

Custom task forms are attached to the site's default master page and contain a Data Form Web Part to interact with the workflow. The custom task form can be customized for layout and appearance — for example, you can attach a different master page or modify the styles. However, to change what fields appear on the form, you must use the Custom Task Wizard in the Workflow Designer. You cannot change the form fields by editing the Data Form Web Part directly. If you make other customizations to the Data Form Web Part (for presentation and not for functionality), note that those changes are lost each time that the workflow is recompiled. Customizations to the rest of page are preserved.

To change the fields on the custom task form, you must open the workflow in Office SharePoint Designer 2007 (File menu, Open Workflow command). When you open the workflow and edit the task by using the Custom Task Wizard, you see the following warning.

If you modify the custom task form and recompile the workflow, all running instances of the workflow continue to run using the new form. If you delete or modify fields (for example, by changing their type or renaming them), a workflow error will occur if the running instances of the workflow reference data that is not what is expected. For example, a running workflow may do a lookup and expect a field to contain data (be non-empty) but now it is empty, or the field may have changed type. Therefore, it is important not to make any change that deletes, renames, or otherwise alters form fields that currently running workflow instances may attempt to reference.

In addition to the custom task form, each time that you use one of the three task actions to create a task, Office SharePoint Designer 2007 automatically generates a content type for that task in the Tasks list. The content type defines the available fields and what format they use, as you specified in the Custom Task Wizard. The name of the content type matches the name that you give the task in the Custom Form Wizard. For example, if you create a task named "Review document", you will see a content type with that name on the Settings page of the Tasks list.

We recommend that you modify workflow content types only by opening the workflow in Office SharePoint Designer 2007, and not by modifying the columns or other settings for the content type in the browser. Modifying the content type in the browser can potentially break the custom task form that it is associated with.

TOP OF PAGE

What is a list item ID?

A list item ID is a unique row number. When a workflow participant clicks eitherComplete Task or Save Draft on the custom task form, the information submitted in the form is stored in an item in the Tasks list. The content type for that task defines the columns, and the list item ID identifies a specific item, or row. Each item in the Tasks list (or any list or library) has a unique ID. In the browser, you can add the ID column to any view of a list or library.

In addition, when you view a list item on a page in the browser — for example, when you click View Properties to see the item details on DispForm.aspx — the ID of that list item is visible in the URL as part of the query string. All standard SharePoint forms contain an ID parameter in the query string section of the URL.

When a workflow runs the Collect Data from a User action, the workflow creates a single task and stores the list item ID of that task in a variable. The workflow can later use that variable to look up the specific task item.

TOP OF PAGE

Step 1: Collect data from a user

First you want to use the Collect Data from a User action to create the custom task form, assign the task to a single user or group, and then store the ID of the task item in a variable. The workflow will later use the task item ID to look up the values submitted by the user in the task form.

In this example, your team uploads documents to a library named "Documents for review". When a document is added to the library, the workflow creates a task named "Review document". The person to whom the task is assigned must choose one of two options from a drop-down menu when they edit the task: Approved or Rejected.

NOTE This workflow is a custom approval workflow, but it does not use the Content Approval feature in Windows SharePoint Services and does not change the Approval Status field of the document. The Content Approval feature in Windows SharePoint Services presumes two different permission levels: one that does not include the Approve Items permission (for people submitting content for approval), and a second that does include the Approve Items permission (for people approving content). However, a workflow designed in Office SharePoint Designer 2007 always impersonates the permission level of the person who starts the workflow. If a person who does not have the Approve Items permission starts a custom workflow that tries to update the Approval Status field of the current item, the workflow will stop because the person who started the workflow does not have permission to approve items.

On the File menu, point to New, and then click Workflow.
On the first page of the Workflow Designer, name the workflow, choose the list or library that the workflow will be attached to, and then select the check boxes for the start options that you want.

Click Next.
Click Actions, and then click Collect Data from a User.

If this action does not appear in the list, click More Actions to see the full list.

In the action, click data.
On the first page of the Custom Task Wizard, click Next.
In the Name box, type a name for this task.

NOTE The task name must be unique in the current site.

In the Description box, type any general instructions to the recipient of the task.

This description appears at the top of the custom task form, so include here any instructions that you want the workflow participant to see, not just a general description.

Click Next.
Click Add to define a custom form field for this task.
In the Field name box, type a name for this field.
In the Description box, type the question for which this form field is storing the answer.
In the Information type list, choose an option that formats the field appropriately for the type of information that you are collecting.

Click Next.
The next page of the wizard varies depending on the Information type that you chose on the previous page. Specify the settings that you want.

In this example, type Approved, press ENTER, and then type Rejected.

In the Display as list, click Drop-down menu.
Clear the Allow blank values check box because you want the reviewer to choose one of the two options.

Click Finish twice.

The following illustration shows how this task will be displayed to the workflow participant in the browser when they edit the task. This is the custom task form — Review document.aspx — that you just designed by using the Custom Task Wizard.

Back in the Workflow Designer, you still need to set the second and third parameters in the Collect Data from a User action.

In the action, click this user.
In the Select Users dialog box, type a name or e-mail address, or click an existing user or group in the list, and then click Add.

NOTES

With the Collect Data from a User action, the workflow creates only one task, which you can assign to only one person or group. For more information, see the earlier section Which action should I use to create a task?
Instead of entering a specific user name or e-mail address, you can store this information in a separate list, and then use a workflow lookup to get this information. This way, various users can be configured as workflow participants without you having to modify the workflow itself. Alternatively, you can create a new SharePoint group, and then add users to the group whom you want to be workflow participants. For example, you can create a group named Approvers, add one or more users to it, and then configure this group as part of the Collect Data from a User action (keeping in mind that only one task is created, which can be edited by only one person).

Click OK.
In the action, click the third parameter, and then click Create a new variable.

You want to create a new variable instead of using the default name (Variable: collect) when your workflow will have multiple variables and you want to give the variable a more descriptive name.

In the Edit Variable dialog box, type a name that describes the value that the variable is storing.

For this variable, List Item ID is the only choice in the Type list. For more information about list item IDs, see the earlier section What is a list item ID?

Click OK.

At this point, your action should look like this.

TOP OF PAGE

Step 2: Set a workflow variable

At this point in the workflow, a workflow participant submits a completed task, and the review status that person submits is stored in a field or column in the Tasks list, as shown here.

How do you get at this information to use it in another step in the workflow? You use the Set Workflow Variable action to look up the value of the Review status field for the task that the user edited, and you store the value of this field in a new variable — in this example, named Review status.

By looking up and storing the review status in a new variable, you can now use this variable as the basis for future comparisons. This is a best practice because the workflow now makes it clear where the data is coming from, and this data can be reused more easily — multiple times, if necessary.

Click Actions, and then click Set Workflow Variable.

If this action does not appear in the list, click More Actions to see the full list.

In the action, click workflow variable, and then click Create a new variable.

In the Edit Variable dialog box, type a name that describes the value that the variable is storing.
In the Type list, click the type of data that the variable is storing.

In this example, click string because this variable will store the review status ofApproved or Rejected, which are both text strings.

Click OK.
In the action, click value, and then click Display data binding.
In the Define Workflow Lookup dialog box, choose the following options:
- Source: Tasks If more than one tasks list is available, choose the list that contains the custom form field that you created in the previous section.
- Field: Review status Choose the custom form field that you created in the previous section.
- Field: Tasks:ID
- Value: Click Display data binding.
In the second Define Workflow Lookup dialog box, choose the following options:
- Source: Workflow Data
- Field: Variable: ID of Review document task

Click OK.

The final workflow lookup should resemble the following. This lookup says, "Go to the Review status field in the Tasks list. Then go to the row in the Tasks list whose ID matches the ID stored in the variable for this instance of the workflow." If the workflow runs and creates a task whose ID is 3, this lookup retrieves the value of the Review status column from the third row in the Tasks list. The next time the workflow runs, this ID may be 4, so the lookup goes to the fourth row, and so on.

Click OK.

At this point, your rule should look like this.

TOP OF PAGE

Step 3: Use the variable to make decisions

In step 1, you created a custom task form to collect data from a user and store the ID of the task item in a variable. In step 2, you used the task ID variable to look up the user response and store that particular response in a new variable. Now that you have this variable — in this example, Variable: Review status — you are ready to use it as the basis for making decisions in the workflow. To do this, use theCompare any data source condition.

For example, you can add a step to your workflow that says if Variable: Review status equals Approved, run these actions. But if Variable: Review status equalsRejected, run different actions.

CREATE THE FIRST CONDITIONAL BRANCH

The first conditional branch compares the value that is stored in Variable: Review status. If the value equals Approved, the workflow will perform any actions associated with this condition.

In the Workflow Designer, under Workflow Steps, click Add workflow step.
Click Conditions, and then click Compare any data source.
In the condition, click the first value hyperlink, and then click Display data binding.
In the Define Workflow Lookup dialog box, choose the following options:
- Source: Workflow Data
- Field: Variable: Review status.

Click OK.
In the condition, leave equals as the value for the second parameter.
In the condition, click the second value hyperlink, type Approved, and then press ENTER.

CREATE THE SECOND CONDITIONAL BRANCH

The second conditional branch handles the case where the value stored inVariable: Review status equals Rejected.

Click Add 'Else If' Conditional Branch.
Click Conditions, and then click Compare any data source.
In the condition, click the first value hyperlink, and then click Display data binding.
In the Define Workflow Lookup dialog box, choose the following options:
- Source: Workflow Data
- Field: Variable: Review status.

Click OK.
In the condition, leave equals as the value for the second parameter.
In the condition, click the second value hyperlink, type Rejected, and then press ENTER.

Before you add any actions to the condition in each branch, this step of the workflow should look like this.

To complete this step in the workflow, click Actions, and then add whatever actions you want to each conditional branch.

TOP OF PAGE

Quick reference: A summary of the steps

For quick reference, here is a summary of the steps presented in the three preceding sections:

Add the Collect Data from a User action:
- For the first link, use the Custom Task Wizard to create the custom task form.
- For the second link, select a single user a group to assign the task to.
- For the third link, create a variable of the List Item ID type to store the ID of the task item that the user edits.
Add the Set Workflow Variable action:
- For the first link, create a variable to store the actual value (not just the ID) of a specific field from a specific row in the Tasks list.
- For the second link, look up the field whose value you want in the Tasks list, by using the value stored in the List Item ID variable to retrieve the specific list item (or row).

This lookup should resemble the following example. This lookup says, "Go to the Review status field in the Tasks list. Then go to the row in the Tasks list whose ID matches the ID stored in the variable for this instance of the workflow." If the workflow runs and creates a task whose ID is 3, this lookup retrieves the value of the Review status column from the third row in the Tasks list. The next time the workflow runs, this ID may be 4, so the lookup goes to the fourth row, and so on.

Create a new workflow step.
Add the Compare any data source condition:
- For the first link, choose the variable that you set to an actual value in step 2.
- For the second link, click a comparison.
- For the third link, enter a value that you want to compare with the value stored in the variable.
Add any actions that you want to run if this condition is satisfied.
Click Add 'Else If' Conditional Branch and repeat steps 4–5 to create additional branches.

SharePoint Calculated Value Nested

2011-05-22T20:56:00.001-07:00

http://office.microsoft.com/en-us/windows-sharepoint-services-help/if-function-HA001161010.aspx

keep track this formula for nested function , so i can use this to select other option to show here as lookup list

Example set 3

45
=IF([Score]>89,"A",IF([Score]>79,"B", IF([Score]>69,"C",IF([Score]>59,"D","F"))))
Assigns a letter grade to the first score (F)

90
=IF([Score]>89,"A",IF([Score]>79,"B", IF([Score]>69,"C",IF([Score]>59,"D","F"))))
Assigns a letter grade to the second score (A)

78
=IF([Score]>89,"A",IF([Score]>79,"B", IF([Score]>69,"C",IF([Score]>59,"D","F"))))

Assigns a letter grade to the third score (C)

In the preceding example, the second IF statement is also the value_if_false argument to the first IF statement. Similarly, the third IF statement is the value_if_false argument to the second IF statement. For example, if the first logical_test ([Score]>89) is TRUE, "A" is returned. If the first logical_test is FALSE, the second IF statement is evaluated, and so on.

The letter grades are assigned to numbers using the following key (assuming use of integers only).

IF SCORE IS
THEN RETURN

About site Template and site definition

2011-05-03T08:29:00.001-07:00

Just notice the enterprise tab is not available when i try to create on our production , look like is someone hiding it. So try find some information on internet to see how to disable the settings .

some information to keep track about template topic.

What are site templates? > Here

Register site definitions > Here (below article )

Last night, Carl and I did end up recording the sequel to the first SharePoint 2007 DNRTV show we did earlier. In this episode, I had a chance to talk more about content types, and then I ran through a full-fledged example demonstrating an InfoPath Forms Services based solution solving a real life problem. And then after that I demonstrated creating KPI (key performance indicator) reports based on data collected via infopath forms running in a web browser.

All in all, the show I think, turned out quite well. I will blog about it when it is online.

But, that is not what this blog post is about. When Carl and I were recording, based on a conversation, I had alluded to the fact that you can create your own site definitions and register them within SharePoint 2007. How you ask? It’s a question of twiddling with a bunch of XML files. To which, of course the developer world comes to a screeching halt.

Yes, SharePoint does suffer from XMLITIS, but I have blogged about that as one of the criticisms, and let us get over that.

The real Q is, how can you, register your own site definitions. Well here is how.

First you need a custom site definition. As you may be aware, a custom site definition is nothing but a logical grouping of features, lists, web parts, and a whole bunch of other things, that together make a site. For instance, I could create a custom site definition for a “Blog reader” application. (Speaking of which, in a week or two, the next issue of code-magazine will contain an article from me, demonstrating exactly how to create a blog-reader application a.k.a. bloglines/newsgator etc in SharePoint). All site definitions reside as a bunch of files at the following location.

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\SiteTemplates

(Note: I am almost done reviewing Scot Hilier’s upcoming Apress book on SharePoint 2007. He explains this very well in Chapter 11, and I strongly recommend you picking a copy of it – the book is simply excellent, and yes I will post a full review later).

Now in that directory, there are a bunch of site definitions already created. You can create one of your own, but since this blogpost doesn’t talk about that – go ahead and copy paste, “BLANKINTERNET” to a directory called “Sahil”

Now ideally, the directory “Sahil” which contains the details of your site definition, should contain something meaningful in it – so a blogreader site definition will contain the necessary lists, features etc. But ignoring that, let us next look at, how you can register this new Site definition, in SharePoint.

Now at this path –

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\

You would note a curiously named directory called “1033”. 1033 is the culture number for en-us (US English). Under 1033\Xml, there are a bunch of XML files. Strangely enough, many of them are named as “WebTemp*.xml”. That is where you need to put this new site definition’s information, so SharePoint will understand it. Go ahead and copy paste webtempsps.xml and call the new file webtempsahil.xml. The name is important, since SharePoint will look for all files that match “WebTemp*.xml”.

Now go ahead and edit the webtempsahil.xml file to look like as below.

<?xml version="1.0" encoding="utf-8"?>


<Templates xmlns:ows="Microsoft SharePoint">
<Template Name="Sahil" ID="10001">
<Configuration ID="0" Title="Sahil's site" Hidden="FALSE"
ImageUrl="/_layouts/1033/images/IPPT.gif" Description="This is the custom site I was talking about." SubWebOnly="FALSE" DisplayCategory="Winsmarts"> </Configuration>
</Template>
</Templates>

A few things that will jump out at you from the above XML file.

- ID must be greater than 10000, so your IDs don’t screw up SharePoint’s.
- You have a whole bunch of other control from the various possible elements, I think the above are self-explanatory.

Now go ahead, and do an iisreset, and try creating a site collection under SCAW (SharePoint Central Web Administration), or a site under a site collection through various means. You should see something like the following in the page that prompts you to create new sites:

Note that the text, the image, and everything else has been picked from WebTempSahil.xml.

Now how cool is that J!!? Now you can merrily create your custom site definitions, register them, and create them on a per-demand basis.

In further blog posts, I will cover various other aspects of Site Definitions. Until then, Rock On!!

SharePoint InfoPath 2007 Integration

2011-04-27T00:04:00.001-07:00

Sharing and keep track on this :)

SharePoint InfoPath 2007 Integration

View more documents from Biz Support Online.

About Alert email issues

2011-04-25T20:20:00.001-07:00

Issues : new item assign to task list , owner not receive alert

Step to check:

stsadm -o getproperty -pn job-immediate-alerts -url http://abc.com/sites/XXXX

this command is check the alert timer job status :

Restults:
<Property Exist="Yes" Value="every 5 minutes between 0 and 59" />
which mean the alert timer will check every 5 minutes.
*normally this is standard setting

Next Step:

Run following command to check from SQL server whether new item created or not :
· use [content_DB
]
select top 50 itemname,EventData,ACL,* from EventCache order by EventTime desc

you should see the new created item , else which mean something wrong.

Solution :

create new list and try again.

ha ha..is not perfect solution but anyhow let me resolve mine problem.

just notice have good post about the alert :
http://msmvps.com/blogs/bradley/archive/2009/03/22/how-to-troubleshoot-alerts-in-wss-3-0-moss.aspx

Only with Document library permission is unable to subscribe Alert me!

2011-04-21T03:44:00.001-07:00

Issues :

user only have full control permission at document library, when user try to click on alert me setting then will show Error: Access Denied

Root cause:

this is by design on Microsoft product or maybe is bug :D

When you click on the Alert me you will route to the page sites/abc/_layouts/XXXXX , which is needed read permission at site level.

Solution:

1. Grant user view permission at site level. > if allow user to see other information

2. If user using client Microsoft outlook 2007 then can direct sync the folder to outlook ( if have any new document upload then you will see unread document at outlook)

3. Admin can help user add the alert.

Using Marco to save file to sharepoint document library :)

2011-04-19T06:05:00.001-07:00

Just learnt something new from user, which is we can run macro then the excel file can save to SharePoint document library .

here is the code :

Sub TestSave()
     FolderPath = “http://sharepoint.abc.com/sites/abc/docmentLibrary/”
         SavePath = FolderPath & "sinpeow.xls"
     ActiveWorkbook.SaveAs Filename:=SavePath, FileFormat:=xlNormal
End Sub

How Many current connection to your IIS ?

2011-04-05T06:40:00.001-07:00

Recently server is out of memory , so thinking to check and see how many connection is connected to my sharepoint web application.

At last have found one counter is under Web services > current Connection.

This counter is show how many current connection is connected to your web application.

Run Perfmon then add the counter , you will see it.

SharePoint List filter with [Null] ?

2011-03-23T20:09:00.001-07:00

thinking to find any parameter is available to Filter by empty Field at SharePoint list. But i found one article , is not with Null….is with nothing to compare mean is null!! ha ha..let me share it at below :

http://www.endusersharepoint.com/2009/01/23/filter-by-an-empty-field/

I ran into a little quirk this morning that turned out to have an interesting solution. When authors submit articles to the Article Submission Library at EndUserSharePoint.com, there is a date column named “Actual Publication Date” to compare against the “Scheduled Publication Date”.

I want to create a view that shows only the articles that have not been published.

My first pass used the filter section to say “Show items when Actual Publication Date is greater than 1/1/2008″. I figured since it was a date column, any item that had a date in that field would not show up in the view. Nope… didn’t work.

Then I thought “What if you filter for an empty field?” So this time, I set filter to “Show items when Actual Publication date is equal to” and left the value field empty…. Score!!!

Weird one… don’t compare against the date, just leave the filter value empty. You learn something new everyday.

wohoo!! 32bit and 64bit in the SharePoint farm :D

2011-03-22T23:35:00.001-07:00

Recently our sharepoint Farm facing out of memory issues when downloading large file. After investigation , analyst on the memory dump we have notice is because of the workload… so our option have 2 , one is upgrade to 64bit sharepoitn farm or add on more web front end server.

suddenly read the article here about performance : http://technet.microsoft.com/en-us/library/cc298550%28office.12%29.aspx

just get to know 32bit and 64bit SharePoint server can mix up :)

Mixing 32-bit and 64-bit servers can affect load balancing. You can run an environment that has some Web servers running the 32-bit version of Office SharePoint Server 2007 and others running the 64-bit version. However, there is a risk that the 32-bit Web servers might become overloaded if the network load balancer is configured to use a less-intelligent model such as round robin. We recommend that you configure the load balancer to manage distribution based on load.

Additionally, deploying both 32-bit and 64-bit servers increases the maintenance overhead for the farm. This is because third-party applications, custom solutions, patches, and software updates for both architectures must be tracked and managed independently

the benefit i can think of is we can have less down time to conver our fram from 32 bit to 64 bit by mixing it. :D

sub sites owner with Full Control unable to add Content Editor Web Part

2011-02-24T19:34:00.001-08:00

after so many year at sharepoint , just notice web part also have permission setting.

below is the detail from the forum.

http://www.tek-tips.com/viewthread.cfm?qid=1444650&page=3

Background: SharePoint V3 on a hosted server. The user is a "site owner" and "site owners" have "full control" over the site. "full control" has all the options that can be selected for security. This is a sub-site to the main SharePoint site and it does not inhearit security from the parent site. I want site owners to have full control over there individual sites, but not have control over other's sites.
Problem: When the user goes to add a web part to the "Home" page of the site via selecting "Site Actions" - "Edit Page" the only web parts that are available to them are the "Lists and Libraries" web parts that consist of "Announcements", "Calendar", "Links", "Shared Documents", "Tasks", and "Team Discussion".
When a Site Collection Administrator does the same thing as above, they see all the web parts listed above as well as "Miscellaneous" web parts consisting of "Content Editor Web Part", "Form Web Part", "Image Web Part", "Page Viewer Web Part", "Relevant Documents", "Site Users", "User Tasks", and "XML Web Part". Is it possible to make these web parts accessible to the owners of sub-sites with out giving them full control over the entire SharePoint site hierarchy?

I believe I figured out a solution. So, if your curious, here is how I fixed it.
Logged into the top level SharePoint site as a site collection administrator.
Select "Site Actions" - "Site Settings"
In the "Galleries" Colum, select "Web Parts"
With the Web Part Gallery open, select the "Settings" menu and select "Gallery Settings"
Now you should be in the Customize Web Part Gallery window. In the "Permissions and Management" column, select "Permissions for this gallery".
In the "Permissions: Web Part Gallery" Select "Actions" - "Edit Permissions"
Select "OK" to the pop up that is displayed warning you that you are about to create unique permissions, and now you can select "New" and add additional users to the Gallery.
This will allow whomever you add to see all the Web Parts available.

Command line method to create large files

2011-02-21T01:38:00.001-08:00

wohoo… finally get to this lost time command forget in my mine.~~

sometime need to have huge file to upload to SharePoint for testing or network testing or do what ever test need to have huge file.

simple command below for you to generate the large dump files!!

You can easily create dummy file of specific size which do not contain any datausing Fsutil command.

fsutil file createnew <name of file> <size in bytes>

Following is example to create dummy file of 10MB size in ‘temp’ folder of E drive.

fsutil file createnew e:temptempfile.txt 10000000

Introduction to workflows

2011-02-16T07:04:00.001-08:00

Microsoft Office SharePoint Designer 2007 another article from Microsoft

Across your enterprise, teams use Microsoft SharePoint sites to collaborate on documents and share information. You want to build a SharePoint application that improves team productivity and efficiency, but you don’t want to write code. Where do you start?

With Microsoft Office SharePoint Designer 2007, you can design workflows that add no-code application logic to your SharePoint sites and applications. Using the Workflow Designer, you create rules that associate conditions and actions with items in SharePoint lists and libraries. Changes to items in lists or libraries trigger actions in the workflow.

For example, suppose that a team's primary responsibilities are writing, revising, and approving contracts. These contracts are stored in document libraries on the team site. With Office SharePoint Designer 2007, you can create a workflow that sends a notification e-mail message to the reviewer when a new contract has been uploaded to the site. At the same time, the workflow creates a task in the Tasks list for the reviewer. When that person reviews the contract and marks the task as complete, different actions are triggered depending on whether the contract is assigned a status of Approved or Rejected.

Team efficiency and productivity improve because the workflow drives the process so that the team can focus on doing the work, rather than on managing the workflow. And no programming is required to build such a solution. By creating rules in the Workflow Designer, you can quickly add interactivity to a SharePoint solution or application.

This article introduces the basics of workflows. When you understand the basic building blocks of a workflow — events, actions, conditions, and steps — you can quickly add application logic to your SharePoint applications.

IMPORTANT To create a workflow, your SharePoint site must be located on a server running Windows SharePoint Services 3.0.

In this article

What is a workflow?

Your team uses a SharePoint site to collaborate and store valuable business information in SharePoint lists and libraries. With Office SharePoint Designer 2007 , you can now attach application logic to documents or items in these lists and libraries.

With the Workflow Designer, you can attach a sequence of conditions and actions to a list or library — this sequence is a workflow. A workflow is a natural way to organize and run a series of actions that correspond to a work process. This process can control almost any aspect of a list item in Windows SharePoint Services 3.0, including the life cycle of that item. The workflow can include both actions performed by people (or workflow participants) and actions performed by the workflow. Workflow participants can interact with the workflow through the Tasks list, where a workflow can create a task for someone and remain paused until the task is marked complete.

Workflows can be as simple or as complex as your business processes require. You can create a workflow that the user initiates, or a workflow that is initiated automatically based on an event, such as when a list item is created or changed.

In general, when you use Office SharePoint Designer 2007 to design a workflow, you follow these basic steps:

Use the Workflow Designer to choose and assemble the conditions and actions that define the steps of the workflow.
Have Office SharePoint Designer 2007 automatically generate any ASP.NET forms for workflow initiation or any custom SharePoint task, if necessary.
Customize the workflow forms, if necessary.

You can think of a workflow as a flowchart of actions with a beginning, an end, and a sequential flow from start to finish. Workflows can incorporate parallel branches, but ultimately they progress from the initial action to the final action.

For example, suppose you were to chart the workflow described earlier that routes a document in Windows SharePoint Services 3.0 for approval. When the workflow starts, it automatically notifies the specified reviewer by e-mail that they have a document to review. The reviewer then reviews the document, and changes the status of the document to indicate that they have completed their task, and whether they have approved or rejected the document. Based on the reviewer response, the workflow proceeds down one of two parallel branches. If the reviewer approves the document, the workflow moves the approved document to a specific document library, and then sends an e-mail message to the entire team notifying them of the approved document. If the reviewer rejects the document, the workflow notifies the document author of this. In either case, the workflow then reaches its end and the process is completed.

TOP OF PAGE

What are events, actions, conditions and steps?

These are the building blocks of a workflow. A workflow consists of one or more steps, and each step consists of actions and any associated conditions. Each workflow is initiated by an event.

WHAT ARE EVENTS?

An event is what starts or initiates a workflow. There are exactly three events that can start a workflow:

An item is created.
An item is changed.
A workflow participant clicks a start button on the SharePoint site.

It is important to understand that a workflow created with Office SharePoint Designer 2007 is always attached to exactly one list or library in a SharePoint site. When you design a workflow, you choose which list to attach it to. An event in this list starts the workflow.

You can create a workflow that a participant starts manually, or a workflow that is started automatically when a list item is created or changed. For example, in the document approval workflow, you want to design the workflow so that it starts automatically whenever someone adds a document to the Shared Documents library. On the File menu, point to New, and then click Workflow. In the Workflow Designer, you see the following page.

When a workflow participant starts a workflow manually, that person first browses to the list or library that the workflow is attached to. Any person with at least the Contribute permission level can initiate a workflow that is designed to start manually. The participant clicks an item, clicks Workflows on the menu, and then chooses a workflow from a page that displays all workflows associated with that item. The participant fills out a workflow initiation form, if necessary, and then initiates the workflow by clicking the start button on the form. Initiating a workflow creates a new instance of that workflow for that specific item.

NOTE The Workflows command is available only when the item is in a list or library that has at least one workflow attached to it.

For a workflow that is started manually, the initiation form can be as simple as the following.

You can also add custom fields to an initiation form when you design the workflow. Workflow participants can then provide information to the workflow by filling out this form, and those settings are passed to the workflow. A new workflow instance starts, and that workflow can then look up and use the information provided through the form at any point in the workflow.

WHAT ARE ACTIONS?

An action is the most basic unit of work in a workflow. Office SharePoint Designer 2007 provides a set of ready-made, reusable actions for you to incorporate into your workflow. For example, your workflow can:

Create, copy, change, or delete list items (including documents).
Check items in or out.
Send an e-mail message.
Create a task for someone on the Tasks list of your team site.
Collect data from a participant that can be referenced later in the workflow.
Pause or stop the workflow.
Log workflow information to a History list to use for repudiation or workflow debugging.
Set workflow variables or perform calculations.

A workflow can contain any number of actions. The actions just listed are performed by the workflow, but other actions might be performed by workflow participants. For example, the document approval workflow is comprised of five actions. Four of these actions are performed automatically by the workflow, but one of these actions — actually reviewing the document — is done by a workflow participant. Actions done by a workflow participant are represented by tasks assigned to that person in the Tasks list. The five actions in the example workflow are:

Send an e-mail message to notify the reviewer
Review the document (a task assigned to a workflow participant)
Move the document to the Approved document library
Send an e-mail message to notify the team
Send an e-mail message to notify the document author

In the most basic sense, when you design a workflow, you identify the necessary sequence of actions, and then you assemble that sequence of actions by using the Workflow Designer. For example, in the document approval workflow, the first action that you want is to send an e-mail message to notify the reviewer.

So in the Workflow Designer, you choose that action for the first step in the workflow.

WHAT ARE CONDITIONS?

When you design a workflow, you can use the Workflow Designer to create rules that apply conditional logic to SharePoint lists and items. A rule establishes a condition where the workflow performs the associated action only if that condition is true. For example, you can create a rule where the workflow sends a reviewer an e-mail message only if an item is created by a specific person. You can also add clauses to a condition. For example, you can create a rule where a reviewer is sent an e-mail message only if an item is both (1) created by a specific person and (2) the document title contains specific keywords. Finally, you can associate multiple actions with one condition. For example, you can create a rule where if an item is created by a specific person, then (1) the reviewer is sent an e-mail and (2) workflow information is logged to the History list.

To sum up, a rule is a condition associated with one or more actions: If all clauses in the condition are true, do all the associated actions.

In the previous example, the user specified only one condition. However, you can create multiple conditions for a step in the workflow. Multiple conditions create branches in the workflow: If condition A is true, do one action; if condition B is true, do a different action. To add a branch to a step, click Add 'Else If' Conditional Branch. For example, in the document approval workflow, if the reviewer approves a document, the workflow performs one action (or series of actions); if the reviewer rejects a document, the same workflow performs a different action. This is a conditional branch.

In the Workflow Designer, this step has two branches and looks like the following. The green diamond indicates that the step has a conditional branch.

You can also create a branch that has no specific condition. This way, the workflow performs one action if a condition is true and a different action if the condition is false. For example, the following step in a workflow sends a message to the team only if the condition is true; else, the workflow sends a message just to the document author. By adding a branch with no specific conditions, the workflow performs the action in that branch in any case where the condition in the first branch is false.

NOTE Branching in a workflow cannot extend from one step to another. A set of 'Else If' branches is always contained in a single step.

Office SharePoint Designer 2007 provides several ready-made, reusable conditions for you to incorporate into your workflow. For example, you can specify that the workflow performs the associated actions only if an item:

Is created or modified in a specific time span.
Is created or modified by a specific person.
Has a title field that contains specified keywords.
Is a file of a specific type or has a file size in a specific range. (This condition is available only when the workflow is attached to a document library.)

In addition, you can create custom conditions and advanced conditions where you can specify a wide range of parameters. With custom conditions, you can compare a field in the current list with a value. For example, you can create a custom condition where if the Approval Status field equals Approved, do the associated action. With advanced conditions, you can compare one value to another value. This allows you to create a comparison between a field in any list and a value from another list. For example, you can create an advanced condition for the Shared Documents library where if the value of the Status field in the Tasks list equals Pending, do the associated action.

NOTE An action does not require a condition. For example, the first step of the example document approval workflow sends an e-mail to notify the reviewer. This action does not have a condition associated with it.

PARALLEL VS. SERIAL ACTIONS

When you have more than one action associated with a condition, the actions can be set up to run at the same time (parallel) or one after another (serial).

Serial actions For example, in the document approval workflow, you can set up two actions so that when a document is approved, a message is sent and then (afterward) the document is copied to the Approved document library. In the Workflow Designer, then indicates that the second action occurs after the first.

Parallel actions For example, in the document approval workflow, you can set up two actions so that when a document is approved, a message is sent and (at the same time) the document is copied to the Approved document library. In the Workflow Designer, and indicates that the second action occurs at the same time as the first.

NOTE Parallel actions are not absolutely simultaneous; the exact order cannot be specified and may vary each time the workflow runs.

NOTES

In any given rule (conditions and actions), all actions must be either serial or parallel.
A set of serial or parallel actions must be contained within a single step.

WHAT ARE STEPS?

A workflow is comprised of one or more steps. Each step can contain any number of actions and associated conditions. You can think of steps simply as pages in the Workflow Designer. For example, the document approval workflow has two steps, as shown in the Workflow Designer.

Steps allow you to group conditions and actions so that one set of rules (conditions and actions) can be evaluated and performed before a second set.

One step or many? Some workflows can be designed either as a sequence of actions within one step, or as a sequence of steps.

For example, the following three actions could be Step 1 of a basic one-step workflow.

The same three actions could be separated into several steps.

How you structure your workflow into steps depends on what you want each step to accomplish. The rules in one step are processed to conclusion before going on to the next step, so you want to group in the same step any rules necessary to effect the specific action or actions that you want.

More specifically, each step can hold one set of 'Else If' conditional branches, where the actions in each branch are performed only when the associated condition is satisfied. In this case, additional steps are needed only when:

Multiple sets of 'Else If' conditional branches need to be evaluated.
You need to separate a branched statement from a non-branched statement.

You can also use steps simply as a way to organize your workflow. For example, a workflow might have many actions in a step that doesn't use conditions. In this case, you might want to separate the actions into steps just to better organize them.

TOP OF PAGE

What are workflow forms?

To make your workflow more dynamic and flexible, you can add a form to the workflow. With a form, you can collect information from workflow participants at predefined times in the workflow, and make it possible for participants to interact with the tasks for that workflow.

With Office SharePoint Designer 2007, you can create two types of workflow forms:

An initiation form gathers information from the workflow participant when they start the workflow. Initiation forms are displayed to users when they manually start a workflow on a given SharePoint item. With an initiation form, users can specify additional parameters or information about the workflow as it applies to the given SharePoint item. For example, you might use an initiation form to ask who should review a document and by when the review should be completed. Not all workflows need initiation forms. If you do need one, Office SharePoint Designer 2007 automatically generates an ASP.NET initiation form according to your initiation specifications.
A custom task form allows workflow participants to interact with tasks in the Tasks list on a SharePoint site. With the Custom Task Wizard, you can easily create custom form fields and add them to a custom task form. When you finish designing the workflow, Office SharePoint Designer 2007 automatically generates the ASP.NET forms for your custom tasks. Then, when the workflow runs and tasks are created, the user browses to the Tasks list on the SharePoint site, marks the task as completed, and enters any optional or required information specific to the workflow. The workflow can then respond to those changes as specified in the workflow, or look up and evaluate that information in later steps of the workflow.

After Office SharePoint Designer 2007 automatically generates the ASP.NET forms, you can customize them. Workflow forms are ASP.NET pages with a Data Form Web Part and a master page applied to it. These .aspx files are stored on the SharePoint site with the workflow source files. You can open and customize these forms as you would any other .aspx file.

TOP OF PAGE

Where are workflows stored?

Workflows are stored in a site-level document library called Workflows. This document library is created automatically by Office SharePoint Designer 2007. In the Folder List, the Workflows document library displays the workflow icon instead of the usual list or document library icon. By default, the Workflows document library is hidden from the browser and has no List Views, such as AllItems.aspx or EditForm.aspx. This document library contains a folder for each workflow created with Office SharePoint Designer 2007. The folder contains all the source files necessary for the workflow, including:

The workflow markup (.xoml) file (needed only when the workflow uses conditions).
The workflow rules file.
The workflow configuration file.
Any .aspx forms needed, such as initiation forms (for workflows that are started manually) or custom task forms.

To modify an existing workflow, you can either click Open Workflow on the Filemenu or double-click the .xoml file in the Folder List. This opens the workflow to its first step in the Workflow Designer. If you click Back to view the initiation settings of the workflow, you see that you cannot change which list or library the workflow is attached to. After a workflow is attached to a list or library by using Office SharePoint Designer 2007, this association cannot be changed.

The Workflow Designer provides an action called Log to History List. You might use this action when you want to keep a record of the workflow history for investigating errors or for tracking and repudiation purposes. When you create a workflow that uses the action Log to History List, Office SharePoint Designer 2007 automatically creates a list called Workflow History. This list has columns for such information as user ID, date, event, and error description. Like the Workflows document library, by default the History list is hidden from the browser but can be seen in the Folder List.

The Workflow Designer provides three actions that interact with the Tasks list: Assign a To-Do Item, Collect Data from a User, and Assign a Group Survey. When you create a workflow that uses any of these three actions, Office SharePoint Designer 2007 automatically creates the .aspx form, the content type for the task, and the Tasks list, if necessary. By default, the Tasks list can be viewed in the browser, unlike the Workflows document library and Workflow History list.

TOP OF PAGE

Where can I check the status of a workflow?

You can easily view the progress of workflows on a selected item through the browser. The All Items view of a list or document library displays the current status of workflows running on an item. In addition, each item has a Workflows page where you can view the following information:

All workflows currently running on that item.
All workflows that have run on the item in the past.
All the available workflows for that item.

To view the Workflows page for an item, click the item in the list, and then clickWorkflows on the menu.

NOTE The Workflows command is available only when the item is in a list or library that has at least one workflow attached to it.

When a user starts a workflow on an item, Windows SharePoint Services 3.0 adds a new column to that item. By default, the column name matches the name of the workflow. This read-only column displays the current status of the item within that workflow. This status column is added automatically for each workflow the first time it is run.

In each column, the workflow status is a link. When you click In Progress, for example, you see the Workflow Status page for that instance of the workflow.

A workflow created in Office SharePoint Designer 2007 cannot be deployed to multiple lists. It is only valid for the list for which it was created. However, multiple workflows can be attached to one list and may be available for a given item. Multiple workflows can run simultaneously on the same list item, but only one instance of a specific workflow can run on a specific item at any given time. For example, you might have two workflows, Workflow A and Workflow B, available for a specific list. Although both workflows can run simultaneously on a specific item in the list, you cannot have two instances of Workflow A or Workflow B running on the same item at the same time.

Introduction to customizing pages by using Web Parts

2011-02-16T07:03:00.001-08:00

WSS list is so useful for business user, can do something simple system by the simple list and filter :D. i am start thinking should i be business personnel rather then SharePoint engineer? ha ha ha , ok, just keep tract this article from Microsoft , i am sure one day i will consult user to user this :D

This article is intended for Web page owners and administrators. It provides an overview of Web Parts and Web Part Pages and explains how you can customize a page by adding, changing, or deleting Web Parts.

Overview of Web Parts and Web Part Pages

A Web Part is a modular unit of information that forms the basic building block of a Web Part Page. You can add Web Parts to Web Part zones in a Web Part Page and then customize the individual Web Parts to create a unique page for your site users.

The following example uses the Image Web Part to describe the basic features of a Web Part.

The Web Part title bar contains the heading for the Web Part.

The Web Part menu contains functions that enable you to minimize or close the Web Part, edit the Web Part, or get Help for a specific Web Part. When the page is in edit mode, you can also use this menu to delete the Web Part or connect it to other Web Parts, depending on the type of Web Part that you are using.

The body of the Web Part contains the content that you specified for the type of Web Part that is being used. In this example, the Web Part is an Image Web Part, which displays an image.

A Web Part Page is a special type of Web page in which you can use Web Parts to consolidate data, such as lists and charts, and Web content, such as text and images, into a dynamic information portal that is built around a common task or special interest.

Your site home page is one example of a Web Part Page. When you create a new site or workspace site, you are creating a Web Part Page. You can also create a Web Part Page by selecting one of the available site templates, or you can use a Web design program that is compatible with Microsoft Windows SharePoint Services, such as Microsoft Office SharePoint Designer 2007, to create a Web Part Page from scratch.

You can use a Web Part Page to present a variety of structured and unstructured information in an organized, useful, and convenient way. Web Part Pages often contain several Web Parts that are connected so that you can dynamically display data and content to see the results that you want.

For example, you can create a Web Part Page called Customer Orders that you frequently use to display critical information. You get a call from a customer who has a question about an order, does not remember the order ID number, but does remember the date when the order was placed. You can use a Web Part Page to do the following.

Look up an order by order ID number or, in this case, the order date.

Display all orders by date.

Select the correct order, based on the customer's name, and look up the order details as well as the customer details.

Select a line item in the order (in this case, the lamp), and display a product picture to confirm the customer's question.

Scan for late-breaking business news that is pertinent to the customer's order.

WEB PART PROPERTIES

Each Web Part shares a set of common properties (also called base class properties) that are organized into sections in the tool pane and that control the Web Part's appearance (such as the title, height, and width), layout (such as the Web Part order in the zone and the direction of the content), and advanced characteristics (such as the image icon and description).

Many Web Parts also have custom properties that are unique to the Web Part. These are usually displayed either above or below the common Web Part properties in the tool pane. For example, the Image Web Part has additional custom properties, including the image link, its horizontal and vertical alignment, and background color.

NOTE Depending on how the Web Part was created, a Web Part custom property may be displayed in a default Miscellaneous section below the common properties in the tool pane.

WEB PART VIEWS

You can customize a Web Part in one of two views:

Shared view You can add a Web Part to a Web Part Page and then edit the Web Part Page in a shared view. Shared Web Parts are available to all users of a Web Part Page who have the appropriate permission.
Personal view You can add a shared Web Part to your own personal view and then edit your view of the Web Part. The changes that you make to a Web Part while you are in a personal view are available only to you. Other users who did not make changes in a personal view continue to see the shared view of the Web Part.

The view of the Web Part that you are working with can be important because:

You may have permission to edit only some Web Parts on certain Web Part Pages but not on other Web Part Pages.
You may be able to connect to certain Web Parts on a Web Part Page but not to other Web Parts on the same Web Part Page.

WEB PARTS AND WEB PART CONNECTIONS

An additional feature of Web Parts is the ability to easily connect them by passing data between them and synchronizing their behavior. By connecting Web Parts, you can manage data in dynamic and interesting ways. In many products and technologies, the task of connecting sets of data from different data sources is not easy and often requires programming skill. But with Web Parts, making data connections is as simple as using menu commands. By connecting Web Parts, you can, for example, present data from two Web Parts in alternate views, perform related calculations between two Web Parts, and filter a Web Part by using values from another Web Part — all on one Web Part Page.

WEB PART ZONES AND THEIR PROPERTIES

Web Part zones are containers of Web Parts that are used to group and organize Web Parts on a Web Part Page. Web Part zones also have a set of properties that serve a dual purpose. You can use one subset of properties to organize the layout and format of Web Parts on the Web Part Page. You can use another subset of properties to provide an additional level of protection from modification (or "lock down") of the Web Parts within the zone.

The Web Part zone properties each have default settings or behaviors. As you add Web Parts to the Web Part Page, some of these property values are automatically set. These property values are not designed to be edited in the browser, but you can edit them by using a Web design program that is compatible with Windows SharePoint Services, such as Office SharePoint Designer 2007.

For more information about Web Part zone properties, see the Windows SharePoint Services 3.0 SDK, which is available from the Windows SharePoint Services Developer Center on MSDN.

TOP OF PAGE

Types of Web Parts

Windows SharePoint Services provides several Web Parts that are ready to use with your site. You can use these built-in Web Parts, customize them to suit your needs, or create new Web Parts and upload them for use throughout your site.

DEFAULT WEB PARTS

The following Web Parts are included by default in any site and can be customized to suit the needs of your team. Many of these Web Parts can also be connected to each other to create a variety of unique solutions:

Content Editor Web Part You can use the Content Editor Web Part to add formatted text, tables, hyperlinks, and images to a Web Part Page.
Form Web Part You can use the Form Web Part to connect to and filter a column of data in another Web Part. Both Web Parts must run on the same server.
Image Web Part You can use the Image Web Part to add a picture or graphic to a Web Part Page. To more easily coordinate the image with other Web Parts on the page, you can control the vertical alignment, horizontal alignment, and background color of the image inside the Image Web Part by editing its custom properties in a shared view.
List View Web Part You can use the List View Web Part to display and edit list or library data on your site and to connect to other Web Parts, including other List View Web Parts. Lists are information that you share with team members and often display in tabular format. List views display this information in different ways for different purposes, such as filtering, sorting, or selecting specific columns.

NOTE There is no Web Part called List View. When you create a list on your site, a List View Web Part is automatically created and named after the list. For example, if you create a list called Boats, a Web Part called Boats will be available in the Site Name gallery. The Web Part automatically displays the data contained in the list that you created.

Page Viewer Web Part You can use the Page Viewer Web Part to display a Web page, file, or folder on a Web Part Page. You enter a hyperlink, file path, or folder name to link to the content.
Site Users Web Part You can use the Site Users Web Part to display a list of users and groups who have permission to use a site. The Site Users Web Part automatically appears on the home page of a Document Workspace site. You can also add the Site Users Web Part to any Web Part Page.

NOTE In sites that are running on Microsoft Windows SharePoint Services 2.0 and earlier, the Site Users Web Part was called the Members Web Part.

XML Web Part You can use the XML Web Part to display Extensible Markup Language (XML) and apply Extensible Stylesheet Language Transformations (XSLT) to the XML before the content is displayed. For example, you might have an XML file that contains a list of boats, prices, and links to images of the boats. You can use the XSLT to transform the data to display a list of boats and prices and make the boat name a hyperlink to display the image in a separate window.

PRECONFIGURED LIST VIEW WEB PARTS

The following Web Parts are built into the Windows SharePoint Services team site template and are automatically configured and ready to use on a Web Part Page when you create a new team site. Different combinations of these Web Parts are included when you create a team site or workspace site, depending on which site template you select.

NOTE These Web Parts are derived from the List View Web Part and use preconfigured Web Part templates to create their unique layout and design. To add data to these lists, on the Quick Launch, click View All Site Content, and then clickLists. On the All Site Content page, click the name of the list for which you want to add data.

Announcements Use the Announcements Web Part to post news, status, and other short bits of information that you want to share with team members.
Calendar Use the Calendar Web Part to display upcoming events or team schedules.
Links Use the Links Web Part to post hyperlinks to Web pages that interest your team.
Shared Documents Use the Shared Documents Web Part to share files from the default document library with site users.
Tasks Use the Tasks Web Part to assign a task to a member of your team, specify its due date and priority, and indicate its status and progress.
Team Discussion Use the Team Discussion Web Part to provide a forum for talking about topics that interest your team.

CUSTOM WEB PARTS

By using a programming environment that is compatible with Windows SharePoint Services, such as Microsoft Visual Studio, developers can exploit the full feature set of Microsoft ASP.NET to create custom Web Parts. A Web Part Page is an ASP.NET file (.aspx), and Web Parts are derived from Web Form Controls. To further enhance Web Part Pages, developers can create their own Web Parts that provide new functionality. Developers can also add custom properties to the Web Parts, add custom builders in the tool pane for specialized user interfaces, and connect to other Web Parts by using Web Part connections. For more information about creating and deploying Web Parts, see the Windows SharePoint Services 3.0 SDK, which is available from the Windows SharePoint Services Developer Center on MSDN.

You can also use Web Parts that other people or companies have created. You must have appropriate permissions to add a third-party Web Part to your Web Part Page or site. Some Web Parts may need to be deployed directly to the server. If you are unable to add a third-party Web Part to your Web Part Page or site, contact your administrator for assistance.

TOP OF PAGE

Ways to use Web Parts and Web Part Pages

You can use Web Part Pages in the following ways:

Consolidate data from different data sources.
Report and summarize critical data.
Analyze and aggregate data (for example, sums, totals, or counts).
Summarize key information that you want to see at the beginning of each day.
Prioritize and highlight project or customer data to help you make effective decisions.
Display an up-to-date work schedule and meeting information to quickly plan your day.
Get quick access to business news, local weather, and your favorite Web sites to focus your Web browsing.

WAYS TO CREATE AND CUSTOMIZE A WEB PART PAGE

There are several ways to create and customize a Web Part Page:

The New Web Part Page form The most common way to create a Web Part Page is through the New Web Part Page form. On the Site Actionsmenu , click Create, and then click Web Part Page to open the New Web Part Page form. After using this form to create a page, you can begin designing the page right away in the browser. When you want to browse through the page, just close the tool pane.
A Web design program By using a Web design program that is compatible with Windows SharePoint Services, such as Microsoft Office SharePoint Designer 2007, you can make advanced customizations to a Web Part Page, including the following:
- Customize the theme of a Web Part Page that uses the site theme by default.
- Edit a Web Part Page template or create a new one.
- Customize the page layout.
- Edit zone properties.
- Add HTML code or Web controls.
- Change the way Web Parts are ordered inside a zone.
- Add Web Parts outside a zone, or add a Web Part to a Web page that is not a Web Part Page.
- Create connections between Web Parts on different Web Part Pages.
- Publish a Web Part Page to a Web site that is running Windows SharePoint Services.
- Customize the Form Web Part and use the Data View Web Part.

TOP OF PAGE

Web browser support for Web Part Pages

Web browser support for Web Part Pages can be categorized into two levels:

Level 1 support is the highest level of visual and functional support. Browsers that provide level 1 support include recent versions of Microsoft Internet Explorer for Microsoft Windows.
At level 2 support, a few visual and functional features are not available to some browsers, and some other features are compromised and behave differently from the way they behave in level 1 browsers. However, the majority of features are still available to users. Browsers that provide level 2 support include Firefox 1.5 and later for Windows and Netscape Navigator 8.0 and later for Windows. Level 2 browsers are not supported for Windows SharePoint Services 3.0 Central Administration.

NOTE Level 2 browsers do not support the creation of connections between Web Parts.

A way to determine the size of subsites?

2011-01-18T23:08:00.001-08:00

There's a tool on Codeplex that will give you this information: http://www.codeplex.com/SPUsedSpaceInfo .

Bob Klass also has a tip in his blog of another way to try to get that info:http://bobklass.blogspot.com/2009/01/easy-way-how-to-find-sharepoint-subsite.html .

Easy Way How to Find SharePoint Subsite Size

I was looking for a GOOD way to find out the size of subsites. It seems a lot of people are struggling with this. You could try SharePoint Designer. That's fun. When you ask it site properties, it will give you a different answer depending on what document libraries or lists you touched. Obviously that is not going to be reliable.

I'll cut to the chase (although I was trying to be as wordy as possible). This isn't a GOOD way, but it is a very simple way:

open the site in Windows Explorer
navigate to the root of the site or subsite in question
right click, properties

That may be a little resource intensive - it takes a while to open. I think it may have to open a lot more than it appears just to get you that number, but there it is in the properties window. Piece of cake.

Post Script: http://www.codeplex.com/SPUsedSpaceInfo is a console app to get a CSV listing of sites and their size. Beware that the setup is pretty heavy handed - a Dotnet 3.5 SP1 installation starts right up if you aren't there already.

If you only have a couple of sites you want to take a look at and don't want to install a tool, you might try it. I would caution you to take his approach with a grain of salt, I am a lot more confident in the accuracy of a solution that uses the SharePoint object model to retrieve this information than his "hack" through the Windows Explorer GUI. I just would expect the object model to be able to present a much more true picture of how much storage a site is using than the UI would.

Some queries with Share[point content DB

2011-01-11T23:28:00.001-08:00

Some queries with these tables:

-- Query to get all the top level site collections

SELECT SiteId AS Siteid, Id AS Webid, FullUrl AS FURL, Title, Author, TimeCreated FROM dbo.Webs WHERE (ParentWebId IS NULL)

-- Query to get all the child sites in a site collection

SELECT SiteId AS Siteid, Id AS Webid, FullUrl AS FURl, Title, Author, TimeCreated FROM dbo.Webs WHERE (NOT (ParentWebId IS NULL))

-- Query to get all the SharePoint groups in a site collection

SELECT dbo.Webs.SiteId, dbo.Webs.Id, dbo.Webs.FullUrl, dbo.Webs.Title, dbo.Groups.ID AS Expr1, dbo.Groups.Title AS Expr2, dbo.Groups.Description FROM dbo.Groups INNER JOIN dbo.Webs ON dbo.Groups.SiteId = dbo.Webs.SiteId

-- Query to get all the users in a site collection

SELECT dbo.Webs.SiteId, dbo.Webs.Id, dbo.Webs.FullUrl, dbo.Webs.Title, dbo.UserInfo.tp_ID, dbo.UserInfo.tp_DomainGroup, dbo.UserInfo.tp_SiteAdmin, dbo.UserInfo.tp_Title, dbo.UserInfo.tp_Email FROM dbo.UserInfo INNER JOIN dbo.Webs ON dbo.UserInfo.tp_SiteID = dbo.Webs.SiteId

-- Query to get all the members of the SharePoint Groups

SELECT dbo.Groups.ID, dbo.Groups.Title, dbo.UserInfo.tp_Title, dbo.UserInfo.tp_Login FROM dbo.GroupMembership INNER JOIN dbo.Groups ON dbo.GroupMembership.SiteId = dbo.Groups.SiteId INNER JOINdbo.UserInfo ON dbo.GroupMembership.MemberId = dbo.UserInfo.tp_ID

-- Query to get all the sites where a specific feature is activated

SELECT dbo.Webs.Id AS WebGuid, dbo.Webs.Title AS WebTitle, dbo.Webs.FullUrl AS WebUrl, dbo.Features.FeatureId, dbo.Features.TimeActivatedFROM dbo.Features INNER JOIN dbo.Webs ON dbo.Features.SiteId = dbo.Webs.SiteId AND dbo.Features.WebId = dbo.Webs.Id WHERE (dbo.Features.FeatureId = '00AFDA71-D2CE-42fg-9C63-A44004CE0104')

-- Query to get all the users assigned to roles

SELECT dbo.Webs.Id, dbo.Webs.Title, dbo.Webs.FullUrl, dbo.Roles.RoleId, dbo.Roles.Title AS RoleTitle, dbo.UserInfo.tp_Title, dbo.UserInfo.tp_Login FROM dbo.RoleAssignment INNER JOIN dbo.Roles ON dbo.RoleAssignment.SiteId = dbo.Roles.SiteId AND dbo.RoleAssignment.RoleId = dbo.Roles.RoleId INNER JOIN dbo.Webs ON dbo.Roles.SiteId = dbo.Webs.SiteId AND dbo.Roles.WebId = dbo.Webs.Id INNER JOIN dbo.UserInfo ON dbo.RoleAssignment.PrincipalId = dbo.UserInfo.tp_ID

-- Query to get all the SharePoint groups assigned to roles

SELECT dbo.Webs.Id, dbo.Webs.Title, dbo.Webs.FullUrl, dbo.Roles.RoleId, dbo.Roles.Title AS RoleTitle, dbo.Groups.Title AS GroupName FROM dbo.RoleAssignment INNER JOINdbo.Roles ON dbo.RoleAssignment.SiteId = dbo.Roles.SiteId AND dbo.RoleAssignment.RoleId = dbo.Roles.RoleId INNER JOIN dbo.Webs ON dbo.Roles.SiteId = dbo.Webs.SiteId AND dbo.Roles.WebId = dbo.Webs.Id INNER JOIN dbo.Groups ON dbo.RoleAssignment.SiteId = dbo.Groups.SiteId AND dbo.RoleAssignment.PrincipalId = dbo.Groups.ID

You can also find interesting to read Different Database created with SharePoint

Copy From http://manish-sharepoint.blogspot.com/2008/06/some-important-tables-with-sharepoint.html

How to deal with orphaned SharePoint sites

2011-01-10T20:42:00.001-08:00

Copy from http://www.cjvandyk.com/blog/Lists/Posts/Post.aspx?ID=299

“in my case do all the step below cannot resolved , once do the step detach and attach db problem resolved” > keep track the nice step from

Cornelius J. van Dyk

Whatever causes it, orphaned sites in SharePoint can be a very painful issue to deal with. One way in which an orphaned site can occur is when a STSADM command it terminated during execution because of a drop of your remote desktop connection.

If you are working with STSADM, be sure to configure your Remote Desktop settings in order to keep disconnected sessions alive. Failure to do so, WILL cause problems for you in the future.

The toughest orphaned site I've ever had to deal with occurred during such a case. The site was being restored from a STSADM backup. The server's Remote Desktop settings were not set to keep the session alive and when a blip in the wireless network cause the connection to be broken, Windows simply killed the session causing the site collection to become orphaned. This was evident when the restore command was re-attempted:

stsadm -o restore -url http://server/site -filename site.stsadm.bak -overwrite

Which returned this puzzling message:

Another site already exists at http://server/site. Delete this site before attempting to create a new site with the same URL, choose a new URL, or create a new inclusion at the path you originally specified.

This is a puzzling message because... didn't we specify the "-overwrite" switch? Why yes we did! So what is going on here?
OK, OK. So the site is there and the "-overwrite" switch isn't working. Let's just delete the site. The following command is issued:

stsadm -o deletesite -url http://server/site

Only thing is, the site collection delete statement failed with the following error:

The system cannot find the path specified. (Exception from HRESULT: 0x80070003)

No problem you say. Just use the -force switch with the deletesite command. Doing that, the following command is issued:

stsadm -o deletesite -force -siteid 2a9fbc10-4a60-427b-8e6e-e1565d7e5796 -databaseserver sql -databasename Site_Content

Unfortunately, the response is not what you expected. This is the error returned:

Database "Site_Content" is not associated with this Web application

Of course, the message would make sense if the database was not associated with the web application, but it was. It is time for the good old orphan identification and handling swich... databaserepair
We begin by identifying the orphaned content. We issue the following command:

stsadm -o databaserepair -url http://server/site -databasename Site_Content

As expected, the command dumps a bunch of orphaned content. Time to delete the corrupted content so we can restore the site again. Simply add the -deletecorruption switch thus:

stsadm -o databaserepair -url http://server/site -databasename Site_Content -deletecorruption

Once the corrupted content has been deleted, rerunning the command without the -deletecorruption switch yields a clean bill of health for our database thus:

<OrphanedObjects Count="0" />

Unfortunately, retrying the restore still fails by with the same "site exists" error. This is where I had the idea to detach and re-attach the database to try and clear up the issue. Two quick STSADM commands later thus:

stsadm -o deletecontentdb -url http://server/site -databasename Site_Content

and

stsadm -o addcontentdb -url http://server/site -databasename Site_Content

yielded:

Operation completed successfully.

Now retrying the restore thus:

stsadm -o restore -url http://server/site -filename site.stsadm.bak -overwrite

finally yielded the result we were looking for:

Operation completed successfully.

Hopefully this will help you get sticky orphaned sites handled quickly so you can move on to more important things!

Later
C

Installing Microsoft SQL Server 2008 Reporting Services Add-On On a MOSS 2007 server

2011-01-03T19:21:00.001-08:00

How to publish the SSRS to MOSS 2007 ? will it impact the MOSS 2007 Database? So we get the advice from some expert as below :

By default, it will be pretty safe for us to integrate reporting service with MOSS. It will add some application pages to MOSS instance, kind of like add a feature to the farm. As I said in the phone, the impact it involve is it will install some application pages to the SharePoint site and report file (.RDL) will be saved in ContentDBs (The version of the backend database is not a matter). However, we only support part of combination of the version of reporting service, reporting service add-in and SharePoint.

Report Server	Add-in	SharePoint	Supported
SQL Server 2008 R2	SQL Server 2008 R2	SharePoint 2010 Products	Y
SQL Server 2008 R2	SQL Server 2008 SP2 (*)	SharePoint 2007 Products	Y
SQL Server 2008 SP1 Cumulative Update #8	SQL Server 2008 R2	SharePoint 2010 Products	Y
SQL Server 2008	SQL Server 2008	SharePoint 2010 Products	N
SQL Server 2008	SQL Server 2008	SharePoint 2007 Products	Y
SQL Server 2005 SP2	SQL Server 2005	SharePoint 2007 Products	Y

(*) It actually has been released and you could download it through http://www.microsoft.com/downloads/en/details.aspx?FamilyID=35c3a13f-4b5e-4d4a-86e4-07ee307b9638

As you could see, if your reporting service is SQL Server 2008 R2 and your SharePoint is 2007, there is no combination supported by us. More information about reporting service integration overview, you could refer to the following document.

Overview of Reporting Services and SharePoint Technology Integration

http://msdn.microsoft.com/en-us/library/bb326358(SQL.105).aspx

After installing Reporting Services Add-in, you could see the following feature in Central Admin in ‘Application Management’ page.

With these links you could configure where the report server is, what kind of authentication mode you want to use, etc.

You could also see the reporting in Site collection features page.

querying membership data

2010-12-14T07:44:00.001-08:00

Found one very usefull query from internet :

http://johnlivingstontech.blogspot.com/2009/11/sharepoint-2007-five-very-helpful-yet.html

thanks for the creator to share this!! Below is the SQL query

1. Select Groups By URL

USE [WSS_Content]

CREATE PROCEDURE [dbo].[usp_SelectGroupsByUrl]

@url NVARCHAR(255)

BEGIN

SELECT Groups.ID AS "GroupID", Groups.Title AS "GroupTitle", Webs.Title AS WebTitle, Webs.FullURL AS WebURL, Roles.Title AS "RoleTitle"

FROM RoleAssignment WITH (NOLOCK)

INNER JOIN Roles WITH (NOLOCK) ON Roles.SiteId = RoleAssignment.SiteId

AND Roles.RoleId = RoleAssignment.RoleId

INNER JOIN Groups WITH (NOLOCK) ON Groups.SiteId = RoleAssignment.SiteId

AND Groups.ID = RoleAssignment.PrincipalId

INNER JOIN Sites WITH (NOLOCK) ON Sites.Id = RoleAssignment.SiteId

INNER JOIN Perms WITH (NOLOCK) ON Perms.SiteId = RoleAssignment.SiteId

AND Perms.ScopeId = RoleAssignment.ScopeId

INNER JOIN Webs WITH (NOLOCK) ON Webs.Id = Perms.WebId

WHERE ((Webs.FullUrl = @url) OR (@url IS NULL))

ORDER BY

Groups.Title, Webs.Title, Perms.ScopeUrl

END

Sample Query

EXEC usp_SelectGroupsByUrl 'Sites/HR/Pay'

Results

GroupID	GroupTitle	WebTitle	WebURL	RoleTitle
71	Manager	Accounting	Sites/HR/PAY	View Only
74	Acct Sr Manager	Accounting	Sites/HR/PAY	Full Control
75	Member	Accounting	Sites/HR/PAY	View Only
76	Viewer	Accounting	Sites/HR/PAY	View Only

2. Select Groups By URL and User

USE [WSS_Content]

CREATE PROCEDURE [dbo].[usp_SelectGroupsByUrlUser]

@login NVARCHAR(255),

@url NVARCHAR(255)

BEGIN

SELECT G.ID AS "GroupID", G.Title AS "GroupTitle", W.Title AS WebTitle, W.FullURL AS WebURL, R.Title AS "RoleTitle"

FROM RoleAssignment AS RA WITH (NOLOCK)

INNER JOIN Roles AS R WITH (NOLOCK) ON R.SiteId = RA.SiteId

AND R.RoleId = RA.RoleId

INNER JOIN Groups AS G WITH (NOLOCK) ON G.SiteId = RA.SiteId

AND G.ID = RA.PrincipalId

INNER JOIN Sites AS S WITH (NOLOCK) ON S.Id = RA.SiteId

INNER JOIN Perms AS P WITH (NOLOCK) ON P.SiteId = RA.SiteId

AND P.ScopeId = RA.ScopeId

INNER JOIN Webs AS W WITH (NOLOCK) ON W.Id = P.WebId

WHERE ((W.FullUrl = @url) OR (@url IS NULL))

AND G.ID IN

(

SELECT Groups.ID FROM GroupMemberShip WITH (NOLOCK)

INNER JOIN Groups ON GroupMembership.GroupID = Groups.ID

INNER JOIN UserInfo ON GroupMembership.MemberID = UserInfo.tp_ID

WHERE ((tp_Login = @login) OR (@login IS NULL))

)

ORDER BY

G.Title, W.Title, P.ScopeUrl

END

Sample Query

EXEC usp_SelectGroupsByUrlUser 'acmedomain\jdoe', 'Sites/HR/Pay'

Results

GroupID	GroupTitle	WebTitle	WebURL	RoleTitle
74	Sr Manager	Accounting	Sites/HR/PAY	Full Control

3. Select Groups By User Login

USE [WSS_Content]

CREATE PROCEDURE [dbo].[usp_SelectGroupsByUserLogin]

@login NVARCHAR(255)

BEGIN

SELECT DISTINCT Groups.ID AS "GroupID", Groups.Title AS "GroupTitle"

FROM GroupMemberShip WITH (NOLOCK)

INNER JOIN Groups WITH (NOLOCK) ON GroupMembership.GroupID = Groups.ID

INNER JOIN UserInfo WITH (NOLOCK) ON GroupMembership.MemberID = UserInfo.tp_ID

WHERE ((tp_Login = @login) OR (@login IS NULL))

ORDER BY Groups.Title

END

Sample Query

EXEC usp_SelectGroupsByUserLogin 'acmedomain\jdoe'

Results

GroupID	GroupTitle
74	Sr Manager
52	Corporate Viewer
14	HR Team Member

4. Select Users By Group

USE [WSS_Content]

CREATE PROCEDURE [dbo].[usp_SelectUsersByGroup]

@groupTitle NVARCHAR(255)

BEGIN

SELECT dbo.UserInfo.tp_ID AS UserID, dbo.UserInfo.tp_Title AS UserTitle, dbo.UserInfo.tp_Login AS UserLogin, dbo.UserInfo.tp_Email AS UserEmail, dbo.Groups.ID AS GroupsID, dbo.Groups.Title AS GroupsTitle

FROM UserInfo WITH (NOLOCK)

INNER JOIN GroupMembership WITH (NOLOCK) ON UserInfo.tp_ID = GroupMembership.MemberID

INNER JOIN Groups WITH (NOLOCK) ON GroupMembership.GroupID = Groups.ID

WHERE ((dbo.Groups.Title = @groupTitle) OR (@groupTitle IS NULL))

ORDER by dbo.UserInfo.tp_Login

END

Sample Query

EXEC usp_SelectUsersByGroup 'HR Team Member'

Results

UserID	UserTitle	UserLogin	UserEmail	GroupsID	GroupsTitle
23	Doe, John	acmedomain\jdoe	jdoe@acmedomain.com	14	HR Team Member
20	Doe, Jane	acmedomain\jadoe	jadoe@acmedomain.com	14	HR Team Member
2	Smith, Bob	acmedomain\bsmith	bsmith@acmedomain.com	14	HR Team Member
24	Yamamoto, Kazue	acmedomain\kyamamoto	kyamamoto@acmedomain.com	14	HR Team Member
46	Nakamura, Ichiro	acmedomain\inakamura	inakamura@acmedomain.com	14	HR Team Member

5 Select Users By Groups

USE [WSS_Content]

CREATE PROCEDURE [dbo].[usp_SelectUsersByGroups]

@groupTitles VARCHAR(1000)

BEGIN

DECLARE @idoc INT

EXEC sp_xml_preparedocument @idoc OUTPUT, @groupTitles

SELECT dbo.UserInfo.tp_ID AS UserID, dbo.UserInfo.tp_Title AS UserTitle, dbo.UserInfo.tp_Login AS UserLogin, dbo.UserInfo.tp_Email AS UserEmail, Groups.Title AS GroupTitle

FROM UserInfo WITH (NOLOCK)

INNER JOIN GroupMembership WITH (NOLOCK) ON UserInfo.tp_ID = GroupMembership.MemberID

INNER JOIN Groups WITH (NOLOCK) ON GroupMembership.GroupID = Groups.ID

JOIN OPENXML(@idoc, '/Root/Group', 0) WITH (Name VARCHAR(100)) AS g

ON dbo.Groups.Title = g.Name

ORDER by dbo.Groups.Title, dbo.UserInfo.tp_Title

END

Sample Query

EXEC usp_SelectUsersByGroups '<Root><Group Name="HR Team Member"></Group><Group Name="Acct Sr Managers"></Group></Root>'

Results

UserID	UserTitle	UserLogin	UserEmail	GroupsID	GroupsTitle
23	Doe, John	acmedomain\jdoe	jdoe@acmedomain.com	14	HR Team Member
20	Doe, Jane	acmedomain\jadoe	jadoe@acmedomain.com	14	HR Team Member
2	Smith, Bob	acmedomain\bsmith	bsmith@acmedomain.com	14	HR Team Member
24	Yamamoto, Kazue	acmedomain\kyamamoto	kyamamoto@acmedomain.com	14	HR Team Member
46	Nakamura, Ichiro	acmedomain\inakamura	inakamura@acmedomain.com	14	HR Team Member
7	Horowitz, Rick	acmedomain\rhorowitz	rhorowitz@acmedomain.com	15	Acct Sr Managers
3	Davis, Jiro	acmedomain\jdavis	jdavis@acmedomain.com	15	Acct Sr Managers

user's list of web sites in SharePoint : SharePoint

2010-12-14T07:16:00.001-08:00

SELECT DISTINCT w.Title, r.WebId, r.Title AS accessLevel, ui.tp_Login,
ui.tp_DomainGroup, ui.tp_Title, w.FullUrl, w.AlternateCSSUrl,
p.ScopeUrl
FROM RoleAssignment AS ra INNER JOIN
Roles AS r ON r.SiteId = ra.SiteId AND r.RoleId
= ra.RoleId INNER JOIN
UserInfo AS ui ON ui.tp_SiteID = ra.SiteId AND
ui.tp_ID = ra.PrincipalId INNER JOIN
Sites AS s ON s.Id = ra.SiteId INNER JOIN
Perms AS p ON p.SiteId = ra.SiteId AND p.ScopeId
= ra.ScopeId INNER JOIN
Webs AS w ON w.Id = p.WebId

copy from Forum

Discovering all workflows in SharePoint farm

2010-12-14T07:06:00.001-08:00

I got a question from user to identify all workflow in my Sharepoint environment. I tried to identify some out of box option but could not find one. After that I have to put my DB cap on and write query on backend content database of MOSS farm to get list all sites and sub containers which are having active workflow running in them. Here is the query :

select distinct(w.fullurl) as SiteName, L.tp_Title as ListName from webs w,workflow wf , Alllists L where w.id=wf.webid and w.siteId=wf.siteId and wf.listId=L.tp_Id

Copy from Here

Clean Up Event ID 7888 and 5553.

2010-12-08T21:23:00.001-08:00

see the error at your event viewer ?

failure trying to synch site 51d6d8b3-9ee0-4af3-af2f-fa5f78cc9651 for ContentDB 840eac13-c23e-4123-9fa2-9d2975d0ff13 WebApp 53ea7eb2-ec0f-4250-9d87-1550224223b8. Exception message was Cannot insert duplicate key row in object 'dbo.UserMemberships' with unique index 'CX_UserMemberships_RecordId_MemberGroupId_SID'.
The statement has been terminated..

Solution here:

http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/11af8a85-0fca-466d-beac-d29d03297edf

solution summary :

Run 'stsadm- o preparetomove -Site <http://whatevertheguiltysiteis/> -OldContentDb <GUID of the contentdb listed in event log error>'
Run 'stsadm -o sync -deleteolddatabases 0'

FQA:

How do i know which site is it by GUID ?

-- QUERY#1 Run this against your config database, this will give you the content database name

SELECT *
FROM [SharePoint_Config].[dbo].[Objects]
WHERE ID='<Content DB Id from error msg>'

--QUERY#2
-- Run followign queries against the database name returned by the QUERY#1

SELECT [FullUrl]
  ,[Id]
  ,[RootWebId]
 FROM [WSS_Content_##_03].[dbo].[Sites]
WHERE ID='<Site ID from event log message>'

or you can run the query at sitemap table at the config database , then you will see all the site under this content db , then manually go to find out on the Path column of the site URL.

SELECT [Id]

      ,[ApplicationId]

      ,[DatabaseId]

      ,[Path]

      ,[Pairing]

      ,[Status]

      ,[Version]

      ,[RedirectUrl]

      ,[HostHeaderIsSiteName]

FROM [MOSS_CONFIG_DB].[dbo].[SiteMap]

where [DatabaseId]='<Content DB Id from error msg>'

Create an installation source that includes software updates (Office SharePoint Server 2007)

2010-12-02T20:19:00.001-08:00

is time to build another environment, to save some step to install the service pack so we can extract the sp2.exe to update folder at the installer folder then will help direct install during installed. **aslipstreamed

http://technet.microsoft.com/en-us/library/cc261890(office.12).aspx

In server farm deployments, all your Web servers must have the same software update version applied. This means that, before you add a new Web server to an existing server farm, this new Web server must have the same software updates as the rest of the Web servers in your server farm. To accomplish this, we recommend that you follow the procedures in this topic to create an installation source that contains a copy of the released version of the software, along with software updates that match those installed on your server farm (also known as aslipstreamed installation source). When you run Setup from this updated installation source, the new Web server will have the same software update version as the rest of the Web servers in your server farm.

Note:

In this article, we use the term software update as a general term for all update types, including any service pack, update, update rollup, feature pack, critical update, security update, or hotfix used to improve or fix this software product.

Use the updates folder

To create an installation source, you must add software updates to the updates folder of the released version of the software.

To use the updates folder

Copy the files from the released version source media for the product to a folder that you can use as an installation point for the servers in your server farm.
Download the appropriate software update package.
Extract the software update files, by using this command:

<package> /extract: <path>

The /extract switch prompts you to provide a folder name for the files, for example, for x86 systems:

wssv3sp2-kb953338-x86-fullfile-en-us.exe /extract: <C:\WSS> \Updates

<C:\WSS> is the location to which you copied the files that you extracted from the Windows SharePoint Services 3.0 released version.

Note:

You must use the default location for the updates folder. If you use the SupdateLocation="path-list" property to specify a different location, Setup stops responding.
Copy the files that you extracted from the Windows SharePoint Services 3.0 software update package to the updates folder you created in the previous step.
Extract the Microsoft Office SharePoint Server 2007 software update files, by using this command:

officeserver2007sp2-kb953334-x86-fullfile-en-us.exe /extract: <C:\rtm_product_path> \Updates

<C:\rtm_product_path> is the location to which you copied the files that you extracted from the Office SharePoint Server 2007 released version.
Copy the files that you extracted from the Office SharePoint Server 2007 software update package to the updates folder containing the source for the released version. You must verify that the Svrsetup.dll file has been copied from the Office SharePoint Server 2007 software update package and you should delete the Wsssetup.dll file.

Important:

Delete Wsssetup.dll because it may conflict with Svrsetup.dll. Having both Wsssetup.dll and Svrsetup.dll in the updates folder for a slipstreamed installation source is not supported.
You can now use this location as an installation point, or you can create an image of this source that you can burn to a CD-ROM.

Note:

If you extracted the software update files to a location to which you had previously copied the source for a released version, the source is updated and is ready to use.

For more information about using enterprise deployment tools to deploy updates, see the article Distribute product updates for the 2007 Office system.

You can download the 32-bit or 64-bit edition of Service Pack 2 (SP2) for Office SharePoint Server 2007 at the following location:

The 2007 Microsoft Office Servers Service Pack 2 (SP2) (http://go.microsoft.com/fwlink/?LinkID=148352&clcid=0x409).

Language template packs

Use the following procedure to create an installation location that you can use to install the language template packs with software updates already applied.

To use the updates folder with language template packs

Download the language template pack package for the released product.
Extract the files from the language template pack package.
Copy the extracted files to a folder that you can use as an installation point for the servers in your server farm.
Download the updated language template pack package for the released product.
Extract the files from the updated language template pack package.
Copy these extracted files to the updates folder, in the subfolder in which you stored the files for the released product in step 3.

You can now use this location as an installation point, or you can create an image of this source that you can burn to a CD-ROM.
To install the language template pack with the software update already applied, run Setup from this location, and then run the SharePoint Products and Technologies Configuration Wizard to complete the configuration.

Delete old folder script

2010-12-01T20:31:00.001-08:00

nice script from internet again :D http://www.eggheadcafe.com/software/aspnet/31061977/an-easy-script-to-delete-folders-on-a-network-share-that-are-older-than-14-days.aspx

change at cint( XX ) > XX for how many days old
Directory > location of the folder you want delete. Network drive also can :)

Dim Directory
Dim Noofdays
Dim FSO
Dim FSO2
Dim LogFile
Dim Folderlist
Dim folders
Directory ="C:\Program Files\Microsoft Office Servers\12.0\Logs\UAP\"
Noofdays=cint(30)
LogFile="C:\Program Files\Microsoft Office Servers\12.0\Logs\UAP\deleted.txt"
Set FSO = CreateObject("Scripting.FileSystemObject")
Set FSO2 = CreateObject("Scripting.FileSystemObject")
Set oFSO = CreateObject("Scripting.FilesyStemObject")
'
If oFSO.FileExists(Logfile) Then
Const ForAppending = 8
Set ofile = oFSO.OpenTextFile(LogFile, ForAppending, True)
Else
Set oFile = oFSO.CreateTextFile(logfile, true)
End If
ofile.writeline "Delete Folders older than 30 days Started   --> " & now()
Set Folderlist = FSO.GetFolder(Directory)
Set folders = Folderlist.SubFolders
For Each d In Folders
'          msgbox d.name
'          msgbox d.size
'          msgbox d.dateCreated
'          msgbox d.dateLastModified
'          msgbox d.dateLastAccessed
tempdirectory = Directory & d.name
If datediff("d",d.dateCreated,now()) > Noofdays Then
FSO2.DeleteFolder(tempdirectory )
ofile.writeline "Deleting Folder...." & tempdirectory
if err.number <>0 then
ofile.writeline cstr(now()) & "    " & Err.description
err.clear
end if
End If
Next
ofile.writeline "Delete Folders older than 30 days Completed --> " &now()
ofile.writeline "--------------------------------------------"
ofile.close

Batch file to keep track enumsites with date :D

2010-11-10T23:43:00.001-08:00

SET D1=%date:~-4,10%
SET D2=%date:~4,-8%
SET D3=%date:~-7,-5%

set tarik=%D1%%D2%%D3%

echo %tarik%

"C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\stsadm" -o enumsites -url http://abc.com > %tarik%.csv

This report will run at scheduled tasks and the purpose is keep track on the sites in which Database , when user need to restore the sites then we only know which DB need to restore back for the sites.

Site Collection Administrator VS Site Owner

2010-11-08T22:56:00.001-08:00

hi hi..one of the question ask by interviewer :D . as i understand is about the recycle bin and quota reach limit contact!! After that i found the answer here :

http://blogs.sharepointhosting.com/Lists/Posts/Post.aspx?ID=61

About twice a week someone calls or writes into support trying to figure out why their Site Owners cannot reset passwords, manage the recycle bin, or "see everything" in site settings. The answer is pretty easy – you have to be a Site Collection Administrator to be able to perform those actions. The next question we get from Site Owners is "how do I become a Site Collection Administrator?" The answer is easy enough, find out who your current Site Collection Administrator is and ask that individual to promote you to that role. Here's a short tutorial on how to create new Site Collection Administrator.

Take a look at the graphic below (click for full version). It displays the different views if you will see if you log into the Site Settings portion of your WSS 3.0 site as a member of the site owner's group and then as a Site Collection Administrator. Hint – the Site Collection Administrator's view is the top image. You can easily replicate this for yourself if you want to test it out – just create a test user that is a member of the Site Owners (or similar) SharePoint security group and go to the site settings page.

Extra this are at site setting :D [all the time our permission is Farm admin , then will never notice about this!! ha ha] Now you know? :D

How to confirm your update item is going to do incremental crawl or not ?

2010-11-02T00:48:00.001-07:00

Search problem for the sub sites… unable to get any error from iis, uls log.

so we need go to search database to see can get any information.

in this case is we want to see the specify sites after i add the item in , this item going to involved in incremental crawl or not.

normally we can see the item at MSSChangeLogCookies table before the incremental crawl start.

Run this query: select * from dbo.MSSChangeLogCookies order by UpdateTime desc > you will see all the item change going to crawl

This table keeps track of the last change that the crawler processed for each content database. You'll want to look at the ChangeLogCookie_new column and you'll see several rows but the output of each will look something like this:

1;0;1b82082a-66eb-47bb-a053-26dde844f5ac;634242420353000000;7403

The GUID 1b82082a-66eb-47bb-a053-26dde844f5ac is the content database id

i already have the Database ID on the sites (go to your content DB , check the database information table will know) , so i will search the results and see my database id is available on the MSSChangeLogCookies.

if you want see how many crawl from the content DB you check, you can use below query on the targert content db:

select * from eventcache with (NOLOCK) where ID > '’7403'

so the total row is the item goign to crawl

yeah !! found the item…so go to run the incremental crawl now…but after run also not working!!! ha ha ha…continue checking….DAY 5

here you go for more detail on the .MSSChangeLogCookies :

http://blogs.msdn.com/b/russmax/archive/2008/11/17/how-to-determine-the-number-of-changes-an-incremental-crawl-will-process-prior-to-initiating-the-crawl.aspx

http://www.cnblogs.com/awpatp/archive/2010/11/02/1866938.html > Chinese version

Crawling history from SSP search DB ( SQL Query)

2010-11-01T03:21:00.001-07:00

Copy from MS:

select * from MSSCrawlhistory

select h.crawlid,
c.catalogid,
c.contentsourceid,
c.startaddressid,
typeofcrawl=
case h.crawltype
when 1 then 'full crawl'
when 2 then 'incremental crawl'
end,
h.status as status_id,
status=
case h.status
when 4 then 'start'
when 9 then 'pause'
when 10 then 'resume'
when 13 then 'stop'
when 11 then 'done'
else 'other'
end,
h.requesttime, h.starttime, h.endtime, datediff(n, h.starttime, h.endtime) as 'duration'
from msscrawlhistory h left join msscrawlcontent c
on h.crawlid=c.crawlid where h.projectid=1 order by h.requesttime desc

change sub-site to a new sub-site URL and wanted the old link auto redirect to the new link.

2010-10-26T03:49:00.001-07:00

Go to old URL link and open in SPD
Create an .aspx page
Paste the coding in .aspx page(target site URL)

<meta http-equiv="refresh" content="0;url=http://xxxxx/sites/xxxxxxxxxx/yyyyyy">

Right click .aspx page > click Set as Home Page
Rename the .aspx page to default.apsx

Search log where to see ?

2010-10-26T03:06:00.001-07:00

problem with the search no results under some subsites , when can check the crawl log or error ?

crawl log under SSP
enable ULS for wss query with veberos, then can see the log at ULS log
go to search database to run the query on terfert sites , see have crawl or not :

select * from MSSCrawlURL (nolock)
where DisplayURL like '%/sites/XXXXX%'

but the problem not yet resolved…to be continue… ha ha

Who Deleted my SharePoint Top Level Sites!!!!

2010-10-25T08:23:00.001-07:00

have customer want to know who deleted his top level sites ( aka site collection ).

the easy answer is the one site collection admin or the user have full control permission at your site collection!!

But let say have 100 site collection admin!!! ha ha..so which one is the one??

oh yeah easy to trace is go to the IIS log file then search it at the folder level:

A word or phrase in the file with

“/sites/<sites collection name>/_layouts/deleteweb.aspx ”.

yeah!!! shoot the one delete it!!! ha ha

-- Query to get all the SharePoint groups in a site collection

2010-10-19T06:25:00.001-07:00

Another cool query from sharepointkings

Customer request the report on all the user in the group on the specify sites collection.

-- Query to get all the SharePoint groups in a site collection
SELECT dbo.Webs.SiteId, dbo.Webs.Id, dbo.Webs.FullUrl, dbo.Webs.Title, dbo.Groups.ID AS Expr1,
dbo.Groups.Title AS Expr2, dbo.Groups.Description
FROM dbo.Groups INNER JOIN
dbo.Webs ON dbo.Groups.SiteId = dbo.Webs.SiteId

-- Query to get all the members of the SharePoint Groups
SELECT dbo.Groups.ID, dbo.Groups.Title, dbo.UserInfo.tp_Title, dbo.UserInfo.tp_Login
FROM dbo.GroupMembership INNER JOIN
dbo.Groups ON dbo.GroupMembership.SiteId = dbo.Groups.SiteId INNER JOIN
dbo.UserInfo ON dbo.GroupMembership.MemberId = dbo.UserInfo.tp_ID

after query the all the memeber of the group, use excel to remove the duplicate data then you will know how many user in the group :)

Unable to reorder content type

2010-10-19T01:34:00.001-07:00

Have user copy the list template from another site and want to reorder the content type, when click on the column order at the content type you will see the error :

Object reference not set to an instance of an object.   at Microsoft.SharePoint.ApplicationPages.ChangeFieldOrderPage.OnLoad(EventArgs e)
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Work around:

you will not be able to manage the order of your columns on the list settings page again until you switch “Allow management of content types” back to No. When the management of content types if enabled, you can then reorder the columns for each specific content type. You may or may not want this to be your standard setup, so my best practice here would be to turn this feature back off when you are finished managing the content type.

Detail step:

1. change the list setting at Advanced settings and change the Allow management of content types to no. > click ok

2. under the column, you will see Column ordering. Click on the column ordering and change the order.> click ok when you done

3. change the list setting at Advanced settings and change the Allow management of content types to yes > click ok

guessing of the root cause:

i think because the content type is attach to the template and no content type created for the sites. once you click on ordering, then will go to search the content type gallery at site level. once cannot found it and error message will show at above. i guess is consider bug :)

Default Recovery Models for MOSS2007 Databases

2010-10-14T19:32:00.001-07:00

Today attend SQL2008 training is talking about what is the different Simple recovery model VS Full recovery Model.Then i am thinking what is the moss2007 setting? Below is the Default Recovery Model.

Simple model :

Automatic reclaims the transaction log
Allow only Full backups

Full Model:

Require transaction log backup (which mean not automatic to shrink your transaction log file)
able to enable recovery the data very near to down time

* oh ya…please remember all the Database here, because one of my interview is asking about this :) . ha ha..

System.Data.SqlClient.SqlError: The backup set holds a backup of a database other than the existing ‘dbName’ database

2010-10-11T19:36:00.001-07:00

familiar with this message? one of my problem always face when restore the shaerpoint content DB from other farm with backup file. today i found out the solution at this blog : http://www.linglom.com/2009/07/08/solved-system-data-sqlclient-sqlerror-the-backup-set-holds-a-backup-of-a-database-other-than-the-existing-dbname-database/

*if you restore the path to different path of mdf and ldf, you need to change it

is great to keep it , so i will copy paste here for future reference.

before start restore the bak file, you need to create the new Database then restore the bak.

Problem

You have backup a database on SQL Server 2005. Then, you try to restore the backup file on an existing database and receive the error message below:

Restore failed for Server ‘SQL Server name‘. (Microsoft.SqlServer.Smo)
Additional information:
System.Data.SqlClient.SqlError: The backup set holds a backup of a database other than the existing ‘dbName‘ database. (Microsoft.SqlServer.Smo)

This error message indicates that you are going to restore a database on another database which are not the same database. For example, you have backup Northwind database and try to restore the backup to AdventureWorks database, the error will occur.

Solution

To solve the problem, you can use the overwrite the existing database option while you’re restoring.

On Restore Database, select Options tab on the left menu. Then, check Overwrite the existing database on Restore options.
Note: This option will overwrite any existing data on the targeted database.
Try to restore the database, the problem should be gone now.

Note: you can also delete the targeted database before perform restore a database. This way also gives the result as same as the solution above.

Filter the calendar of today event

2010-10-06T22:51:00.001-07:00

The start time at calendar Filter is not available then we cannot use [Today] to filter the item. In this case you just created one column and select Calculated (calculation based on other columns) then Formula =[Start Time].

after that you can edit the view with filter on column you created is equal to [Today]:

In this example , i created column name as DOB.

How to Move Large SharePoint Document Libraries

2010-10-01T02:57:00.001-07:00

Faced some problem to move large SharePoint Document during migration , so found out the solution here.

Scenario : one document library is over 25GB so unable to use stsadm export and import.

Solution: have 2 post is same, so i not sure who is the owner. anyway just like to keep track on the coding and sharing here :) [This can move different farm :) ]

http://www.law.com/jsp/lawtechnologynews/PubArticleLTN.jsp?id=1202443237483

http://pravyns.blogspot.com/2010/08/how-to-move-large-sharepoint-document.html

EXPORT AND IMPORT WITH THE SHAREPOINT OBJECT MODEL

To accomplish the goal of copying an arbitrarily large document library, and only that document library, from one site to another, we'll need to use a bit of .NET code and the SharePoint object model. The code will perform two broad tasks:

export the source document library to a set of one or more files on disk; and

import the file-set created in step 1 to the target location.

You could write this code in a number of ways, but for simplicity, I'll create two .NET console applications: ExportDocLib and ImportDocLib. Both these applications must be run on the SharePoint web front-end server of the farm containing the source and target document libraries respectively.

ExportDocLib exports the source document library to operating system files. To create the application, open Visual Studio 2005 or later, and create a new C# console application. Next, add a reference to the Windows SharePoint Services .NET assembly, and then add "using" statements at the top of the program to reference the Microsoft.SharePoint and Microsoft.SharePoint.Deployment namespaces.

The rest of the code is fairly straightforward; you will need to provide references to the site collection and the web site within it that contains your document library (I simply referenced the RootWeb property of my site collection because my document library was contained in the top-level web site), a reference to the list to be copied, and information about where to create the export files and export log. I've also instructed SharePoint to retain the security via the IncludeSecurity switch, and to display progress to a command window as the program runs using the CommandLineVerbose switch. There are many other settings you can use, but those shown below are all you'll need for a basic list export:

using System;

using System.Collections.Generic;

using System.Linq;

using System.Text;

using Microsoft.SharePoint;

using Microsoft.SharePoint.Deployment;

namespace ExportDocLib

{

class Program

{

static void Main(string[] args)

{

// Get handle to web and doclib to export

SPSite site = new SPSite("http://localhost/sites/SITE1");

SPWeb web = site.RootWeb;

SPList list = web.Lists["Shared Documents"];

// Define export settings

SPExportSettings settings = new SPExportSettings();

settings.SiteUrl = "http://localhost/sites/SITE1";

settings.FileLocation = @"C:\Export Files\";

settings.BaseFileName = "SITE1.cmp";

settings.ExportMethod = SPExportMethodType.ExportAll;

settings.LogFilePath =

settings.FileLocation + "SITE1_export_log.txt";

settings.CommandLineVerbose = true;

settings.IncludeSecurity = SPIncludeSecurity.All;

// Add reference to document library to export

SPExportObject exportObject =

new SPExportObject(

list.ID,

SPDeploymentObjectType.List,

web.ID, false);

settings.ExportObjects.Add(exportObject);

// Export it

SPExport export = new SPExport(settings);

export.Run();

}

ImportDocLib is almost a mirror image of ExportDocLib. ImportDocLib will import the document library from the operating system files created by the ExportDocLib program. As before, start by creating a new C# console application in Visual Studio, adding a reference to the Windows SharePoint Services .NET assembly, and by adding "using" statements to reference the two Microsoft.SharePoint namespaces.

Next you'll create a SPImportSettings object and set its properties to define the location of the import files, the location of the site collection and web site where you want your new copy of the document library, and a location for the import log.

Although it’s beyond the scope of this article, the RetainObjectIdentity setting is noteworthy because its value will determine whether you can apply subsequent incremental imports to this same document library. For example, you could copy the full library once, and then periodically import only changed or new items from the source into the target library. To enable these subsequent imports, however, the RetainObjectIdentity setting must be set to "true." However, you may not set it to "true" if you will be importing a document library into the same content database as the source library, because all objects in a SharePoint database must have unique object IDs. The most likely scenario for which you would use the RetainObjectIdentity switch is to create a copy of a document library on a different SharePoint farm, and subsequently to refresh that second library with updates from the original.

using System;

using System.Collections.Generic;

using System.Linq;

using System.Text;

using Microsoft.SharePoint;

using Microsoft.SharePoint.Deployment;

namespace ImportDocLib

{

class Program

{

static void Main(string[] args)

{

// Settings for import

SPImportSettings settings = new SPImportSettings();

// File & path

settings.FileLocation = @"C:\Export Files\";

settings.BaseFileName = "SITE1.cmp";

// Site and web to import to

settings.SiteUrl = "http://localhost/sites/SITE2";

settings.WebUrl = "http://localhost/sites/SITE2";

// Set log file location

settings.LogFilePath =

settings.FileLocation + "SITE2_import_log.txt";

// Display messages while running

settings.CommandLineVerbose = true;

// Don't retain object GUIDs, only necessary

// if want to do incremental imports to same list

// at a later time

settings.RetainObjectIdentity = false;

// Keep security, versions, and date/time stamps

settings.UpdateVersions = SPUpdateVersions.Append;

settings.UserInfoDateTime =

SPImportUserInfoDateTimeOption.ImportAll;

// Import it

SPImport import = new SPImport(settings);

import.Run();

}

You might correctly observe that both the ExportDocLib and ImportDocLib routines can be combined into a single program. This would simplify the process in that you wouldn't need to execute two separate programs to complete the copy process. But when copying a document library from one SharePoint farm to another, you will need to run ExportDocLib on a WFE server in the source farm, and the ImportDocLib on a WFE in the target farm. Keeping them separate gives you the flexibility you need in such instances.

CONCLUSION

With just a bit of .NET coding you can copy document libraries of arbitrary size from one site to another, within or between farms, without the need to purchase a third-party product. With a bit of additional coding you can add the capability of applying incremental updates from a master document library to a copy, thus keeping the secondary library in synch.

At Fenwick & West we have found this technique invaluable for migrating large document libraries between SharePoint farms, filling the gap between the built-in capability to save small libraries using a list template, and backing up full site collections using the backup and export functions of STSADM.

About TEMP folder concept

2010-09-29T04:17:00.001-07:00

Error : STSADM.EXE Export “There is not enough space on the disk”

I was recently doing an export for a pretty big MOSS site and I ran across the following error while using the following stsadm command:

stsadm -o export -url http://servername/site -filename D:\backup\sharepoint.cab -includeusersecurity -overwrite

We verified that the C drive had 1 GB of space and the D drive had 50 GB of space. Simple enought right. Wrong!

After some head scratching, we figured out that the export uses the C drive to store the entirety of the backup files before writing it to the D drive. More specifically, the location pointed to by the TEMP environment variable was being used for the backup.

The solution we found was to change the TEMP and TMP environment variable to point to a temporary folder on the D drive and then do the backup. (I had to also logout and login in order for the variables to take effect).

detail step to change the temp is here

Information from : http://aboutdev.wordpress.com/2008/03/21/stsadmexe-export-there-is-not-enough-space-on-the-disk/

Tech insight 2010 Penang

2010-09-23T10:37:00.001-07:00

22-23 Sept 2010 at USM penang, so far for the SharePoint related session only have 3 but this also help to increase some sharepoint 2010 knowledge.Today have one session is sharing on the SharePoint list Improvement , is look great a lot limitation user cannot get now already available.

Example,

unique column ( something like primary key for the list , cannot duplicate)
validate the columns ( using excel formula)
Lookup Field Relationship Behavior – behavior that can be enforced includes; Project multiple fields into a child list; Joins between lists, Relational integrity between child and parent lists – this brings up new possible security issues & considerations
List Relationships & Data Integrity – one-to-many allows you to trigger cascade delete and restrict delete
more detail you can get from here

ok let me finish the tomorrow session then will share more :)

Set searchadcustomquery back to OOB setting

2010-09-13T22:19:00.001-07:00

how do you reset the searchadcustomquery to oob setting? which is <Property Exist = “No”> , normally used stsadm the value will showed as <Property Exit=”Yes”, Value=””>”.

to set the value back to <Property Exist = “No”> , we can use simple coding as below to reset it.

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using Microsoft.SharePoint;
using Microsoft.SharePoint.Administration;

namespace reset_customQuery
{
    class Program
    {
        static void Main(string[] args)
        {
            using (SPSite site = new SPSite(@"http://abc.com"))
            {
                SPWebApplication apps = site.WebApplication;
                //reset to null
                apps.PeoplePickerSettings.ActiveDirectoryCustomQuery = null;
                 apps.Update();

                Console.WriteLine("Done");
            }
        }
    }
}

to checking your value you can use the stsadm below:

stsadm -o getproperty -url "http://abc.com" -pn peoplepicker-activedirectorysearchtimeout
stsadm -o getproperty -url "http://abc.com" -pn peoplepicker-distributionlistsearchdomains
stsadm -o getproperty -url "http://abc.com" -pn peoplepicker-nowindowsaccountsfornonwindowsauthenticationmode
stsadm -o getproperty -url "http://abc.dhl.com" -pn peoplepicker-onlysearchwithinsitecollection
stsadm -o getproperty -url "http://abc.dhl.com" -pn peoplepicker-searchadcustomquery

How People Picker works ?

2010-09-05T19:17:00.001-07:00

Recently have an issues with the people picker , so just understand how people picker works.

All you want to know about People Picker in SharePoint ( Functionality | Configuration | Troubleshooting ) Part-1

All you want to know about People Picker in SharePoint ( Functionality | Configuration | Troubleshooting ) Part-2

Workflow History Hidden list

2010-09-01T05:50:00.001-07:00

Workflow error ? where to check ? as what i know we have 3 place to check the log :

http://[servername]/[sitename]/lists/Workflow%20History
list settings > workflow settings > View workflow reports
ULS log at \12\logs (CTRL + F search for Workflow Infrastructure )

Basic sharing on Code Access Security (CAS)

2010-08-27T02:45:00.001-07:00

Controlling access to system resources ( Dir structures and file)

WSS have 2 security approaches :

user identity-based
code identity-based [digital certificate or URL or site]

WSS is use .NET Framework , which is using code identity-based approach so call CAS

Levels of trust

Full > unmanaged code
High > cannot call unmanaged code and enterprise service but can send email using SMTP servers , also can access sockets and file system
Medium > SMTP and SQL but cannot access sockets and registry
Low > read only application virtual dir and no network connectivity
Minimal > have execute permission only

WSS have 2 policy ( Virtual server extedned to wss this policy will applied to)

wss_minimaltrust.config
wss_mediumtrust.config

WSS security setting for CAS:

machine.config > c:\windows\micorsoft.net\framwork\V2.0.50727\config
web.config

Web.config located

top level conetn root > C:\Inetpub\wwwroot > configuration for web server
web part resoucces of the global assemy cache
CONFIG ….\web server extensions\60\config\ > define for other extending vs
ISAPI ….for the /_vti_bin
LAYOUTS > for /_layouts
ADMIN > SharePoint CA

How to change the Sharepoint theme template option

2010-08-26T07:02:00.001-07:00

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\1033

have one file name SPTHEMES.XML , this is the file control the theme for SharePoint. if you want to add some custom theme make sure here is added

1033 is for English version , 1031 is German…if you have more so different language keep at different folder .

Utility to quickly reapply themes to sites collection

2010-08-23T05:14:00.001-07:00

After MOSS SP2 Deployment have faced some problem on the theme, so we need to edit the CSS format then to make it take effect on all sites.

now the problem come in …we have so many sites and subsites how going to get it done? as you know we need to reapply the theme then the CSS only take effect.

Luckily have some good utility tool at coplex , is so call retheme.exe.

this help a lot, you can download it from CodePlex.

Below is the coding from the Codeplex reTheme :)

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using Microsoft.SharePoint;

namespace reTheme
{
   class Program
   {
   static void Main(string[] args)
   {
   string siteUrl;
   if (args.Length == 0)
   {
   Console.Write("Site Collection URL:");
   siteUrl = Console.ReadLine();
   }
   else
   {
   siteUrl = args[0];
   }

   try
   {
   using (SPSite site = new SPSite(siteUrl))
   {
   foreach (SPWeb web in site.AllWebs)
   {
   Console.Write(web.ServerRelativeUrl + ": ");
   try
   {

   string themeName = web.Theme;
   web.ApplyTheme("");
   web.ApplyTheme(themeName);
   Console.WriteLine("OK");
   }
   catch (Exception e)
   {
   Console.WriteLine(e.Message);
   }
   }
   }
   }
   catch (Exception e)
   {
   Console.WriteLine(e.Message);
   }
   }
   }
}

Why There is a Shortage of SharePoint Experts

2010-08-10T21:49:00.001-07:00

Copied from here : SharePoint expert are we on the right path ? :D

This post started out as a short reply to a discussion on LinkedIn about this post: Why there is a shortage of SharePoint Experts. Once I hit the fourth paragraph I decided it made a better blog post then a comment. :)

There is a shortage of SharePoint experts because the learning curve for the base technologies is large and the learning curve for the breadth of SharePoint functionality is even larger.

Consider SharePoint 2010 Server Enterprise edition. You can deploy the platform as a public facing site with heavy customization and branding, as a team collaboration portal, as a business intelligence and information delivery, as a stand-alone or connected enterprise content management system, as a search appliance, as a business process automation (workflow) platform, and as a basis for custom applications. There are even more uses, but hopefully you get the basic idea – you can use it for lots of unrelated things.

To call yourself an expert, you should understand most or all of these core uses and the related tools used by end users, developers, and administrators. The SharePoint learning curve is honestly measured in years - assuming that you have a few years' experience building either Windows applications or building and administering complex server systems.

Fortunately, most organizations do not need a full-time SharePoint expert to be successful. Most deployments involve a small subset of the functionality. Most people who work in a corporate setting will use a subset of the tools and fulfill a role in a larger team. If you are looking to implement SharePoint, my advice is to spend the money on a good consultant(s) who is an actual SharePoint expert to create a good foundation and focus on hiring or training full time staff to participate in the build-out and maintain the completed system. Once you are up and running, say goodbye for now to the experts and use them on an ongoing basis only as needed.

The multi-year learning curve plus the sharp upward demand curve means that the supply of experts will be well short of demand for several more years. The supply of people who have serious SharePoint experience will obviously increase along with adoption, but there is no reason you should expect someone who worked in a large heavily controlled collaboration environment where the focus was to maximize stability and minimize risk through aggressive governance to know much about building high-quality public facing sites with significant branding and customization (or vice-versa). That's not to say the person could not make the switch, but it is to say that person is not an expert.

For those organizations looking to find a "SharePoint expert" on the cheap - don't hold your breath. If you are offering a rate that is comparable to that earned by a qualified Web developer in your area, ask yourself why someone who is already a qualified to do work that pays the Web developer rate as a Web developer is willing to provide the additional value of their additional 3+ years of learning in the SharePoint domain at no additional cost to work on SharePoint. Instead try to hire to the narrower skill set you actually need.

The pool of people who have solid experience in one of WCM, ECM, BPA, BI, information architecture, system administration, etc. who can be very productive in a SharePoint environment with the right training and mentoring is large. Build your team from this pool. Trying to build a team of SharePoint experts is much harder and more expensive. More importantly, it's probably an unnecessary and poor strategy.

Posted at 11:30 PM by Doug Ware | Category: Random Whatnot | Permalink | Email this Post | Comments (3)

Comments

great post

I started working with SharePoint back in 2004, was a member of the hosted SharePoint team at Microsoft (now called BPOS-Dedicated), and now work for a SharePoint ISV (echoTechnology, recently acquired by Axceler), and actively write and speak on SharePoitn solutions -- and yet I still feel like a newbie. I know several MVPs and MCMs who are "the" experts on the SharePoint platform who find themselves constantly learning as the platform growns and develops, and especially as partners and customers use it to create new solutions.
But here's my point for responding: If you're looking for SharePoint expertise, you really need to focus on the business problem you're trying to solve rather than find a generalist. Someone with deep vertical experience and some basic SharePoint training is probably a better bet than someone with years of SharePoint but new to your business.

@buckleyplanet at 8/6/2010 1:59 AM

Nice response

The idea that the competency takes years to achieve is an interesting angle I did not consider - I saw it as a skill set developers are not interested in.

Nadir Kamdar at 8/6/2010 11:39 AM

Lack of Investment

As a certified Master, I guess I am one of the *experts*, and I can attest to the enormous learning curve on SharePoint including not only the actual technical skills and APIs, but also the problem domains related to the solutions that SharePoint provides a platform for: Business Intelligence, Knowledge Management, Social Computing, Business Process Automation, etc. These all include significant learning burdens beyond just the technology.
My observations on the lack of SharePoint developers more firmly points a finger a broad problem within the IT industry: Organizations are no longer investing in employees who work in IT favoring to advocate hiring specialists that already have the skills to solve the problem at hand.
- the learning curve is steep and takes a lot of time
- organizations don't yet recognize the learning curve is steep
- organizations don't want to provide the required training
- organizations don't want to pay more for those skills
- organizations don't provide an environment where learning on the job is really tolerated anymore (how can you accurately estimate how long something will take or cost if you have never done it before)
There just isn't a lot of incentive for developers to absorb the learning costs for very little return. IT in general is already suffering from long hours, understaffed projects, and a new technology release cycle that makes it challenging just to keep your skills current, let alone learn significant chunks of new skills. I have seen very few IT organizations in recent years where the IT staff were not *just barely hanging on*.
To take advantage of the SharePoint platform and the considerable features it can provide for a Business Productivity platform, they are simply going to have to change their IT resource management strategies to make appropriate investments in skills development. Until they do, I see the shortage of qualified SharePoint Developers being in short supply for many years to come.

Chris Beckett / SharePoint Bits at 8/6/2010 8:30 PM

The faster way get the enumsites report in excel

2010-08-10T00:23:00.001-07:00

Just notice have the easy way for you to get the nice report with the stsadm enumsites command. you can see the top level sites , owner, content db report between one minute!!! cool !!

stsadm -o enumsites -url http://abc.com > sitelist.xml
Then just opened up the xml file with excel2007. (really beginning to like the features in this version)

It warned that there was not an associated schema, would I like to create on from the file, ‘yes Please’!

And now we can sort, filter, sum, etc.

Great SharePoint Tutorials site to share

2010-08-04T23:16:00.001-07:00

here have some freebies to share from internet, if you like to have some training tutorials for your SharePoint user here is have good one.

Video Tutorials > easy to learn :D enjoy ya

http://www.fpweb.net/sharepoint-tutorials/

Templates & Navigation

Create a SharePoint Group

Delete a Group

Create a Site Template

Create a List Template

Change Title Description & Logo

Change Quicklist Order

Add Quicklist Link

SQL query to find "DayLastAccessed" in portal's Site DB

2010-08-04T06:15:00.001-07:00

is time to do clean up for the SharePoint environment , have 2 option i know we can do that. one is manual one is auto :P ha ha ha

Auto one you can setup at CA, Site use confirmation and deletion /_admin/applications.aspx . not sure how correct is it!! ha ha

but i prefer manual one.so use below query to check day last accessed , so we can guess is still used or not.

SELECT     FullUrl AS 'Site URL', TimeCreated, DATEADD(d,
DayLastAccessed + 65536, CONVERT(datetime, '1/1/1899', 101)) AS
lastAccessDate
FROM         Webs
WHERE     (DayLastAccessed <> 0) AND (FullUrl LIKE N'sites/%')
ORDER BY lastAccessDate

Useful SQL Queries to Analyze and Monitor SharePoint Portal Solutions Usage

2010-08-04T05:59:00.001-07:00

keep track on what i can get from internet about SQL query for SharePoint :

i am looking for last access to sites query, but unable to find..but found some other interesting one.. at below from this link

A List of SQL Queries

Top 100 documents in terms of size (latest version(s) only):

Collapse

SELECT TOP 100 Webs.FullUrl As SiteUrl, 
Webs.Title 'Document/List Library Title', 
DirName + '/' + LeafName AS 'Document Name',
CAST((CAST(CAST(Size as decimal(10,2))/1024 As 
      decimal(10,2))/1024) AS Decimal(10,2)) AS 'Size in MB'
FROM     Docs INNER JOIN Webs On Docs.WebId = Webs.Id
INNER JOIN Sites ON Webs.SiteId = SItes.Id
WHERE
Docs.Type <> 1 AND (LeafName NOT LIKE '%.stp')  
               AND (LeafName NOT LIKE '%.aspx') 
               AND (LeafName NOT LIKE '%.xfp') 
               AND (LeafName NOT LIKE '%.dwp') 
               AND (LeafName NOT LIKE '%template%') 
               AND (LeafName NOT LIKE '%.inf') 
               AND (LeafName NOT LIKE '%.css') 
ORDER BY 'Size in MB' DESC

Top 100 most versioned documents:

Collapse

SELECT TOP 100
Webs.FullUrl As SiteUrl, 
Webs.Title 'Document/List Library Title', 
DirName + '/' + LeafName AS 'Document Name',
COUNT(Docversions.version)AS 'Total Version',
SUM(CAST((CAST(CAST(Docversions.Size as decimal(10,2))/1024 As 
   decimal(10,2))/1024) AS Decimal(10,2)) )  AS  'Total Document Size (MB)',
CAST((CAST(CAST(AVG(Docversions.Size) as decimal(10,2))/1024 As 
   decimal(10,2))/1024) AS Decimal(10,2))   AS  'Avg Document Size (MB)'
FROM Docs INNER JOIN DocVersions ON Docs.Id = DocVersions.Id 
   INNER JOIN Webs On Docs.WebId = Webs.Id
INNER JOIN Sites ON Webs.SiteId = SItes.Id
WHERE
Docs.Type <> 1 
AND (LeafName NOT LIKE '%.stp')  
AND (LeafName NOT LIKE '%.aspx')  
AND (LeafName NOT LIKE '%.xfp') 
AND (LeafName NOT LIKE '%.dwp') 
AND (LeafName NOT LIKE '%template%') 
AND (LeafName NOT LIKE '%.inf') 
AND (LeafName NOT LIKE '%.css') 
GROUP BY Webs.FullUrl, Webs.Title, DirName + '/' + LeafName
ORDER BY 'Total Version' desc, 'Total Document Size (MB)' desc

List of unhosted pages in the SharePoint solution:

Collapse

select Webs.FullUrl As SiteUrl, 
case when [dirname] = '' 
then '/'+[leafname] 
else '/'+[dirname]+'/'+[leafname] 
end as [Page Url], 
CAST((CAST(CAST(Size as decimal(10,2))/1024 As 
   decimal(10,2))/1024) AS Decimal(10,2))   AS  'File Size in MB'
FROM     Docs INNER JOIN Webs On Docs.WebId = Webs.Id
where [type]=0 
and [leafname] like ('%.aspx') 
and [dirname] not like ('%_catalogs/%') 
and [dirname] not like ('%/Forms') 
and [content] is not null 
and [dirname] not like ('%Lists/%') 
and [setuppath] is not null 
order by [Page Url];

List of top level WSS sites and their total size, including child sites in the portal:

Collapse

select FullUrl As SiteUrl,  
CAST((CAST(CAST(DiskUsed as decimal(10,2))/1024 As 
   decimal(10,2))/1024) AS Decimal(10,2))   AS  'Total Size in MB'
from sites 
Where FullUrl LIKE '%sites%' AND 
   fullUrl <> 'MySite' AND fullUrl <> 'personal'

List of portal area and total number of users:

Collapse

select webs.FullUrl, Webs.Title, 
    COUNT(WebMembers.UserId) As 'Total User'
from Webs INNER JOIN WebMembers 
ON Webs.Id = WebMembers.WebId
Where fullurl NOT like '%sites%' AND 
    fullUrl <> 'MySite' AND fullUrl <> 'personal'
Group BY webs.FullUrl,  Webs.Title
Order By  'Total User' desc

List of top level and sub sites in the portal and the number of users:

Collapse

select  webs.FullUrl ,Webs.Title, COUNT(WebMembers.UserId) As 'Total User'
from Webs INNER JOIN WebMembers 
ON Webs.Id = WebMembers.WebId
where fullurl  like '%sites%' AND fullUrl <> 'MySite' AND fullUrl <> 'personal'
Group BY webs.FullUrl,  Webs.Title
Order By  'Total User' desc

List of all portal area:

Collapse

select Webs.FullUrl As [Site Url], 
Title AS [Area Title]
from Webs 
Where fullurl NOT like '%sites%' AND fullUrl <> 
    'MySite' AND fullUrl <> 'personal'

List of the total portal area:

Collapse

select COUNT(*)from Webs 
Where fullurl NOT like '%sites%' AND 
    fullUrl <> 'MySite' AND fullUrl <> 'personal'

List of all top level and sub sites in the portal:

Collapse

select Webs.FullUrl As [Site Url], 
Title AS [WSS Site Title]
from webs
where fullurl  like '%sites%' AND fullUrl <> 
     'MySite' AND fullUrl <> 'personal'

List of the total top level and sub sites in the portal:

Collapse

select COUNT(*) from webs
where fullurl  like '%sites%' AND fullUrl <> 
    'MySite'  AND fullUrl <> 'personal'

List of all list/document libraries and total items:

Collapse

select  
case when webs.fullurl = '' 
then 'Portal Site' 
else webs.fullurl
end as [Site Relative Url], 
webs.Title As [Site Title], 
case tp_servertemplate
when 104 then 'Announcement'
when 105 then 'Contacts'
When 108 then 'Discussion Boards'
when 101 then 'Docuemnt Library'
when 106 then 'Events'
when 100 then 'Generic List'
when 1100 then 'Issue List'
when 103 then 'Links List'
when 109 then 'Image Library'
when 115 then 'InfoPath Form Library'
when 102 then 'Survey'
when 107 then 'Task List'
else 'Other' end as Type,
tp_title 'Title', 
tp_description As Description, 
tp_itemcount As [Total Item]
from lists inner join webs ON lists.tp_webid = webs.Id
Where tp_servertemplate IN (104,105,108,101, 
    106,100,1100,103,109,115,102,107,120)
order by tp_itemcount desc

Note: the tp_servertemplate field can have the following values:

104 = Announcement

105 = Contacts List

108 = Discussion Boards

101 = Document Library

106 = Events

100 = Generic List

1100 = Issue List

103 = Links List

109 = Image Library

115 = InfoPath Form Library

102 = Survey List

107 = Task List

List of document libraries and total items:

Collapse

select  
case when webs.fullurl = '' 
then 'Portal Site' 
else webs.fullurl
end as [Site Relative Url], 
webs.Title As [Site Title], 
lists.tp_title As Title,
tp_description As Description, 
tp_itemcount As [Total Item]
from lists inner join webs ON lists.tp_webid = webs.Id
Where tp_servertemplate = 101
order by tp_itemcount desc

List of image libraries and total items:

Collapse

select case when webs.fullurl = '' 
then 'Portal Site' 
else webs.fullurl
end as [Site Relative Url], 
webs.Title As [Site Title], 
lists.tp_title As Title,
tp_description As Description, 
tp_itemcount As [Total Item]
from lists inner join webs ON lists.tp_webid = webs.Id
Where tp_servertemplate = 109  -- Image Library

order by tp_itemcount desc

List of announcement list and total items:

Collapse

select case when webs.fullurl = '' 
then 'Portal Site' 
else webs.fullurl
end as [Site Relative Url], 
webs.Title As [Site Title], 
lists.tp_title As Title,
tp_description As Description, 
tp_itemcount As [Total Item]
from lists inner join webs ON lists.tp_webid = webs.Id
Where tp_servertemplate = 104  -- Announcement List

order by tp_itemcount desc

List of contact list and total items:

Collapse

select case when webs.fullurl = '' 
then 'Portal Site' 
else webs.fullurl
end as [Site Relative Url], 
webs.Title As [Site Title], 
lists.tp_title As Title,
tp_description As Description, 
tp_itemcount As [Total Item]
from lists inner join webs ON lists.tp_webid = webs.Id
Where tp_servertemplate = 105   -- Contact List

order by tp_itemcount desc

List of event list and total items:

Collapse

select case when webs.fullurl = '' 
then 'Portal Site' 
else webs.fullurl
end as [Site Relative Url], 
webs.Title As [Site Title], 
lists.tp_title As Title,
tp_description As Description, 
tp_itemcount As [Total Item]
from lists inner join webs ON lists.tp_webid = webs.Id
Where tp_servertemplate = 106   -- Event List

order by tp_itemcount desc

List of all tasks and total items:

Collapse

select  
case when webs.fullurl = '' 
then 'Portal Site' 
else webs.fullurl
end as [Site Relative Url], 
webs.Title As [Site Title], 
lists.tp_title As Title,
tp_description As Description, 
tp_itemcount As [Total Item]
from lists inner join webs ON lists.tp_webid = webs.Id
Where tp_servertemplate = 107  -- Task List

order by tp_itemcount desc

List of all InfoPath form library and total items:

Collapse

select  
case when webs.fullurl = '' 
then 'Portal Site' 
else webs.fullurl
end as [Site Relative Url], 
webs.Title As [Site Title], 
lists.tp_title As Title,
tp_description As Description, 
tp_itemcount As [Total Item]
from lists inner join webs ON lists.tp_webid = webs.Id
Where tp_servertemplate = 115  -- Infopath Library

order by tp_itemcount desc

List of generic list and total items:

Collapse

select  
case when webs.fullurl = '' 
then 'Portal Site' 
else webs.fullurl
end as [Site Relative Url], 
webs.Title As [Site Title], 
lists.tp_title As Title,
tp_description As Description, 
tp_itemcount As [Total Item]
from lists inner join webs ON lists.tp_webid = webs.Id
Where tp_servertemplate = 100  -- Generic List

order by tp_itemcount desc

Total number of documents:

Collapse

SELECT COUNT(*)
FROM     Docs INNER JOIN Webs On Docs.WebId = Webs.Id
INNER JOIN Sites ON Webs.SiteId = SItes.Id
WHERE
Docs.Type <> 1 AND (LeafName NOT LIKE '%.stp')  
               AND (LeafName NOT LIKE '%.aspx') 
               AND (LeafName NOT LIKE '%.xfp') 
               AND (LeafName NOT LIKE '%.dwp') 
               AND (LeafName NOT LIKE '%template%') 
               AND (LeafName NOT LIKE '%.inf') 
               AND (LeafName NOT LIKE '%.css')

Total MS Word documents:

Collapse

SELECT count(*)
FROM     Docs INNER JOIN Webs On Docs.WebId = Webs.Id
INNER JOIN Sites ON Webs.SiteId = SItes.Id
WHERE
Docs.Type <> 1 AND (LeafName LIKE '%.doc') 
  AND (LeafName NOT LIKE '%template%')

Total MS Excel documents:

Collapse

SELECT count(*)
FROM     Docs INNER JOIN Webs On Docs.WebId = Webs.Id
INNER JOIN Sites ON Webs.SiteId = SItes.Id
WHERE
Docs.Type <> 1 AND (LeafName LIKE '%.xls') 
    AND  (LeafName NOT LIKE '%template%')

Total MS PowerPoint documents:

Collapse

SELECT count(*)
FROM     Docs INNER JOIN Webs On Docs.WebId = Webs.Id
INNER JOIN Sites ON Webs.SiteId = SItes.Id
WHERE
Docs.Type <> 1 AND (LeafName LIKE '%.ppt') 
    AND  (LeafName NOT LIKE '%template%')

Total TXT documents:

Collapse

SELECT count(*)
FROM     Docs INNER JOIN Webs On Docs.WebId = Webs.Id
INNER JOIN Sites ON Webs.SiteId = SItes.Id
WHERE
Docs.Type <> 1 AND (LeafName LIKE '%.txt')  
    AND  (LeafName NOT LIKE '%template%')

Total Zip files:

Collapse

SELECT count(*)
FROM     Docs INNER JOIN Webs On Docs.WebId = Webs.Id
INNER JOIN Sites ON Webs.SiteId = SItes.Id
WHERE
Docs.Type <> 1 AND (LeafName LIKE '%.zip') 
    AND  (LeafName NOT LIKE '%template%')

Total PDF files:

Collapse

SELECT count(*)
FROM     Docs INNER JOIN Webs On Docs.WebId = Webs.Id
INNER JOIN Sites ON Webs.SiteId = SItes.Id
WHERE
Docs.Type <> 1 AND (LeafName LIKE '%.pdf') 
    AND  (LeafName NOT LIKE '%template%')

Total JPG files:

Collapse

SELECT count(*)
FROM     Docs INNER JOIN Webs On Docs.WebId = Webs.Id
INNER JOIN Sites ON Webs.SiteId = SItes.Id
WHERE
Docs.Type <> 1 AND (LeafName LIKE '%.jpg') 
               AND  (LeafName NOT LIKE '%template%')

Total GIF files:

Collapse

SELECT count(*)
FROM     Docs INNER JOIN Webs On Docs.WebId = Webs.Id
INNER JOIN Sites ON Webs.SiteId = SItes.Id
WHERE
Docs.Type <> 1 AND (LeafName LIKE '%.gif') 
               AND  (LeafName NOT LIKE '%template%')

Total files other than DOC, PDF, XLS, PPT, TXT, Zip, ASPX, DEWP, STP, CSS, JPG, GIF:

Collapse

SELECT count(*)
FROM     Docs INNER JOIN Webs On Docs.WebId = Webs.Id
INNER JOIN Sites ON Webs.SiteId = SItes.Id
WHERE
Docs.Type <> 1 AND (LeafName NOT LIKE '%.pdf') 
AND  (LeafName NOT LIKE '%template%')
AND (LeafName NOT LIKE '%.doc')
AND (LeafName NOT LIKE '%.xls')
AND (LeafName NOT LIKE '%.ppt')
AND (LeafName NOT LIKE '%.txt')
AND (LeafName NOT LIKE '%.zip')
AND (LeafName NOT LIKE '%.aspx')
AND (LeafName NOT LIKE '%.dwp')
AND (LeafName NOT LIKE '%.stp')
AND (LeafName NOT LIKE '%.css')
AND (LeafName NOT LIKE '%.jpg')  
AND (LeafName NOT LIKE '%.gif')  
AND (LeafName <>'_webpartpage.htm')

Total size of all documents:

Collapse

SELECT SUM(CAST((CAST(CAST(Size as decimal(10,2))/1024 
       As decimal(10,2))/1024) AS Decimal(10,2))) 
       AS  'Total Size in MB'
FROM     Docs INNER JOIN Webs On Docs.WebId = Webs.Id
INNER JOIN Sites ON Webs.SiteId = SItes.Id
WHERE
Docs.Type <> 1 AND (LeafName NOT LIKE '%.stp') 
               AND (LeafName NOT LIKE '%.aspx') 
               AND (LeafName NOT LIKE '%.xfp') 
               AND (LeafName NOT LIKE '%.dwp') 
               AND (LeafName NOT LIKE '%template%') 
               AND (LeafName NOT LIKE '%.inf') 
               AND (LeafName NOT LIKE '%.css') 
               AND (LeafName <>'_webpartpage.htm')

Shorting the content DB from enumlist.txt

2010-08-01T23:17:00.001-07:00

this morning try to get the URL and Database from enumlist for orphan object checking , but after import to excel with delimited but look like the information is not good enough. ha ha, then learnt some excel function to short it out. so want to keep track new excel command i learnt :

this command is trim up the front part

=RIGHT(A1,LEN(A1)-FIND("e=",A1))

Results is :

="MOSS_Content_DB1" StorageUsedMB="28.7" StorageWarningMB="80" StorageMaxMB="100" />

Another column is trim out the left over

=LEFT(B2,(FIND("St",B2)))

Results is:

="MOSS_Content_DB1" S

At last replace the “ and “ S with space, then you will get the DB name :)

Maybe look stupid , but i get what i want!! i think will have more easy way , but i unable to think out yet. so i just use the faster skill i know to get my information i think this is fair.

please do share with me the easy way , if you have :)

SharePoint 2010 Advanced IT Pro Training

2010-07-24T02:29:00.001-07:00

yeah… hear from management we are going to deploy this Q1 2011, so excited on this!! But not sure is true or not… ha ha..but anyway need to start prepare my self on this :D .

Keep track on the Training first :)

http://technet.microsoft.com/en-us/sharepoint/ff420396.aspx

SharePoint 2010 Advanced IT Pro Training

1Core Architecture of SharePoint 2010

2Security in SharePoint 2010

3IT Pro Management in SharePoint 2010

4Upgrading to SharePoint 2010

5Enterprise Search in SharePoint 2010

6Content Management in SharePoint 2010

7Composite Solutions in SharePoint 2010

8Communities in SharePoint 2010

9Business Intelligence in SharePoint 2010

10SharePoint Online Overview

Additional Training

SharePoint 2010 Advanced Developer Training

Videos, hosted labs, presentations

Get Started with SharePoint 2010 for IT Pros

Videos on how IT Pros new to SharePoint Server 2010 can get started.

Microsoft Learning | SharePoint Training

Certifications, instructor-led training, e-learning

Disk space VBS

2010-07-22T00:25:00.001-07:00

CDisk.bat

cscript "DisksSpace.vbs" > Disks.txt //nologo
sendmail.bat

DisksSpace.vbs

On Error Resume Next

Const wbemFlagReturnImmediately = &h10
Const wbemFlagForwardOnly = &h20

aryServers = Array("001.abc.com","002.abc.com")

WScript.Echo

For Each strComputer In aryServers
   WScript.Echo strComputer
   Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\CIMV2")
   Set colItems = objWMIService.ExecQuery("Select * From Win32_LogicalDisk Where DriveType = 3", "WQL", _
                                      wbemFlagReturnImmediately + wbemFlagForwardOnly)

   For Each objItem In colItems
      SpaceFree = Round(objItem.FreeSpace/(1024*1024))
      Wscript.Echo objItem.Name & Chr(9) & SpaceFree & "MB free" & Chr(9) & "(" & Round(100 * (objItem.FreeSpace/objItem.Size),2) & "%)"
   Next
   WScript.Echo
Next

WScript.Echo

sendmail.bat

@Echo off
call "sendMail.wsf"

sendmail.wsf

<job>

Const ForReading = 1, ForWriting = 2, ForAppending = 8

Dim fso, f
Set fso = CreateObject("Scripting.FileSystemObject")
Set f = fso.OpenTextFile("Check_Disks.txt", ForReading)

BodyText = f.ReadAll

f.Close
Set f = Nothing
Set fso = Nothing

Set objMessage = CreateObject("CDO.Message")
objMessage.Subject = "Disk Report: " & Now() & " [ GMT+8 ]"
objMessage.From = "noreply@abc.com"
objMessage.To = "tosomeone@abc.com"
objMessage.Cc = "ccsomeone@abc.com"
objMessage.TextBody = BodyText
objMessage.Configuration.Fields.Item _
("http://schemas.microsoft.com/cdo/configuration/sendusing") = 2
objMessage.Configuration.Fields.Item _
("http://schemas.microsoft.com/cdo/configuration/smtpserver") = "gateway.abc.com"
objMessage.Configuration.Fields.Item _
("http://schemas.microsoft.com/cdo/configuration/smtpserverport") = 25
objMessage.Configuration.Fields.Update

objMessage.Send

</script>
</job>

F5 with MOSS 2007 to improve our availability

2010-07-19T23:47:00.001-07:00

yahoo!! recently i have found out how to improve the SLA to customer by enable HTTP health Monitor at our BigIp pool TTP health Monitor at our BigIp pool .

if you have BIG-IP^® LOCAL TRAFFIC MANAGER then you can create the HTTP health Monitor to monitor your MOSS2007. This will help to monitor your MOSS site , if discover one your web front end server is not respond on the IIS between the timeout you set then big ip will not send any request from user to this server. So user will not impacted by that server :)

below have more information you can refer to how to set it :

http://www.f5.com/products/big-ip/product-modules/local-traffic-manager.html Model

http://www.f5.com/pdf/deployment-guides/f5-sharepoint07-dg.pdf

setup F5 with MOSS 2007

ISA 2006 Web Caching

2010-07-19T00:02:00.001-07:00

Recently user face the page cannot display problem , so i started to investigate on our ISA server on this problem… so i have found out how to set the web Caching step at below. emm..Look like our caching is enable but the rule is something wrong :D …ok, just want to keep the setup here

below information is from : http://www.isaserver.org/tutorials/ISA-2006-Web-Caching.html

A lot of ISA Firewall admins might forget that the ISA Firewall isn’t only an enterprise class network firewall, but also a nifty Web caching device. The Web caching feature allows the ISA Firewall to cache the responses it gets from user requests from behind the ISA Firewall. This can speed up the Web browsing experience for users and even allow users to view cached content when the Web server hosting the content is offline.

The first step in getting Web caching working is to turn it on. To do that, open the ISA Firewall console and then expand the Configuration node in the left pane of the console. Click on the Cache node and then click the Tasks tab in the Task Pane. Click the Define Cache Drives (Enable Caching) link.

Figure 1

In the Define Cache Drives dialog box, enter the size of the disk cache you want to have. I generally allow about 10 MB per user. In the example below you see that I’m setting the cache to be 250 MB. Keep in mind that the maximum size for a cache file on a single drive is 64 GB. Also, the drive much be formatted to use NTFS.

Figure 2

Right click the Cache node in the left pane of the console and click Properties.

Figure 3

The General tab of the Cache Settings dialog box tells you how big your cache is.

Figure 4

On the Advanced tab you have several options.

The Cache objects that have an unspecified last modification time option allows the ISA Firewall to cache objects that don’t have a time stamp. When the ISA Firewall caches these objects, you can set custom cache rules to determine how long these objects stay in the cache.

The Cache objects even if they do not have an HTTP status code of 200 allows you to cache pages that do not return an OK response when connecting to the destination Web server. This allows for offline caching and other caching behaviors.

The Maximum size of URL cached in memory (bytes) option allows you to configure the maximum size of an object placed in the in-memory cache. The in-memory cache is much faster than the on-disk cache, so you don’t want to clog the in-memory cache with large objects, such as graphics and files. You can enter a custom value if you like, but the default is 12800 bytes.

You have two options for when If Web site of expired object cannot be reached. You can configure the ISA Firewall to:

Do not return the expired object (return an error page) This tells the ISA Firewall to return an error indicating that the object is not available, even if the object is in the cache.
Return the expired object only if expiration was. This allows the ISA Firewall to return objects in the cache even when the Web site is not available. How long the ISA Firewall will continue to return these objects from the cache depends on the following settings: At less than this percentage of original Time-to-Live, But no more than (minutes). These two options determine how long the object can be returned from the cache when the Web server hosting that content is not available.

The Percentage of free memory to use for caching is actually the percentage of memory you want to give to the cache file. It’s really not the percentage of “free” memory because the cache memory size won’t change over time and will not give up memory to other processes. So this is a static value based on how much memory your machine has. The default is 10%, but if you have lots of RAM, you might consider increasing this at 10% intervals until you run into trouble to see how much memory you can dedicate to Web caching.

Figure 5

Creating Cache Rules

Cache rules allow you to define what objects you want to cache and the cache behavior for those objects. To create a cache rule, click on the Cache node in the left pane of the ISA Firewall console and then click the Tasks tab on the Task Pane. Click the Create a Cache Rule link.

Figure 6

On the Welcome to the New Cache Rule Wizard page, enter a name for the cache rule. In this example we’ll create a cache rule that is applied to all content accessed from the Internet, with the exception of the Microsoft Update Site, which has its own rule that should be above all other rules. Click Next.

Figure 7

On the Cache Rule Destination page, click the Add button. In the Add Network Entities dialog box you select which destination you want this rule to apply to. In this example we want the rule to apply to all Internet access, so we’ll click the Networks folder and then double click on the External entry. Note that you can create very finely tuned cache rules by having the destination be a URL Set or a Domain Name Set. Click Close on the Add Network Entitiesdialog box.

Figure 8

On the Content Retrieval page you set how objects stored in the cache are retrieved when requested by users. You have three options:

Only if a valid version of the object exists in cache. If no valid version exists, route the request to the server. So, if there is an expired version of the object in the cache, the ISA Firewall will connect to the Web server to get a fresh version of the object
If any version of the object exists in cache. If none exists, route the request to the server. So, if there is any version of the object in the cache, it will return it to the user, even if it is expired. If no version of the object is in cache, it will go to the Web server to get it.
If any version of the object exists in cache. If none exists, drop the request (never route the request to the server. So, if any version is in the cache, it will return it to the user. If there is no version of the object in the cache, the ISA Firewall will not try to get it from the Web server and will just drop the request

The default option is Only if a valid version of the object exists in the cache. If no valid version exists, route the request to the server. In this example we’ll select the default and click Next.

Figure 9

On the Cache Content page you tell the ISA Firewall whether retrieved content is stored in the cache. By default, an object is stored in the cache only if its source and request headers indicate that the object should be cached. However, you have the option to select the option Never, no content will ever be cached. So, if there is a site where you never want the content to be cached, maybe because you always need the most up to date content, then you should select that option.

Three other options are:

Dynamic content: When you select this option, the ISA Firewall will cache the content, even if the Web server indicates that the content should not be cached.
Content for offline browsing: This allows the ISA Firewall to cache content even when the Web server is not available or the location of the objects has changed.
Content requiring user authentication for retrieval: This allows the ISA Firewall to access content that required user authentication. Be careful with this one, because it has the potential to allow users to see the authenticated content from other users

Click Next.

Figure 10

On the Cache Advanced Configuration page, you can limit the size of cached objects. By default, there is no limit to the size of an object that can be cached. However, if you select the Do not cache objects larger than option, you can set a maximum size of cached objects. Use this option if you’re worried about your cache file getting filled up too quickly by very large objects, such as pictures or data files.

The other option on this page is Cache SSL responses. Be aware that the ISA Firewall cannot cache SSL responses in a forward Web proxy scenario because the ISA Firewall cannot see what’s inside the SSL tunnel. However, if you install Collective Software’s ClearTunnel, you will be able to cache responses made over an SSL connection. For more information about ClearTunnel, check out www.collectivesoftware.com.

Click Next.

Figure 11

On the HTTP Caching page, unless the source specifies an expiration time, HTTP objects stored in the cache are updated according to the time-to-live (TTL) settings. The TTL is the amount of time content remains in the cache before it expires. Content age is the amount of time since the object was created or modified, which is information contained in the object’s header.

The Set TTL of objects (% of content age) is set at 20% by default. HTTP objects remain valid in the cache according to TTL settings. TTL settings are based on the TTL defined in the response header, and the TTL boundaries defined in the cache rule. The percent of the content age is a percentage of the time of the content's existence. The higher the percentage, the less frequently the cache is updated.

You can also set TTL time boundaries, so that you can set custom No less than and No more than times.

Finally, you can override expiration times included in the cached object’s header by selecting the Also apply these TTL boundaries to sources that specify expiration.

Click Next.

Figure 12

The ISA Firewall can also cache objects obtained via FTP for Web Proxy clients (the ISA Firewall won’t cache FTP responses from non-Web proxy client applications). The default is to enable FTP caching and a TTL of 1 day is selected. You can change these defaults to meet your needs. Click Next.

Figure 13

Click Finish on the Completing the New Cache Rule Wizard page.

Figure 14

On the Cache Rules tab, right click the All Sites rule and click Move Down. We need to do this because theMicrosoft Update Cache Rule needs to be on top.

Figure 15

SPDisposeCheck.exe > check the coding have memory leaking or not

2010-07-14T02:23:00.001-07:00

this tool can help us to detect the code , dll , cs and etc file have any possible memory leak coding use or not, since majority administrator and engineer not really have developer skill so we need to make sure the customization going to deploy to our sharepoint environment is safe and will not impacted our environment performance.

Download here > http://code.msdn.microsoft.com/SPDisposeCheck

more explain here > http://jomit.blogspot.com/2009/01/disposing-sharepoint-2007-and-wss-30.html

how to use?

after install then go to the .exe path and run the command as below :

C:\Program Files\Microsoft\SharePoint Dispose Check>SPDisposeCheck.exe xxx.dll

Ok you will see the report.

Creating a SharePoint Solution Package (.wsp) in 5 steps – from Evgeny Tugarev

2010-06-23T02:49:00.001-07:00

For those who are new to the SharePoint solutions and features I would recommend to try the SharePoint Solutions Generator, which is a part of theWindows SharePoint Services 3.0 Tools: Visual Studio 2005 Extensions. It is a windows stand-alone application that converts your existing SharePoint web site into the solution package and creates a Visual Studio project for you to use. Nice isn’t it?

What I personally don’t like in the automatic tools is that they always hide some part of the job they are doing behind the scenes. In this scenario you can’t really control and sometimes understand of that is going on. So, today I would like to blog about of how to manually create the SharePoint feature containing the list, how pack it into the solution package and finally deploy it to the production server. Everything will be done without any use of Visual Studio or other tools (only Notepad++).

So, let’s start!

Step 1. Folders

First, create the folder structure for the solution. I used MySolution but you can give a name whatever you want. Two folders were created beneathMySolution - source and bin. First is for the compiled package, second – to keep the feature and the customized list. I use the same file structure for the feature as in SharePoint - one folder per feature. Check out your SharePoint features hive at C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES\DiscussionsList and see how it’s organized.
In the source folder I made the feature folder called MyList and 2 subfolders inside - List Templates and Messages. In the end you will have something like this:

Step 2. Building a Feature.

Here we create our feature based on the SharePoint discussions list. Go to MyList folder and create a file feature.xml, where we reference 2 files, first – list manifest MyListManifest.xml and the second – schema.xml which is describing the list metadata. And don’t forget to change the GUID of feature Id with your own!

feature.xml
<?xml version="1.0" encoding="utf-8"?>
<Feature Id="A8E6B85F-D81A-4cc1-9708-D15FEF359DE2"
Title="My Feature"
Description="This is my feature containing a list"
Version="1.0.0.0"
Hidden="FALSE"
Scope="Web"
DefaultResourceFile="core"
xmlns="http://schemas.microsoft.com/sharepoint/">
<ElementManifests>
<ElementManifest Location="ListTemplates\MyListManifest.xml" />
<ElementFile Location="Messages\schema.xml"/>
</ElementManifests>
</Feature>

Copy the original schema.xml file from the C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES\DiscussionsList\Discuss folder to the Messages folder, and you have a list schema to start from, MyListManifest.xml we’ll create manually in the ListTemplates folder –

MyListManifest.xml

<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<ListTemplate
Name="Messages"
Type="108"
BaseType="0"
OnQuickLaunch="FALSE"
FolderCreation="FALSE"
SecurityBits="12"
Sequence="999"
DisplayName="My List"
Description="This is my custom list based on the discussions list"
Image="/_layouts/images/itdisc.gif"/>
</Elements>

What is important here is that the Name attribute must have the same name as the folder where schema.xml is placed, Messages, as SharePoint will look for the schema.xml file at that location!

After the end of this step you have 3 new files as seen on the picture

Step 3. Building a Solution Package (.wsp)

SharePoint Solution Packages (wsp ) provide a great way to distribute all your customization in just one flask and the creation of the .wsp ain’t so painful operation as you may think, I would say it is easy as hell! Everything starts from the traditional solution manifest .xml file in the Source folder:

manifest .xml

<?xml version="1.0" encoding="utf-8"?>
<Solution xmlns="http://schemas.microsoft.com/sharepoint/"
SolutionId="EC2EFD73-DBA2-4c0e-9C18-C8FC43F72E6C" >
<FeatureManifests>
<FeatureManifest Location="MyList\Feature.xml"/>
</FeatureManifests>
</Solution>

Here, we reference our Feature.xml file that we had created before at the Step 2, and as you may guess it’s a good way to replace the the SolutionId GUID with something brand new J. The next that should be created is the data definition file (.ddf). It’s a simple text file with the building instructions for themakecab utility because the .wsp package is nothing more than a cabinet file with the .wsp extension. (If you rename .wsp or .stp file to .cab you’ll be able to see its contents). Let’s create a wsp.ddf in the Source folder:

wsp.ddf

.OPTION Explicit
.Set DiskDirectory1="..\bin"
.Set CabinetNameTemplate="MyListSolution.wsp"

manifest.xml

; These directory names (DestinationDir) are used for the folders creation under 12\TEMPLATE\Features

.Set DestinationDir="MyList\ListTemplates"
MyList\ListTemplates\MyListManifest.xml

.Set DestinationDir="MyList\Messages"
MyList\Messages\schema.xml

.Set DestinationDir="MyList"
MyList\Feature.xml

In this file we set an output folder for the compiled package..\bin, its name MyListSolution.wsp and we tell makecab to include 4 files (marked in red) and create 3 folders at the deployment phase (in blue). Now it’s time to build everything into a single file, but before we do that I create a build.cmd file in theSource folder with some lines to facilitate the building process

build.cmd

@setlocal
@pushd.

@cd %~dp0

makecab /f wsp.ddf

@popd
@endlocal

Here I reference the wsp.ddf file with processing instructions which I created before. After you run it your solution package will appear in the bin folder:

Step 4. Solution deployment.

So, the solution package has just been created and the last thing that is left to do is to deploy it to our production server. I always like then the script is doing my job, so I put 2 .cmd files into the bin folder to deploy and retract my.wsp package so I don’t have to deal with stsadm utility from command line.

DeployMyListSolution.cmd

@setlocal
@pushd.

@set PATH=C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN;%PATH% @cd %~dp0

stsadm.exe -o addsolution -filename MyListSolution.wsp
stsadm.exe -o deploysolution -name MyListSolution.wsp -local

@pause
@popd
@endlocal

RetractMyListSolution.cmd

@setlocal
@pushd.

@set PATH=C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN;%PATH% @cd %~dp0

stsadm.exe -o retractsolution -name MyListSolution.wsp –local
stsadm.exe -o deletesolution -name MyListSolution.wsp

@pause
@popd
@endlocal

After the solution is deployed you can activate the feature in the Site features menu of you site and start using the new list!

Step 5. Using the feature.

Before our custom list can be used the feature containing it must be activated within the SPWeb scope.

After activation is done your custom list will appear on the site’s create page and you can create list instances!

Have fun!
Next time I will talk about site definitions inside the solutions.

Evgeny Tugarev.

IU for deployment of SharePoint 2007 solution files

2010-06-22T20:18:00.001-07:00

more user friendly installation and deployment of SharePoint 2007 solution files to a SharePoint server farm. Distribute your SharePoint solution files with this installation program instead of a raw script using STSADM.EXE to install and deploy the solution.

Just notice we can package our .wsp to become exe, so we no need run the stsadm and few more step need to do only can deploy our solution.

codeplex have offer the easy way for us to convert the .wsp to exe, which mean your admin/customer no need know the stsadm command also can install with click next !! :D

here you go : http://sharepointinstaller.codeplex.com/

Freeware to compare your Text file

2010-06-21T21:43:00.001-07:00

Yesterday our sharepoint web.config suddenly change , not sure what going on. The faster recover is restore the backup config , after we restore service is up. Now is the problem we need to compare 2 web.config file see what is missing or edited…

do a search on internet found out the good tool to use , which is ExamDiff . this tools is good to help you compare the different on the text file

Issues : all user unable to log in to ishare , show error message “Parser error”

Work around : restore the web.config from backup

Root cause : Following changer “Configure Session State value from x to y minutes and changed back to 60minutes “ will cause the web.config file deleted some information at web.config. This changer only impacted with our highly customize web.config file. :(

Walkthrough: Creating a Basic Web Part

2010-06-16T20:27:00.001-07:00

http://msdn.microsoft.com/en-us/library/ms415817(office.12).aspx

This walkthrough provides the steps for creating a basic custom Web Part that can be added to your Web Part Pages. It is a simple Web Part that allows the user to define a custom message to be displayed inside the Web Part. This Web Part will derive from the ASP.NET 2.0 Web Part class, which is the recommended practice for Windows SharePoint Services. Note that this walkthrough describes how to create a Web Part without the Visual Studio Extensions for Windows SharePoint Services.

:) own bookmark for developer step

You have chosen to delete too many groups at once. Select fewer groups and try again. ( folder permission)

2010-06-09T20:01:00.001-07:00

ha ha ha…Unable to delete too much user at folder permission !! try to remove user permission at folder permission level then get the error message “You have chosen to delete too many groups at once. Select fewer groups and try again.”

Work around :

delete batch by batch ( maximum user can delete one time is around 450 user)

in this case, because of the admin not manager the user permission by domain or share point group and then cause too much individual user permission appear. If the admin manage the permission properly this issue will not happen.

The Login Name does not exist and SharePoint

2010-06-03T19:57:00.001-07:00

After you migrate a user from a different Active Directory domain, the user can no longer access Windows SharePoint Services ??

yeah, if you get the error message “The Login Name does not exist” i think probably is due to the user migrate from one domain to domain. After do some search at internet found have a lot good information. so i would like to share what i have found at internet.

Here > from Microsoft , tell you what STSADM can help on this

Here > Tell how the stsadm work, can see from SQL table. this is cool!!

Here > more step to let you check what permission the old account have :D

MOSSRAP at MOSS2007

2010-06-01T01:15:00.001-07:00

Pre-Implementation

Scoping tool

During ( public folder for user 1 year)

RADT ( run at tool machine ) [Risk Assessment %]

Data Collector ( run at wfe)

Post- Implementation

Report Generator ( Private)

Install MOSSRAP 2.1 > MOSSRAPToolset\public

Step to run the tool :

Client folder >

Data Collector > cut this folder to WFE or Application C drive

Move cluster server to cluser , if the server not in manually add in.
Add cluster server back to the cluster node. ( save the setting at MossContext.xml )
Start and the process start ( take few hour to complete, depend on the number of sites )

After finish run cut the folder back to the MOSSRAP server back.

Now can start to run the RADT at tool machine.

locate XXXX output

locate Engagement Manifest > EngagmentManifest.xml ( Installer folder )

start the RADT

Change setting

performance monitoring > Perfmon Scheduler (1440 == 24 Hour )
loading context
loading topology file > General Tab (go to data collector open the topology file) , after setting change click save settings.

Run Tests

Survey will not included , this is for private.

after run need stop Engine

Last step View Results

Most information can view from the issues session.

Query to Get Database Size

2010-05-26T07:04:00.001-07:00

s
easy method to show all your database size :

use master
declare @PageSize varchar(10)
select @PageSize=v.low/1024.0
from master..spt_values v
where v.number=1 and v.type='E'
select name as DatabaseName, convert(float,null) as Size
into #tem
From sysdatabases where dbid>4
declare @SQL varchar (8000)
set @SQL=''
while exists (select * from #tem where size is null)
begin
select @SQL='update #tem set size=(select round(sum(size)*'+@PageSize+'/1024,0) From '+quotename(databasename)+'.dbo.sysfiles) where databasename='''+databasename+''''
from #tem
where size is null
exec (@SQL)
end
select * from #tem order by DatabaseName
drop table #tem

this script is created by Here

SharePoint Dispose Checker Tool

2010-05-26T06:36:00.001-07:00

ha ha..this is the tool to check on your dll or exe develop by your sharepoint developer have any memory leak on the solution or not. you can use the tools to check and tell the developer what going wrong and cause your server IIS out of memory.

Resource Page Description
SPDisposeCheck is a tool to help you to check your assemblies that use the SharePoint API so that you can build better code. It provides assistance in correctly disposing of certain SharePoint objects to help you follow published best practice. This tool may not show all memory leaks in your code. Further investigation is advised if you continue to experience issues.
SPDisposeCheck.exe takes the path to a managed .DLL or .EXE or the path to a directory containing many managed assemblies. It will recursively search for and analyze each managed module attempting to detect coding patterns based on the MDSN article.

The SPDisposeCheck tool can be downloaded here.

Delete MOSS orphan sites manually in SQL DB

2010-05-20T00:16:00.001-07:00

Running Scoping tool and stsadm -o databaserepair but the results is showed different, but the scoping tool is listed more orphan sites. so we decide to clean up the orphan sites , due to the stsadm unable to detect that mean the databaserepair will not able to help us to do clean up.

after discuss with mircrosoft , we decide to remove it manually from MOSS SQL DB. This make me excited because can learnt a lot one the MOSS DB table.

This clean up activity we can category in detect , confirm , delete.

Detect stage: Run the scooping tool if don’t have than maybe you can follow the script at internet .

Confirm stage ( make sure the content is really not in used) :
Results from the detect stage will provided the siteid and content DB.
use the path URL from the script go to CA to check which one is actual use content DB. after this go to sql content DB check the Database id.
once get the Databse id you can keep this is record then can refer to the database id you get from sitemap.

select * from sitemap where id='xxxxxx-xxxxxx--xxxxxxx-xxxxxxxx’
this results will give the orphan database id

select * from SiteMap where Path like 'url'
EXP:
Select * from SiteMap where Path like '/sites/accmgmt'
this will give you the database id same as the CA.(which is the database current in use)

please confirm the orphan databaseid is not same as the CA databaseid

Delete satage ( we will go to the content db to delete the orphan site)
Use [databasename]
exec proc_DeleteSite [siteId]

Learn how to use excel generate Batch file

2010-05-19T18:18:00.001-07:00

Some time we need to create some batch file with a lot command line from some list , example you have MOSS list in excel then you want add the parameter to stsadm then create batch file.

here is the some command i learn and able to help on the purpose :

=VLOOKUP ( what you want to look , look from where, which column you want the return, false value is exact value)

=REPLACE( start from, start from which location ,how many world u want replace, copy from where )

=CONCATENATE( "string", c1 (Colum parameter) )
>>>>> results is string [c1 value]

MOSS Diagnostic Logging

2010-04-22T21:35:00.001-07:00

hey!!! my sharepoint site have error!!! as you get the escalation from user , what log you will check first ? for me i will check on the following sequence:

Event logs : this is the first log to check…because want to know server is working fine or not. (simple way to overview for application and server)

IIS LOG: C:\WINDOWS\system32\LogFiles [different web apps have ID, so you can refer to IIS see which folder you should refer to the correct folder ]

Over here you can get more detail on the user information and activity going on at IIS.

ULS (Unified Logging Service )LOG : [%CommonProgramFiles%\Microsoft Shared\web server extensions\12\LOGS]

This log mainly is for sharepoint log only , you need to enable the log at CA page.

About Subsite backups

2010-04-13T23:50:00.001-07:00

From the command line:
Backup Farm/Content Databases: STSADM -o backup -directory
Backup Site Collections: STSADM -o backup -filename
Backup Web/subsite: STSADM -o export

From the UI:
Backup Farm/Content Databases: Central Admin > Operations > Perform a Backup
Backup Site Collections:  emm…not yet discover any free one..u can develop one? not sure DPM able to do that or not…emm…maybe can :D
Backup Web/subsite: SharePoint Designer

CHANGING A SITE COLLECTION URL

2010-04-07T20:31:00.001-07:00

Can i rename the URL with STSADM ? oh yeah… stsadm -o renameweb maybe can help ….after check on that this, only can rename the subsites not the root (sites collection URL)

ok so as a conclusion , the only way is Backup , Delete , Restore is the one!!

The command line for doing this would look like:

stsadm –o backup –url http://team/sites/site1 -overwrite -filename backupsite1.dat
stsadm –o deletesite –url http://team/sites/site1
stsadm –o restore –url http://team/sites/site2 -filename backupsite1.dat

MOSSRAP

2010-04-05T19:51:00.001-07:00

What is MOSSRAP, that is Risk and Health Assessment Program for Microsoft Office SharePoint Server®.

I am sharing this because just want to keep track the process, so this this is the way i need to learn to become SharePoint consultants.

Program Phase:

Environmental Assessment phase ( collect data from machine and staff )
Analysis and Reporting phase (compared with Microsoft best practice)
Remediation phase. (Recommendations)

Executive summary > summary of environment and action needed

Listed our the issues at high risks and no risks > high risk one need to resolve it immediate

Risk Assessment Scorecards > rate in 3 indicates ( Low , Medium , High)

MOSS RAP Consolidated Scorecard

MOSS Configuration
Customizations ,Farm Topology ,Search ,Security

Operational Excellence
Change Management ,Database ,Disaster Recovery ,Monitoring ,Search ,Service Level Agreement High

Server Configuration
Antivirus ,Database ,Event Logs ,Farm Topology ,IIS Information ,Load Balancing ,Network ,OS Information ,Security

Server Health
Antivirus ,Customizations ,Event Logs ,IIS Information ,Performance ,Security , Security Updates

High Risk Scorecard > List down the high risk area detail
Medium Risk Scorecard > List down the Medium risk area detail
Medium Risk Scorecard > List down the Low risk area detail

Detail for all issues and recommendation :

Issue: <area have issues>
Importance: <why is important>
Recommended Resolution: <Solution or Work around>
Recommended Reading: <Microsoft URL>
Description: <where is the problem>
Detail: <specify the area have problem>

Formulas in calculated columns

2010-03-28T23:45:00.001-07:00

hi hi.. recently start work on Sharepoint admin area also, so now want to share about the simple formulas in calculated columns. At the custom list you can add in one new column with calculated type, then can use simple formula to pull data from othe column and do some calculation .
Below is the simple formula for IF :
=IF(Column1<=Column2, "OK", "Not OK")
However using the function like that causes a syntax-error.
The correct syntax is
=IF(Column1<=Column2; "OK"; "Not OK")
Date and time, Financial, Information, Logical, Lookup and reference, Math and trigonometry, Statistical,Text and data
http://office.microsoft.com/en-us/sharepointtechnology/CH100650061033.aspx
http://office.microsoft.com/en-us/sharepointtechnology/HA011609471033.aspx