The SSP Timer Job Distribution List Import Job was Not Run.Event Id 6641

If  the user profiles are not updated after you changed users property on the SSP and you get the following error

log in your SharePoint server 2007

Then follow the following solutions steps

1. One of Microsoft’s best practices is to make sure that the application pool account for your SSP and your service account for the SSP are the same account.

2. Make sure to add this account to the backup operator’s local group on all your MOSS servers.

3. If you are using Kerberos authentication for your web applications make sure you set your service name principle account for you ssp on you MOSS application server. In order to complete this operation you must install Window support tools from your Windows server installation files under support>>tools>>supporttools.msi. Once you have installed the support tools go to start>>All programs>> Windows support tools>> command prompt. 
setspn.exe –A HTTP/name_of_ssp_address domain\appication 
Assume your site address is ssp, your domain is SharePoint, and your application pool account is svc_ssp. Run these commands 
setspn.exe –A HTTP/ssp SharePoint\svc_ssp (Run this Command) 
setspn.exe –A HTTP/ SharePoint\svc_ssp (Run this command) 

If you are using Kerberos authentication on any of your web applications you must run these commands for the web applications to function properly including your central administration site.

4. Check your system event logs on your MOSS server for any DCOM errors.  You will notice your DCOM errors are associated with your application pool accounts.  Add these accounts to the IIS WAMREG admin service.  Make sure the accounts have the local launch, remote launch, local activation, and remote activation.

5. Next stop your Office SharePoint Server Search through central administation>> operations>> Services on Server.

6. Then go to central administration>> operations>> service accounts.  Click on web application pool.  Then under web service choose Windows SharePoint Service Web application.  Next under application pool, choose your Shared Service Provider application pool account.  Under configurable you will notice that it populated your application pool account.  Now re-enter your password and click ok.

7. Login into all your MOSS servers and run iisreset /noforce.

8. Go back to central administation>> operations>> Services on Server and restart your Office Server Search.

9. Then go to central administation>>Application Management>> Manage this Farm’s Shared Services.  click the drop down on the default SSP and click edit properties.  In the SSP service credentials enter username and password.  In the index, server category select your index server and then click ok. Make sure you wait about 5 minutes.

I hope this should work.

User Profile Synchronization is Not Working in SharePoint Server 2007, Event id 5555

If the user profile is not synchronizing after you changed the property of the user property on SSP and if you found the following error message in your event log

then follow the following solution steps.

Solution Steps:

open the command prompt and run the following command.

stsadm -o sync -DeleteOldDatabases 0

then it removing the old data.

Now it should work properly.

Configure Twitter Search with Sharepoint and Search Server

This blog explains the steps in configuring Twitter Search with Sharepoint and Search Server 2008

Prerequisite: Search Server Express or Search Server 2008 installed and configured

1. Navigate to the Search Administration Page (under Shared Services Administration) from SharePoint Central Administration Page,

2. Navigate to the  Search Administration Page as shown below

3. Then Click on “Federated Locations” Link under “Queries and Results” for configuring the search on Twitter.

Federated Locations is used to configure search on third-party websites like Google, Bing, etc…

4. Now we are in “Manage Federated Locations”. Using this page we can add or import a new third party search to SharePoint.

Click on “New Location” link to add a new search to the SharePoint Page. This will show the “Add Federated Location” page.

5. The Add Federated Location page has 4 categories as General information, Location Information, Display Information, Restrictions, and Credentials Information.

On General Information enter the

Location Name as “Twitter Search”,

Display Name as “Twitter Search”,

Description as “Search tweets on Twitter”

Author as “Copmany Name”

Version as “1”

Leave the Trigger part as “Always: Query should always match”

6. Federated Search was mainly configured on Location information. There only we have to add the configuration address for search.

Select the Location type as ‘OpenSearch 1.0/1.1”, then only we can search on other servers,

Add the search address as{searchTerms}

on Query Template and “More Results” link Template.

6. Then on Display information check the “Use Default Formatting” to view the default view for the Twitter Search.

If you want to apply your own style, uncheck the “Use Default Formatting” and edit the style sheet in XSL textbox and the parameters needed for XSLT under properties textbox.

7. After finishing this, Click OK to save this new New location.

8. After that, we have to add the Federated web part to Search results page to get the result on Search Query.

Add the Federated Result Web part, and then edit the properties to select the location type for the web part.

9. On editing the properties for webpart, choose the location type “Twitter Search”

10. Click OK to save the properties to Federated Results webpart.

11. We can also change the view of the Twitter search to look more attractive by changing the XSL stylesheet on XSL Editor property under display properties on when editing the web part.

Move SharePoint Site from One Domain to Another Domain

I am having two separate domains in Mumbai and Chennai called Mumbai as and Chennai as Both domains are running SharePoint server 2007 with a different domain.
I am planning to move Mumbai SharePoint server 2007 site to Chennai SharePoint server 2007.
For this scenario, you can do the following steps to move the SharePoint site from domain to another.
NOTE: SharePoint version should be same, mean if you installed the service pack on source machine (Mumbai SharePoint server) at the same, you should install the service pack on the destination server (Chennai SharePoint server)
You can check the version of SharePoint, open SharePoint central administration->site setting, you can view the version.
Steps to be the following:
Source SharePoint server (Mumbai SharePoint server):
    1. Take back of the SharePoint site which you required to move using stsadm.exe command utility.
Stsadm.exe –o backup –url -filename c:\mumbai.bak
    2. Move the backed up file to destination SharePoint server.

Destination SharePoint server (Chennai SharePoint server):

1. Create new SharePoint web application on the SharePoint server

     2. Create SharePoint site collection for the new web application.
Note: site collection template should be same as source SharePoint server. For example, if you created team template on source SharePoint server, then you should create same team template in destination SharePoint server.
     3. Then you need to overwrite the database using stsadm command utility
Stsadm.exe –o restore –url -filename c:\mumbai.bak –overwrite
     4. If you access the site immediately after restore, you will get the access denied error.
     5. Add a user via command line because the restored site will deny all of your login attempts (unless your server is on the same domain as the original source server – *** this post describes the steps for restoring to a different domain***)
Using the central administration console, you will note that the site collection still references the original administrators which are now invalid on this new domain (Chennai domain SharePoint).
NOTE: you can view using following steps >> Central Administration >> Application Management >> Site Collection Administrators (on Chennai SharePoint central administration domain).
     6. Now you need to change ownership of the site collection using the following command.
stsadm -o siteowner -url http://chennai/ -ownerlogin chennai\administrator
      7. Now if you refresh central admin console you will see the new administrator as an owner, you can change the secondary administrator at this point as well using same utility.
stsadm -o adduser -url http://localhost -userlogin administrator -useremail [email protected] -role administrator -username administrator
      8. Now reset the IIS and you can log in the main site collection as an administrator.
      9. Then you can optionally run this to clean up the old lingering logins explicitly

                stsadm -o migrateuser -oldlogin olddomain\MossAdmin -newlogin newdomain\MossAdmin

Article was written by


What’s New in SharePoint 2010

In previous versions; by out of the box, alerts are sent only through e-mails, but in SP2010 we can able to send an alert to mobile devices as SMS Message. For that, we have a new property under SPAlert, that indicates whether the alert is delivered as E-mail or as an SMS Message.

By default, alerts can be sent only through e-mail. But we can change that default setting by coding option using the new DeliveryChannels Property of SPAlert class. This DeliveryChannels property specifies the delivery method of the alert.

The following snippet used to set the SMS delivery method to the Alert.

oAlert.DeliveryChannels = SPAlertDeliveryChannels.Sms;

SPAlertDeliveryChannels is the enumerated member, which specifies the method of delivering alerts.

Member Name



Delivery as E-mail

Delivery as SMS Message

The following example code used to update the SMS delivery method to all the alerts for every user available in the Current website.

SPWeb oWebsite = SPContext.Current.Web;
SPUserCollection collUsers = oWebsite.Users;
    foreach (SPUser oUser in collUsers)
        SPAlertCollection collAlerts = oUser.Alerts;
         foreach (SPAlert oAlert in collAlerts)
             oAlert.DeliveryChannels = SPAlertDeliveryChannels.Sms;

That’s all for now!! I’ll be back with the post on a new feature in SharePoint 2010.

Creating a SharePoint Sub Site from Custom Template Through Code

This blog explains the steps involving creating a Sharepoint subsite from a custom template by calling Sharepoint web service from .Net code.

Sharepoint Meeting Webservice has a method named CreateWorkspace that allows the creation of subsite on the specified Sharepoint server. The URL for meeting web service is http:///_vti_bin/Meetings.asmx where can even be a subsite location. The syntax for the Create workspace method is

CreateWorkspace(title, templateName, lcid, timeZoneInformation)
Title is the title for the new sub site that will be created.
TemplateName is the name of the template based on which the
new sub site will be created.
LCID is the locale identifier
timeZoneInformation is the time zone information for the new sub site.

All the arguments mentioned above are pretty straightforward except for the template name. For creating subsites based on the default Sharepoint templates we need to pass the template id such as “MPS#”.Whereas for creating based on custom templates we need to pass the template file name as the argument such as “Mytemplate.stp”

To have a preview of the built-in site templates click here. To find out the templates ids click.

Typical code for creating subsite custom template is shown below

Samples.SP.TimeZoneInf tz = new Samples.SP.TimeZoneInf();
SP.Meetings meetings = new SP.Meetings();
meetings.Url = “http://sitename/_vti_bin/meetings.asmx”;
meetings.Credentials = new System.Net.NetworkCredential(“user name”, “password”, “domain”);
meetings.CreateWorkspace(“Site title”, “Mytemplate.stp”, 1033,tz);


Removing Link from People Name in SharePoint List

Sharepoint lists can have a special type of column that refers to a person or group. When viewing the list data the person column will display the person name and picture with a  link to the page that displays the user details(userdisp.aspx). Sometimes it would be desirable to prevent users from viewing the user details.  This can be done by using a few lines of Jquery script. Following steps explains the steps involved

1. Navigate to the Sharepoint page that displays the list with the people link

2. The people column will be displayed like the one shown below

3.  Add a content editor webpart to the page

4. Modify the content editor webpart and go to the source editor and add the below script

5. Now the people column will be displayed like the one shown below

Highlighting Overrun Tasks In SharePoint Gantt Chart

Though the Gantt Chart that comes out of the box with Sharepoint is useful and easy to setup it has many limitations. One of the features that Sharepoint users were longing for is applying the color code to different tasks. last week Christophe of Path to Sharepoint came up with an interesting way of applying color code using custom images and Jquery script.

The technique used by Christophe can be used to apply different colors to tasks based on their priority.  I have applied the same color changing technique and devised a method for highlighting tasks that have overrun their due date.

Sharepoint adds two custom properties originalTaskFinishDate and originalTaskStartDate to each of the rows in Gantt chart. With this date values, we can determine if a task has overrun its due date. We can then highlight the overrun tasks by changing the image from blue to red using Jquery.


Below is the Jquery code that highlights the overrun tasks

<script src=””type=”text/javascript”></script>
var currentdate = new Date();
//Get the task due date
var d = new Date(this.attributes(“originalTaskFinishDate”).value);
//if due date has value
if(d.getYear() !=1)
var datediff = Math.round((currentdate – d) / (24 * 60 * 60 * 1000));
//if due date is greater than current date
if (datediff > 0 ){
var source=this.innerHTML;
//check if the task is completed
var match = /(Normal.gif)|(MileStone.gif)/.test(source)
var source1=this.src;
//replace blue with red
source1 = source1.replace(/.gif/, “Red.gif”);
//change the path of image to where the red images are stored
source1 = source1.replace(/\/_layouts\/images/,”/Projects/GImages”);

In order to add this highlighting to Gantt charts in your Sharepoint pages, you need to do the following steps



  1. Change the path of the images(/projects/GImages in a script) to the path where you have placed the red images. The images can be downloaded from here.

Adding Document Icons in SharePoint Dataview

When viewing documents list from a document library in Sharepoint the default view page the list displays a document icon which gives a visual cue to the user about the type of document. This feature is not available when using a dataview control within a Sharepoint page. By default, the dataview gives only the file path and file name as shown below.

We can display the document icon name by including the special document icon column to the dataview XSLT as below

            <xsl:value-of select=”@DocIcon”>

This will just add the document icon name as shown below

The document icons are stored in the _layouts/images folder. We need to use the special ddwrt:MapToIcon function and the DocIcon column to map the exact icon path. The syntax for ddwrt:MapToIcon function is

MapToIcon(string szProgID, string szExt)

So to  display an image that shows to the document icon  we need use the below HTML

<a href={@DocIcon}” src=”/_layouts/images/{ddwrt:MapToIcon(string(@HTML_x005F_x0020_File_x005F_x0020_Type),string(@DocIcon))}” _fcksavedurl=”/_layouts/images/{ddwrt:MapToIcon(string(@HTML_x005F_x0020_File_x005F_x0020_Type),string(@DocIcon))}” />


No Item Exists Error Because of Querystring Parameter Name

When working with Data views and filters in Sharepoint Designer, the Sharepoint page may sometimes throw an odd error like

No item exists at http://sitename/pagename.aspx?Id=2.It may have been deleted or renamed by another user.

The typical cause for this issue is that a dataview webpart within the page uses a filter condition that maps ID property of a list to a querystring parameter whose name is ID.

The issue can be easily solved by renaming the querystring parameter to a different name other than ID. After renaming the parameter the Sharepoint page will work as expected.