Archive for category SharePoint

Error when you try to edit the content source schedule in Microsoft Office SharePoint Server 2007: “Access is denied”

To work around this issue, you must add the WSS_WPG group to the Tasks folder. To do this, follow these steps:

  1. Use an account that has administrative permissions to log on to the computer that is running the Office SharePoint Server 2007 indexing service.
  2. Click Start, click Run, type cmd, and then click OK.
  3. At the command prompt, type the following command, and then press ENTER:attrib –s %windir%\tasks

    Note In this example, %windir% is the path of the Windows folder. For example, the path can be C:\Windows.

    Note If Windows Explorer is open when you make this change, you will not see the extra tab in Windows Explorer. If Windows Explorer is already open, close and then reopen it before you perform step 4.

  4. In Windows Explorer, right-click the Tasks folder, and then click Properties.
  5. In the Tasks Properties dialog box, click the Security tab, and then click Add
  6. In the Select Users, Computers, or Groups dialog box, type WSS_WPG in the Enter object names to select box, and then click OK.
  7. Grant the following permissions for the WSS_WPG account, and then click OK:
    • Read
    • Write
  8. Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
  9. In Internet Information Services (IIS) Manager, right-click ComputerName (local computer), click All Tasks, and then click Restart IIS.
  10. Click Start, click Run, type cmd, and then click OK.
  11. At the command prompt, type the following command, and then press ENTER:attrib +s %windir%\tasks

    Note This resets the Tasks Property back to the default view.

No Comments

SharePoint Lists Web Services GetListItems Row Limitation

Check and see if you placed a rowlimit in your getlistitems method. If you want to return everything in the current view that you have you can use “0” see example below: XmlNode doc = doclist.GetListItems(“My List”, “My View”, query, viewFields, “0”, queryOptions, null);

No Comments

Change SharePoint Connection String

Change in Registry:
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Secure\ConfigDb

No Comments

Setting up FBA Claims in SharePoint 2010 with Active Directory Membership Provider

Setting up FBA Claims in SharePoint 2010 with Active Directory Membership Provider – Sridhar’s blog – Site Home – MSDN Blogs



No Comments

Forms Authentication in SharePoint Products and Technologies (Part 2): Membership and Role Provider Samples

1. Create Class Library based on following instructions
Forms Authentication in SharePoint Products and Technologies (Part 2)_ Membership and Role Provider Samples

2. Update the web.config of Central Admin

3. Create Web Application and Site Collection for SharePoint, and update the web.config of the sharepoint to add the new “MembershipProvider”

4. *** Note: the debug message is not meaningful. the details of the error can be found in SharePoint Log, C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS


No Comments

Could Not Load File Or Assembly ‘xxxxx’ Or One Of Its Dependencies. An Attempt Was Made To Load A Program With An Incorrect Format

How to fix it:

Simply follow the steps below :
open project properties window.
select Build tab
Change it to ‘Any CPU’
Save your changes.
Compile your project and run

No Comments

Using iMacro for Performance Testing

Stopwatch is useful for counting the duration of the steps.

No Comments

Share Same Form Based Authentication with SharePoint and custom Application

1> Setup sharepoint for FormsAuthetication. Follow steps from

2> Share same machine key between Sharepoint application and ASP.NET application

3>Make sure you have same Authetication cookie path. (I would not change anything here just leave by default which is “/”)

and that should work


** Use protection=”Validation” if your application CANNOT single sign on with the SharePoint.

It is because authentication cookie size .net framework 4 and .net framework 2 isn’t the same (or doesn’t support). This is the workaround solution!

No Comments

How to Activate the Drop Down Menu in MOSS Sites

MOSS 2007 sites can display drop down menus in the tabbed navigation across the top.  Unfortunately there is not an easy check box to activate this functionality, instead things just have to be set up the right way.  If you want your MOSS site to show drop down menus, make sure the following is true or walk through the following steps:

  1. From the root of the parent site (Home) choose to create a new site (Site 1). Once that site is created, you will be in that new site. From here choose to create a new page.
  2. Once that is created, choose to create another new site (Sub Site 1).  Then create a new page in Sub Site 1.
  3. Your site structure should resemble this, see structure.
  4. For each site in the Navigation settings, both Show Subsites and Show Pages should be checked.
    • Select Site ActionsSite SettingsModify Navigation.
    • Check Show subsites and Show pages in the first row.  See sample.
  5. The end result would be a tab in the horizontal bar for Site 1, with a vertical drop showing Sub Site 1. See sample.

The navigation shows sub sites under the parent and published pages at the parent. Pages for one site are stored flat in a single library.  If you want the navigation to show 2nd level sub site pages or 3rd level sub sites under the 2nd level, you need to make a very minor tweak to the master page that the site is using.

  1. Using SharePoint Designer (SPD), open the master page being used by the site.   Warning!  Making edits to this file will customize the file, a.k.a. unghost it.  Don’t worry you can always undo this action.
    • In SPD, navigate to _catalogs/masterpage/*.master
    • How do you know which master the site is using? In the site, go to Site Actions Site Settings Modify All Settings, then choose Master page under the Look and Feel column.  Check which master page is selected in each drop down.
  2.  In the master page file, search for SharePoint:AspMenu.
    • You will more than likely have more than one instance of a menu control.  Look at the IDs to find the right navigation control for what you want to edit.  They are intelligently named, you will be able to sort out which one you need.   For default.master, look for ID=”TopNavigationMenu”.
  3. In the properties for the tag, find MaximumDynamicDisplayLevels=”1″.  Change the number from 1 to 2.
  4. Save the file and publish the master page (do this from SPD, Manage Content and Structure, or the Master Page Gallery).
  5. Refresh your browser.  Now when you mouse over Site 1 – Sub Site 1, you should see another level of navigation pop up.  See sample.

Cool, ehh?  Please don’t abuse this dynamic display level.  As tempting as it is to provide instant access to something 5 levels deep in your site, drop down menus notoriously aggravate end users.  I highly recommend using no more than 2 levels (what we set in this walk through).

No Comments

Connecting Sharepoint 2007 to your Domino LDAP server

Say, you have Domino up and running in your organisation and your looking into deploying Sharepoint 2007. Wouldn’t it be nice if you could make use of the user accounts created in your Domino directory for authentication in Sharepoint ?

Well, you can, and it’s even not that difficult. If found this post written by Liam Cleary and modified the things a bit to focus on Domino.

First, make sure you have the LDAP task running on your Domino server. Pretty straightforward, if it’s not running, just type


on your server console.

Then log in into your sharepoint server as an administrator and locate the web.config file for your administration server. On my server it was located in


The last part of the path is the port on which your administration server is listening and might differ for your specific installation.

Edit the web.config fil and locate the line saying
Add after that line this xml snippet:

Notice that in the xml code above there are two references to the LDAP/Domino server (I marked them blue), in my case localhost. Make sure you change those to your servername.

After you did that, locate the web.config file for your current sharepoint application (the one that listens on port 80). It’s probably located in


And add the same lines at the same location as you did for the first web.config file.

We are almost there, please stick with me for a bit more.

Open your Central Adminstration site and navigate to

Application Management > Authentication Providers

On the top right of the list you can switch to your current sharepoint site (the one listening on port 80).

Click on the ‘Default’ zone to edit it. You will get a form to complete.

Change Authentication Type to: Forms

The form reloads and a few additional fields appear.

Enter “LDAPMember” in the Membership provider name field (if you changed the name in the web.config use that name here. It should be identical to the name used in the config file)

Enter LDAPRole in the Role Manager name field.

Disable Client Integration (it doesn’t work well when you use Forms based authentication).

Click save.

We are almost done now. Now in order for you to have access using your new accounts to you main website, you will have to grant some users access rights.

You can do that by navigating to

Central Administration > Application Management > Policy for Web Applications

Now click ‘Add Users’. Make sure you select your ‘default’ sharepoint application listening on port 80 again. Then pick a zone (I picked ‘default’) and click next.

Add a Domino shortname (for instance yours) in the Users field and click the little icon to check the user names. If everything went well, your username should become black underlined. Assign the appropriate permissions, and click ‘finish’

You are all done. Navigate to your main site and you should see a form to log in, enter your Domino shortname, your Domino password and you should log in.


, ,

No Comments