SharePoint 2013 / 15: November 2013

Monday, 25 November 2013

Recently I have changed my SharePoint site Administrator password

Recently I have changed my SharePoint site Administrator password. After that whenever I try to create web application it is giving error that Administrator password is wrong.
In this post we will see a quick fix how to resolve this issue

Password Error

Following is the error which I am getting while creating a new web application

Fixing the problem

Update the farm credentials so that SharePoint will update the new password where ever required

stsadm -o updatefarmcredentials -userlogin <domain\username> -password <newpassword>

Add, Update and Delete list items using ECMAScript

Introduction

In this post we will see how to Add, Update and Delete SharePoint list items with ECMAScript (aka javascript client object model)

Add item to SharePoint list
Update item of SharePoint list
Delete item from SharePoint list

Add item to SharePoint list

To add an item to the list, use the ListItemCreationInformation object,set the properties using set_item, call the update and ExecuteQueryAsync methods

    function AddListItem(){

    var ListName = "MyList";

    var context = new SP.ClientContext.get_current(); // the current context is taken by default here

    //you can also create a particular site context as follows

    //var context = new SP.ClientContext('/Sites/site1');

    var lstObject = context.get_web().get_lists().getByTitle(ListName);

    var listItemCreationInfo = new SP.ListItemCreationInformation();

    var newItem = lstObject.addItem(listItemCreationInfo);

    newItem.set_item('Title', 'This is new item');

    // set values to other columns of the list here

    newItem.update();

    context.executeQueryAsync(Function.createDelegate(this, this.onSuccess),

        Function.createDelegate(this, this.onFailure));

     function onSuccess() {

        alert('Item created: ' + newItem.get_id());

    }

    function onFailure(sender, args) {

        alert('Request failed. ' + args.get_message() + '\n' + args.get_stackTrace());

    }

}

Update Item of SharePoint list

function UpdateListItem()

{

var ListName = "MyList";

var context = new SP.ClientContext.get_current(); // the current context is taken by default here

//you can also create a particular site context as follows

//var context = new SP.ClientContext('/Sites/site1');

var lstObject = context.get_web().get_lists().getByTitle(ListName);

this.lstObjectItem = lstObject.getItemById(1);

lstObjectItem.set_item('Title', 'This is updated item');

lstObjectItem.update();

lstObject.set_description("Updated description using ECMAScript");

lstObject.update();

context.executeQueryAsync(Function.createDelegate(this, this.onSuccess),

Function.createDelegate(this, this.onFailure));

}

function onSuccess() {

alert('Item udated');

}

function onFailure(sender, args) {

alert('Request failed. ' + args.get_message() + '\n' + args.get_stackTrace());

}

Delete Item from SharePoint list

function DeleteListItem()

{

var ListName = "MyList";

var context = new SP.ClientContext.get_current(); // the current context is taken by default here

//you can also create a particular site context as follows

//var context = new SP.ClientContext('/Sites/site1');

var lstObject = context.get_web().get_lists().getByTitle(ListName);

this.lstObjectItem = lstObject.getItemById(1);

lstObjectItem.deleteObject();

context.executeQueryAsync(Function.createDelegate(this, this.onSuccess),

Function.createDelegate(this, this.onFailure));

}

function onSuccess() {

alert('Item Deleted');

}

function onFailure(sender, args) {

alert('Request failed. ' + args.get_message() + '\n' + args.get_stackTrace());

}

Move Files of SharePoint Document Library using Object Model

Introduction

In this post we will see how to move files of SharePoint document library to one location to another using object model.
We will also see how to keep same file Version, Modified and Modified By values after moving
The post includes

Generic method to move file to destination
Keeping the file version, Modified and Modified By without any change.

Move file

string siteUrl = "http://sharepoint-devsite.com/DevSite";

string fileName = "ProjectPlan.docx";

string sourceDirectory = "/DevSite/Shared Documents";

string destinationDirectory  = "/DevSite/ProjectDocs/ProjTeam/DevTeam/TechLead";

using (SPSite currSite = new SPSite(siteUrl))

{

    using (SPWeb currWeb = currSite.OpenWeb())

    {

        MoveFile(currWeb, destinationDirectory, sourceDirectory, fileName);

    }

}

public void MoveFile(SPWeb sourceWeb, string sourceDirectory, string destinationDirectory, string fileName)

{

    SPFile sourcefile = sourceWeb.GetFile(sourceDirectory + "/" + fileName);

    if (sourcefile.Exists)

    {

        object modifiedOn = sourcefile.Item["Modified"];

        object modifiedBy = sourcefile.Item["Modified By"];

        //true - replace if file exists

        sourcefile.MoveTo(destinationDirectory + "/" + fileName, true);   

        SPFile dstFile = sourceWeb.GetFile(destinationDirectory + "/" + fileName);

        SPListItem dstItem = (SPListItem)dstFile.Item;

        dstItem.ParentList.Fields["Modified"].ReadOnlyField = false;

        dstItem.ParentList.Fields["Modified By"].ReadOnlyField = false;

        dstItem["Modified"] = modifiedOn;

        dstItem["Modified By"] = modifiedBy;

        //updates the item without creating another version of the item

        dstItem.UpdateOverwriteVersion();

        dstItem.ParentList.Fields["Modified"].ReadOnlyField = true;

        dstItem.ParentList.Fields["Modified By"].ReadOnlyField = true;

    }

}

MoveFile is the method which moves the file to destination without changing ‘Modified’ and ‘Modified By’ values.

Move Folders of SharePoint Document Library using object model

Introduction

SharePoint does not support moving folders directly but in this post we will see how we can achieve move folders of SharePoint document library to one location to another using object model.
We will also see how to keep same folder Version, Modified and Modified By values after moving
The post includes.

Moving folder along with subfolders from source to destination
Moving folder along with its items
Creation of folder
Deleting of folder

Skill Level – Medium

Move folder

Object model has MoveTo option on Folder object but that will not move the folder. From UI if we check Content and structure we will get move option on the file but
move option will be in disabled state on the folder.

Below code uses ‘MoveFolder’ method to move folder from source to destination. The method uses internally other methods to move all the subfolders and items.
Source folder ‘DevTeam’ is located in ‘Shared Documents’ Documents Libary
‘DevTeam’ folder should be moved to ‘ProjTeam’ folder under ‘ProjectDocs’ Documents Library. ‘ProjTeam’ is our destination folder.

string siteUrl = "http://sharepoint-devsite.com/DevSiteA";

string sourceDirectory = "/DevSiteA/Shared Documents/DevTeam";

string destinationDirectory = "/DevSiteA/ProjectDocs/ProjTeam";

using (SPSite currSite = new SPSite(siteUrl))

{

    using (SPWeb currWeb = currSite.OpenWeb())

    {

        MoveFolder(currWeb, sourceDirectory, destinationDirectory);

    }

}

//Move all folders and subfolder

public void MoveFolder(SPWeb sourceWeb, string sourceDirectory, string destinationDirectory)

{

    SPFolder srcFolder  = sourceWeb.GetFolder(sourceDirectory);

    if (srcFolder.Exists)

    {

        SPDocumentLibrary docLib = srcFolder.DocumentLibrary;

        SPFolderCollection oFolder = srcFolder.SubFolders;

        SPQuery oQuery = new SPQuery();

        oQuery.Query = "<Where><Eq><FieldRef Name='FSObjType'/><Value Type='Lookup'>1</Value></Eq></Where>";

        oQuery.Folder = oFolder.Folder;

        oQuery.ViewAttributes = "Scope='RecursiveAll'";

        SPListItemCollection collListItems = docLib.GetItems(oQuery);

        string newdestinationFolderPath = destinationDirectory;

        //Move the root folder with files

        MoveSingleFolder(sourceWeb, sourceDirectory, newdestinationFolderPath);

        newdestinationFolderPath = destinationDirectory + "/" + srcFolder.Name;

        //Move the subfolders with files

        foreach (SPListItem item in collListItems)

        {

            MoveSingleFolder(sourceWeb, item.Url, newdestinationFolderPath);

        }

        // Delete the root folder

        DeleteSourceFolder(sourceWeb, sourceDirectory);

    }

}

//Move single folder

private void MoveSingleFolder(SPWeb srcWeb, string sourceFolderPath, string destinationFolderPath)

{

    SPFolder srcFolder = srcWeb.GetFolder(sourceFolderPath);

    if (srcFolder.Exists)

    {

        string srcFolderName = srcFolder.Name;

        SPFolder dstFolder = srcWeb.GetFolder(destinationFolderPath);

        if (dstFolder.Exists)

        {

            //create the folder

            SPFolder newFolder = dstFolder.SubFolders.Add(srcFolderName);

                SPListItem newFolderItem = (SPListItem)newFolder.Item;

                newFolderItem.ParentList.Fields[SPBuiltInFieldId.Modified].ReadOnlyField = false;

                newFolderItem.ParentList.Fields[SPBuiltInFieldId.Modified_x0020_By].ReadOnlyField = false;

                newFolderItem[SPBuiltInFieldId.Modified] = srcFolder.Item["Modified"];

                newFolderItem["Modified By"] = srcFolder.Item["Modified By"];

                newFolderItem.UpdateOverwriteVersion();

                newFolderItem.ParentList.Fields[SPBuiltInFieldId.Modified].ReadOnlyField = true;

                newFolderItem.ParentList.Fields[SPBuiltInFieldId.Modified_x0020_By].ReadOnlyField = true;

        }

        MoveFolderItems(srcWeb, sourceFolderPath, destinationFolderPath + "/" + srcFolderName);

    }

}

//Move folder items

private void MoveFolderItems(SPWeb sourceWeb, string sourceFolderPath, string destinationFolderPath)

{

    SPFolder srcFolder = sourceWeb.GetFolder(sourceFolderPath);

    int fileCount = srcFolder.Files.Count;

    while (fileCount > 0)

    {

        SPFile sourceFile = sourceWeb.GetFile(srcFolder.Files[0].Url);

        object modifiedOn = sourceFile.Item["Modified"];

        object modifiedBy = sourceFile.Item["Modified By"];

        sourceFile.MoveTo(destinationFolderPath + "/" + sourceFile.Name, true);

        fileCount--;

        SPListItem dstItem = (SPListItem)sourceFile.Item;

        dstItem.ParentList.Fields["Modified"].ReadOnlyField = false;

        dstItem.ParentList.Fields["Modified By"].ReadOnlyField = false;

        dstItem["Modified"] = modifiedOn;

        dstItem["Modified By"] = modifiedBy;

        dstItem.UpdateOverwriteVersion(); //updates the item without creating another version of the item

        dstItem.ParentList.Fields["Modified"].ReadOnlyField = true;

        dstItem.ParentList.Fields["Modified By"].ReadOnlyField = true;

    }

}

//Delete the folder

private void DeleteSourceFolder(SPWeb srcWeb, string sourceFolderPath)

{

    SPFolder srcFolder = srcWeb.GetFolder(sourceFolderPath);

    if (srcFolder.Exists)

    {

        if (srcFolder.Files.Count == 0) //Delete only after moving

        {

            SPFolder srcRootFolder = srcFolder.ParentFolder;

            srcRootFolder.SubFolders.Delete(srcFolder.Url);

        }

    }

}

Move Folder creates folder, moves items to it. It will then creates all the subfolders and moves items to each subfolder from the source. After moving is done the source folder is deleted. Version along with ‘Modified’ and ‘Modified By’ values will be same as the source.

Before Moving

After Moving

Conclusion

Moving folders along with subfolders is a requirement which cannot be done directly from UI or from object model. Hope this code helps when required.

Create an Event Receiver for a Specific List Instance

The following steps show how to modify a list item event receiver to respond only to events that occur in a custom announcements-list instance.

To modify an event receiver to respond to a specific list instance

In a browser, open the SharePoint site.
In the navigation pane, Lists link.
In the All Site Content page, choose the Create link.
In the Create dialog box, choose the Announcements type, name the announcement TestAnnouncements, and then choose the Create button.
In Visual Studio, create an event receiver project.
In the What type of event receiver do you want? list, choose List Item Events.
You can also select any other kind of event receiver that scopes to a list definition, for example, List Email Events or List Workflow Events.
In the What item should be the event source? list, choose Announcements.
In the Handle the following events list, select the An item is being added check box, and then choose the Finish button.
In Solution Explorer, under EventReceiver1, open Elements.xml.
The event receiver currently references the Announcements list definition by using the following line:

The event receiver currently references the Announcements list definition by using the following line:

<Receivers ListTemplateId="104">

Change this line to the following text:

<Receivers ListUrl="Lists/TestAnnouncements">

This directs the event receiver to respond only to events that occur in the new TestAnnouncements announcements list that you just created. You can change the ListURL attribute to reference any list instance on the SharePoint server.
Open the code file for the event receiver and put a breakpoint in the ItemAdding method.
Choose the F5 key to build and run the solution.
In SharePoint, choose the TestAnnouncements link in the navigation pane.
Choose the Add new announcement link.
Enter a title for the announcement, and then choose the Save button.
Notice that the breakpoint is hit when the new item is added to the custom announcements list.
Choose the F5 key to resume.
In the navigation pane, choose the Lists link, and then choose the Announcements link.
Add a new announcement.
Notice that the event receiver does not trigger on the new announcement because the receiver is configured to respond only to events in the custom announcement list instance, TestAnnouncements.

SharePoint Event Handlers – Asynchronous Vs Synchronous

There is a little puzzlement among Asynchronousand Synchronous events, however I believe after reading this article, there will be no place for confusion in your brain, the reason for that I go behind a childlike practice to memorize what is Asynchronous ? and what is Synchronous ?

The same babyish method, I want to share with you.

A for Apple, A for Asynchronous and A for After events, so all Asynchronous events occur after the event, which does not stop the code to execute. All Asynchronous events end with ‘ed’ letters like SiteDeleted, FieldAdded, ItemAdded etc.

Now, let’s talk on the subject of Synchronous events, all Synchronous events occur before the event, which stop the code to execute. All Synchronous events end with ‘ing’ letters like SiteDeleting, FieldAdding, ItemAdding etc.

SPWebEventReceiver Asynchronous Events

SiteDeleted	Occurs after an existing site collection deleted.
WebDeleted	Occurs after an existing web site is completely deleted.
WebMoved	Occurs after an existing web site has been moved.

SPWebEventReceiver Synchronous Events

SiteDeleting	Occurs before an existing site collection is being deleted.
WebDeleting	Occurs before an existing web site is deleted.
WebMoving	Occurs before an existing web site has been renamed or moved

SPListEventReceiver Asynchronous Methods

FieldAdded	Occurs after a field link is added.
FieldDeleted	Occurs after a field has been removed from the list.
FieldUpdated	Occurs after a field link has been updated

SPListEventReceiver Synchronous Methods

FieldAdding	Occurs before a field link is added to a content type.
FieldDeleting	Occurs before a field is removed from the list.
FieldUpdating	Occurs before a field link is updated

SPItemEventReceiver Asynchronous Methods

ItemAdded	Occurs after a new item has been added
ItemAttachmentAdded	Occurs after an attachment added to an item.
ItemAttachmentDeleted	Occurs after an attachment removed from an item.
ItemCheckedOut	Occurs after an item is checked out.
ItemDeleted	Occurs after an item is completely deleted.
ItemFileMoved	Occurs after a file is moved.
ItemUpdated	Occurs after an item is modified/edited.

SPListItemEventReceiver Synchronous Methods

ItemAdding	Occurs before a new item is added.
ItemAttachmentAdding	Occurs before an attachment is added to an item.
ItemAttachmentDeleting	Occurs before an attachment when a user removed from an item.
ItemCheckingIn	Occurs before a file is checking-in.
ItemCheckingOut	Occurs before an item is checking-out.
ItemDeleting	Occurs before an item is completely deleted.
ItemFileMoving	Occurs before a file is moved.
ItemUncheckedOut	Occurs before an item is unchecked out.
ItemUncheckingOut	Before event that occurs when an item is being unchecked out.
ItemUpdating	Occurs before an existing item is modified/edited.

SharePoint Foundation 2010 New Events

Microsoft added several new events to SharePoint Foundation 2010 on Site, List and Item level. These fresh events are intended to meet up the requirements and for better elasticity.

SPWebEventReceiver

WebAdding	Occurs before a new web site is created.
WebProvisioned	Occurs after the web is provisioned.

WebAdding: event arises prior to a fresh web site is created, we can control the website to create or not to create by WebAdding event, then no SharePoint site is created and the provisioning process is not started.

WebProvisioned: event arise after the web is totally provisioned and process has stopped up. WebProvisioned can be configured to control in any synchronous or asynchronous methods.

If user wants to add few webparts to the newly provisioned web we can use this event to meet up the necessity

SPListEventReceiver

ListAdding	Occurs before a list is created.
ListAdded	Occurs after a list is created.
ListDeleting	Occurs before a list is deleted.
ListDeleted	Occurs after a list is deleted.

Reference:
http://msdn.microsoft.com/en-us/library/gg749858(v=office.14).aspx

Creating a simple Event Receiver in SharePoint 2013

Create an empty SharePoint 2013 project in Visual Studio 2012. In the project, select add new item and select Event Receiver

Select the type of event receiver you need to add, and select the events you need to handle.

Here, I have created the Department library to add and maintain documents and also created DocumentLog list to log the changes happening to the library.

In the list I have three columns, Title, Action & DateAndTime in order to catalog the changes happening to the library.

Back to the SharePoint project. Now go to the event receiver .cs file and you'll get a bunch of methods base on your selection during event receiver creation. Edit the code as below to implement the logic. Note that the ItemAdded method is used instead of the ItemAdding method.

public override void ItemAdded(SPItemEventProperties properties)
{
//base.ItemAdded(properties);
using (SPWeb web = properties.OpenWeb())
{
try
{
SPList list = web.Lists["DocumentLog"];
SPListItem newItem = list.Items.Add();
newItem["Title"] = properties.ListItem.Name;
newItem["DateAndTime"] = System.DateTime.Now;
newItem["Action"] = "Item Added";
newItem.Update();
}
catch (Exception ex)
{
throw ex;
}
}
}

public override void ItemUpdating(SPItemEventProperties properties)
{
//base.ItemUpdating(properties);
using (SPWeb web = properties.OpenWeb())
{
try
{
SPList list = web.Lists["DocumentLog"];
SPListItem newItem = list.Items.Add();
newItem["Title"] = properties.ListItem.Name;
newItem["DateAndTime"] = System.DateTime.Now;
newItem["Action"] = "Item Updated";
newItem.Update();
}
catch (Exception ex)
{
throw ex;
}
}
}

public override void ItemDeleting(SPItemEventProperties properties)
{
//base.ItemDeleting(properties);
using (SPWeb web = properties.OpenWeb())
{
try
{
SPList list = web.Lists["DocumentLog"];
SPListItem newItem = list.Items.Add();
newItem["Title"] = properties.ListItem.Name;
newItem["DateAndTime"] = System.DateTime.Now;
newItem["Action"] = "Item Deleted";
newItem.Update();
}
catch (Exception ex)
{
throw ex;
}
}
}

Thursday, 14 November 2013

'Login failed for user 'NT AUTHORITY\IUSR'

Message from ExternalSystem: ‘Login failed for user ‘NT AUTHORITY\IUSR’.’.

This error occurs because database does recognize the credentials passed from SharePoint. Which database? Database that you are connecting to in your external content type! It depends on you have setup application pool identity in SharePoint. If you are not using managed service account for your services, you are most likely to get this error. This is not likely to occur in corporate environments but in home or test environments where users use LOCAL SYSTEM OR NETWORK SERVICE in application pools, this error will occur. This is because NETWORKSERVICE translates to NTAUTHORITY\IUSR when credentials are passed from web server to database server. IUSR is used when user credentials are not available, for example, for anonymous users. To resolve this problem, either change application pool identity or add NT AUTHORITY\IUSR to the database permissions. The first scenario is quite common. You can change application pool identity by go to the web server and updating application pools or by logging into SharePoint central admin site and going to ManageService Accounts. We will cover second scenario here, that is, to add IUSR to the database.

1. Go to MicrosoftSQL Server Management Studio and connect to your database server.

2. Expand Security node and right-click Logins node and select New Login.

3. In the LoginName, enter IUSR and click Search…. This will open a new search box. Enter IUSR in the object name and click Check Names. Click OK.

4. You will notice that Login Name has been populated with MACHINENAME\IUSR where MACHINENAME is your machine name, for example, in the figure below, you see SP2013\IUSR. SP2013 is my machine name.

This is not what you want to add to the logins. Change MACHINENAME to NT AUTHORITY so Login Name should read NT AUTHORITY\IUSR. Click OK.

5. Now you may think that the user has been added and your external content type will work. Right? Wrong! You still have to map user to the database otherwise you will get following error on the list page(where you are trying to load external content type):

The query against the database caused an error.

This error occurs, as I said, because user is not mapped to the database yet.

6. To map user to the database, right-click NT AUTHORITY\IUSR in Logins and select Properties.

7. There are two ways to do this mapping. One way is to add user to one of the server roles, for example, serveradminor sysadmin. This will give user full rights to all databases and thus you won’t have to do explicit mapping. To do this, on the properties page, click ServerRoles and check sysadmin. Click OK. Obviously you would not want to do this in real environment. So the other option is to map the user directly to the database that has been used in the external content type.

To add user mapping, in LoginProperties, click User Mapping. Locate the database in the list and then check the box in the Map column. As soon as you check the box, NT AUTHORITY\IUSER appears in the User column. That’s it. Click OK to save the setting. By the way on the same properties page, you can also assign database role membership to the user for the database but that is not required.

Now, go back to the list page and reload it. You will see results from the external data source.