Category Archives: SharePoint Development

Sharepoint 2013 hosting – ASPHostPortal.com :: Solving Sharepoint cannot Login Problem by Using WAADby

Environment: SharePoint 2013, Windows Azure AD service as Identity Provider.

Issue: Cannot login to SharePoint Portal working and getting Session has timed out error. Steps to reproduce

Open SharePoint Portal
Portal navigates to Azure login page
After proving credentials, the page redirects to Azure login page

Cause: There is no SAMLResponse cookie available to validate the credentials and that is the reason why the login is failing. The FedAuth cookie that the SharePoint STS is setting before redirecting to SharePoint application is expiring. This is occurring because the cookie lifetime has exceeded the lifetime of the token issued by ACS, so it’s redirecting to get a new SAML token from ACS immediately.

The login page keeps looping because because the default LogonTokenCacheExpirationWindow for the SharePoint STS is 10 minutes. The relying party by default it sets the token lifetime in ADFS to be 2 minutes, so as soon as it authenticated it knew the cookie was good for less time than the LogonTokenCacheExpirationWindow value. Therefore it goes back to ADFS to authenticate again. And so it goes , back and forth. So I needed to change the LogonTokenCacheExpirationWindow to be less than the SAML TokenLifetime.

Findings: The first time that you navigate to a SharePoint Portal that is secured with SAML claims, it redirects you to get authenticated and get your claims. Your SAML identity provider, also known as identity provider security token service (IP-STS), does all that and then redirects you to SharePoint. When you come back into SharePoint, SharePoint creates a FedAuth cookie; that is how SharePoint knows that you have been authenticated. To make a smoother end-user experience, SharePoint writes the FedAuth cookie value to the local cookies folder. On subsequent requests for that site, if SharePoint finds a valid FedAuth cookie for the site, SharePoint reads the cookie and takes you directly to the SharePoint content, without reauthenticating.
The token lifetime is determined by the Relying Party Trust in ADFS, and is stamped with the local time of that server before being sent to SharePoint. SharePoint is in charge of determining when it feels that the token has expired (based on the LogonTokenCacheExpirationWindow property). Both of these properties can be changed but unless you have a very specific scenario, there is likely no need. Default values work fine.

Resolution: The default lifetime for the SharePoint Relying Party in ACS and the STS token cache lifetime is 10 minutes. You can increase the SAML token lifetime in ACS on the SharePoint Relying Party trust to something higher that 600 seconds (10 minutes) so that the FedAuth cookie cache is lower than the SAML token lifetime.

Cheap and Recommended SharePoint 2013 Hosting

ASPHostPortal.com is Perfect, suitable hosting plan for a starter in SharePoint. ASPHostPortal the leading provider of Windows hosting and affordable SharePoint Hosting. ASPHostPortal proudly working to help grow the backbone of the Internet, the millions of individuals, families, micro-businesses, small business, and fledgling online businesses. ASPHostPortal has ability to support the latest Microsoft and ASP.NET technology, such as: WebMatrix, WebDeploy, Visual Studio 2015, .NET 5/ASP.NET 4.5.2, ASP.NET MVC 6.0/5.2, Silverlight 6 and Visual Studio Lightswitch, ASPHostPortal guarantees the highest quality product, top security, and unshakeable reliability, carefully chose high-quality servers, networking, and infrastructure equipment to ensure the utmost reliability

Sharepoint 2013 Hosting – ASPHostPortal.com :: User Profile Property Cannot be Deleted in SharePoint 2013

If you run into the problem that you can’t delete properties within the User Profile Service Application, an Exception like this will be shown:

The delete operation failed, please try again later. If the problem persists, please contact your administrator.

To resolve the problem, grant “Full Control” permissions to the administrative Applicationpools group (WSS_WPG).

Now you should be able to delete properties again.

Cheap and Recommended SharePoint 2013 Hosting

SharePoint 2013 Hosting – ASPHostPortal.com :: How to Fix SharePoint 0x8004010F Error

Task ‘SharePoint‘ reported error (0x8004010F) : ‘The SharePoint List cannot be found. If the problem continues, contact the SharePoint site administrator. HTTP 404.

Issue: connected SharePoint Lists with the Outlook and we open the Outlook we see the error sometimes” Task ‘SharePoint’ reported error (0×80040102) : ‘Outlook cannot connect to the SharePoint List (site name – list name). The server may not be reachable from your location. Contact the SharePoint site administrator for more information. HTTP 0.

Cause: The issue could be of many reasons. find the below

1.   Could be the Lists is not connected properly with outlook
2.   Could be the list is removed
3.   make sure that all user accounts requesting have proper permissions

Solution: Ensure to check the following steps to resolve the issue.
If you no longer have to synchronize with the specific SharePoint list mentioned in the error, follow these steps to remove the SharePoint list from Outlook:

1.   Select Tools, and then click Account Settings.
2.   Click Account Settings, and then click SharePoint Lists.

3.   In the Account Settings dialog box, double-click the SharePoint list for which you received the error.
4.   Clear the check on Display this list on other computers with the account: and then click OK.
5.   Make sure that the SharePoint list for which you received the error is still selected, and then click Remove.
6.   Close the Account Settings dialog box

Cheap and Recommended SharePoint 2013 Hosting

SharePoint 2013 Hosting – ASPHostPortal.com :: How to Solve Cannot generate SSPI context in SharePoint

Today’s problem occured after I restarted a Hyper-V based SharePoint 2013 farm (Windows Server 2012, one SharePoint 2013 machine, one SQL Server 2012 machine, one DC). I fired up Central Administration and was hit with the following error:

Unknown SQL Exception 0 occurred. Additional error information from SQL Server is included below.

The target principal name is incorrect. Cannot generate SSPI context.

After checking the obvious things – testing connectivity to the DB server, checking the SQL service was running, verifying permissions, etc – I initially figured this was an issue with my Hyper-V snapshots being out of sync, so I ran the SharePoint Products Configuration Wizard. This hit me with the following error:

Failed to detect if this server is joined to a server farm. Possible reasons for this failure could be that you no longer have appropriate permissions to the server farm, the database server hosting the server farm is unresponsive, the configuration database is inaccessible or this server has been removed from the server farm.

I attempted to rejoin the server farm to no avail, then I realised I was barking up the wrong tree. The initial error message suggests a Kerberos issue, while my farm is set up to use NTLM. After a lot of searching, this ancient forum thread pointed me in the right direction. In Active Directory, I opened the computer record for the DB server. In the attribute list, the servicePrincipalName attribute showed the following entries:

Delete the two MSSQLSvc entries and then restart the database server. In most cases this should solve the problem. Without the SPNs, authentication falls back to NTLM as it should and the farm comes back to life.

Other users have reported that they also need to delete the RestrictedKrbHost entries. In a previous version of this post, I suggested deleting every entry – after all, if we’re using NTLM, we shouldn’t need any SPNs. However, if you delete all the entries you may find you have to remove and then re-add the database server to the domain.

I’m fairly certain that this issue arose when I added Analysis Services to the SQL Server instance on the database server. Other users have reported similar issues when adding Reporting Services and Integration Services to a SQL Server instance.

Cheap and Recommended SharePoint 2013 Hosting

ASPHostPortal.com
ASPHostPortal.com is Perfect, suitable hosting plan for a starter in SharePoint. ASPHostPortal the leading provider of Windows hosting and affordable SharePoint Hosting. ASPHostPortal proudly working to help grow the backbone of the Internet, the millions of individuals, families, micro-businesses, small business, and fledgling online businesses. ASPHostPortal has ability to support the latest Microsoft and ASP.NET technology, such as: WebMatrix, WebDeploy, Visual Studio 2015, .NET 5/ASP.NET 4.5.2, ASP.NET MVC 6.0/5.2, Silverlight 6 and Visual Studio Lightswitch, ASPHostPortal guarantees the highest quality product, top security, and unshakeable reliability, carefully chose high-quality servers, networking, and infrastructure equipment to ensure the utmost reliability

SharePoint 2013 Hosting – ASPHostPortal.com :: How to Fix SharePoint Cannot Show The Value of Filter

Multi-valued PeoplePicker Column that can be filtered using PowerShell

Recently I came across an error while filtering the multi-valued PeoplePicker column. The error reads “Cannot show the value of filter“. The field may not be filterable, or the number of items returned exceeds the list view threshold enforced by the administrator.” There are only four values in the column, surely it has no relation to the list view threshold value.

Internally, SharePoint server uses “_layouts/filter.aspx” application page for filter values which are presented in an iFrame. I checked the ULS logs and copied the Request URL with filter.aspx. I pasted it in browser and hit “Enter”. It returned no result.

What is multi-valued field?

The field which allows more than one values or which allows multiple selections. The multi-valued fileds are non-sortable, non-filterable. Multi-valued fields cannot be indexed.

How to Fix

This behavior can be overridden. Every field has an associated schema. Multi-valued fields are marked as “Sortable =false” in the schema for performance reasons. Note: Apply the workaround wherever it is unavoidable.

If we mark the multi-valued PeoplePicker as “Sortable=true”, the column turns filterable/ sortable. This can be achieved using SharePoint Server Object Model or using Windows PowerShell (I love it).

PowerShell Script to mark the column as Sortable:

$web=Get-SPWeb <weburl>
$list=$web.Lists[<list title>]
$field=$list.Fields[<field title>]
$strSchema=$field.SchemaXml
$str=Schema$strSchema.Replace(“Sortable=`”FALSE`””,”Sortable=`”true`””)
$field.SchemaXml = $strSchema

Update: I noticed that multi-valued “person or group” column in other web application was showing filter choices even though “Sortable=false”. Googling did not help. I checked at various levels and found that “Online Presence” setting causes this error. If Online presence setting is turned OFF, SP 2010 starts showing this error for multi-valued columns when tried to filter. So turn it ON, and no error, filter choices are shown back. The Online Presence setting is available in Web applications’s General Settings.

Cheap and Recommended SharePoint 2013 Hosting

FREE ASP.NET Hosting for SharePoint :: How to Solve Stuck Deploying status in SharePoint 2010

Signs :

Typically we will properly deploy/update a remedy deal (that is usually, a remedy having a gaggle of graphic world-wide-web parts) inside our SharePoint 2010 farm. We all deployed/updated the solution from the order “Update-SPSolution –Identity <SolutionName>. wsp –LiteralPath <Solution Location>\<SolutionName>. wsp –GACDeployment –force” inside the SharePoint 2010 Administration Shell. When we attempted for you to up-to-date the solution, many of us approved that it option wasn’t up-to-date. We all noticed that the deployment reputation inside the SharePoint 2010 Middle Government the Rank was generally “deploying”.

Trouble:

The problem can be related with one of the items bellow

Microsoft company SharePoint Groundwork Workflow Timer Assistance is just not managing
SharePoint Timer service is just not managing

Alternative:

To check on the execution on the service on the point 1:

Open the SharePoint Middle Government Portal
Go to Take care of services on server, underneath Program Settings
Authenticate in the event the service “Microsoft SharePoint Groundwork Workflow Timer Service” is usually managing. Or even, start it

To check on the execution on the service on the point 2:

Open the Glass windows Products and services window to confirm the services which might be managing inside the server
Find the “SharePoint 2010 Timer” service as well as examine if it is managing
In the event the service is just not managing, wide open the order range immediate
– Form the order “net start sptimerv4” to start out the service as well as click Type in
– If you receive “The service failed to start because of a logon inability. ”, edit the “Log On” account to make sure that the service identity account is usually put together effectively you need to the service

Immediately after making sure every one of the services are generally managing, release again the service.

Best Recommended SharePoint 2013 Hosting

ASPHostPortal.com is Perfect, suitable hosting plan for a starter in SharePoint. ASPHostPortal the leading provider of Windows hosting and affordable SharePoint Hosting. ASPHostPortal proudly working to help grow the backbone of the Internet, the millions of individuals, families, micro-businesses, small business, and fledgling online businesses. ASPHostPortal has ability to support the latest Microsoft and ASP.NET technology, such as: WebMatrix, WebDeploy, Visual Studio 2015, .NET 5/ASP.NET 4.5.2, ASP.NET MVC 6.0/5.2, Silverlight 6 and Visual Studio Lightswitch, ASPHostPortal guarantees the highest quality product, top security, and unshakeable reliability, carefully chose high-quality servers, networking, and infrastructure equipment to ensure the utmost reliability

SharePoint 2013 Hosting with ASPHostPortal :: Configures the Application Server and Web Server

The pre-requisites installation in one of my recent SharePoint 2013 farm installations was failing at the step where it configures the Application Server and Web Server role for the Server:

Further, the error logs had the following entry:

Request for install time of Application Server Role, Web Server (IIS) Role
Install process returned (0)
[In HRESULT format] (0)
“C:\Windows\system32\cscript.exe” “C:\Windows\system32\iisext.vbs” /enext “ASP.NET v4.5.30319″
Request for install time of Application Server Role, Web Server (IIS) Role – Install process returned (1)
[In HRESULT format] (-2147024895)
Error when enabling ASP.NET v4.5.30319 – Last return code

Since I did not find much community guidance around this, I thought I’ll do some research myself and post the solution for other’s benefit as well. A little bit of digging around revealed that the IISExt.vbs script file was indeed missing from the C:\Windows\System32 folder. Further research revealed that the script is part of the IIS 8.0 scripting tools. The solution therefore is as simple as enabling the IIS 8.0 Scripting Tools through the Server Roles and Features Wizard. The path to the IIS 8.0 Scripting Tools is shown in the following screen capture:

That’s it. Your pre-requisites installation should proceed as intended after you install these tools… Good Luck with your install!

SharePoint 2013 Hosting with ASPHostPortal.com :: How to Access SharePoint Data from Provider-Hosted Apps Use the Right Context

Recently I have focused on building apps that access, manipulate, and interact with data stored in SharePoint Online with Office 365. If you have done any development using the client-side object model (CSOM) for SharePoint, you understand the importance of instantiating the proper ClientContext object to access data in a particular SharePoint site. The ClientContext constructor takes as an argument the URL of a SharePoint site and allows you to access data stored in the Lists collection of the Web associated with it. In this post, I will discuss the various context objects you should use in your provider-hosted app depending on where the data your app needs to access resides and if the user’s permissions need to be considered. If you have been developing apps for SharePoint for awhile now (and even if you haven’t), I strongly encourage you to use Visual Studio 2013 and the Office Developer Tools for Visual Studio 2013

Host webs and app webs

When dealing with apps for SharePoint, you will become familiar with host webs and app webs:

Host web – the SharePoint site to which an app is installed
App web – the special isolated site (a unique app web is provisioned for each installation of the app) where the app for SharePoint’s internal components and content, such as lists, content types, workflows, and pages, are deployed

Note that a provider-hosted app is not required to have an app web, and in fact may not need one depending on your business requirements.

Your app will always have Full Control permissions to its app web. However, your app will need to request (and be granted) permissions by the user installing your app in order to access data in the host web. This is handled through the app manifest.
If your app needs to access data in the SharePoint site where it is being installed, you will be working with a host web context of some sort. As you will see, there are actually two different host web context objects, depending on the app authorization policy you choose.
Life made easy, thanks to SharePointContext.cs

When you create a new provider-hosted app in Visual Studio 2013, you have the option to create a new ASP.NET Web Forms or MVC application to serve as your app’s remote web application. If you are using the Office Developer Tools for Visual Studio 2013, you also have the option to convert an existing ASP.NET web application to an app for SharePoint project (really cool!) In either case, you will notice that SharePointContext.cs is added to the remote web application project. This file contains class definitions forSharePointAcsContext and SharePointHighTrustContext, which allow you to create host web and app web context objects based on whether your trust broker is ACS (which it is with Office 365) .
Accessing data in the app web
To access data in the SharePoint app web from your app, use the following pattern:

CSOM (C#)

var spContext = SharePointContextProvider.Current.GetSharePointContext(Context);using (var clientContext = spContext.CreateUserClientContextForSPAppWeb()){Web web = clientContext.Web;

clientContext.Load(web);

clientContext.ExecuteQuery();

ListCollection lists = web.Lists;

clientContext.Load<ListCollection>(lists);

clientContext.ExecuteQuery();

}

REST (C#)

var spContext = SharePointContextProvider.Current.GetSharePointContext(Context);HttpWebRequest listRequest = (HttpWebRequest)HttpWebRequest.Create(spContext.SPAppWebUrl + “/_api/web/lists”);listRequest.Method = “GET”;listRequest.Accept = “application/atom+xml”;

listRequest.ContentType = “application/atom+xml;type=entry”;

listRequest.Headers.Add(“Authorization”, “Bearer ” + spContext.UserAccessTokenForSPAppWeb);

JSOM

var appweburl = decodeURIComponent(getQueryStringParameter(“SPAppWebUrl”));var clientContext = new SP.ClientContext(appweburl);var appWeb = clientContext.get_web();var appWebListColl = appWeb.get_lists();

clientContext.load(appWebListColl);

clientContext.executeQueryAsync(onAppWebGetListSuccess, onError);

Accessing data in the host web

To access data in the SharePoint host web (the SharePoint site where your app is installed) from your app, use the following pattern:

CSOM (C#)

var spContext = SharePointContextProvider.Current.GetSharePointContext(Context);using (var clientContext = spContext.CreateUserClientContextForSPHost()){Web web = clientContext.Web;

clientContext.Load(web);

clientContext.ExecuteQuery();

ListCollection lists = web.Lists;

clientContext.Load<ListCollection>(lists);

clientContext.ExecuteQuery();

}

REST (C#)

listRequest.ContentType = “application/atom+xml;type=entry”;

listRequest.Headers.Add(“Authorization”, “Bearer ” + spContext.UserAccessTokenForSPHost);

JSOM

var appweburl = decodeURIComponent(getQueryStringParameter(“SPAppWebUrl”));var hostweburl = decodeURIComponent(getQueryStringParameter(“SPHostUrl”));var clientContext = new SP.ClientContext(appweburl);var factory = new SP.ProxyWebRequestExecutorFactory(appweburl);

clientContext.set_webRequestExecutorFactory(factory);

var appContextSite = new SP.AppContextSite(clientContext, hostweburl);

var hostWeb = appContextSite.get_web();

hostWebListColl = hostWeb.get_lists();

clientContext.load(hostWebListColl);

clientContext.executeQueryAsync(onHostWebGetListSuccess, onJSOMError);

Note that using JSOM, we still need to construct a ClientContext for the app web before we generate an AppContextSite for the host web, made possible through theSP.ProxyWebRequestExecutorFactory.

A note about the app-only authorization policy

By default, authorization checks in the host web succeed only if both the current user and the app have sufficient permissions to perform the action in question, such as reading from or writing to a list. We are reminded that the user’s permissions are taken into account based on the names of the context and access token objects we use in these scenarios: for instance, CreateUserClientContextForSPHost and UserAccessTokenForSPHost. However, your app has the ability to do something akin to running with elevated privileges using the app-only policyfor authorization. Also controlled through the app manifest, the app-only policy is useful when an app doesn’t need or want to consider the permissions of the current user. In Visual Studio 2013, you can specify that your app would like to have the ability to use the app-only policy by checking this box in the AppManifest.xml editor.
That being said, just because your app is granted this permission does not mean that you can use the same host web context or access token as before to automatically leverage it. To access data from the SharePoint host web (taking only your app’s permissions into account and ignoring the current user’s permissions) from your app, use the following pattern:

CSOM (C#)

var spContext = SharePointContextProvider.Current.GetSharePointContext(Context);using (var clientContext = spContext.CreateAppOnlyClientContextForSPHost()){Web web = clientContext.Web;

clientContext.Load(web);

clientContext.ExecuteQuery();

ListCollection lists = web.Lists;

clientContext.Load<ListCollection>(lists);

clientContext.ExecuteQuery();

}

REST (C#)

listRequest.ContentType = “application/atom+xml;type=entry”;

listRequest.Headers.Add(“Authorization”, “Bearer ” + spContext.AppOnlyAccessTokenForSPHost);

Remember that in order to use the app-only policy, your app must request and be granted this permission by the site owner who installs your app. Also note that there is no JSOM example using the app-only policy because apps that do not make OAuth authenticated calls (such as apps that are only JavaScript running in the app web) cannot use the app-only policy.
As you can see, the code you write in each of the above scenarios (accessing data in the app web, host web, or using the app-only authorization policy) is identical except for the method or property you use from the SharePointContext class to get the appropriate context or access token. Understanding these subtle differences is vitally important when making sure your app has the ability to access and manipulate the SharePoint data it needs.

SharePoint 2013 Hosting With ASPHostPortal.com :: Tips How to Creating a SharePoint development environment

SharePoint 2013 Development Environment

Creating a SharePoint development environment is a task that can be challenging because the aim is to produce a usable environment, often on resource-constrained hardware. Keep in mind that no amount of tweaking will yield a satisfactory result unless your machine meets the minimum requirements for SharePoint 2013. Here are some tips to keep your dev box humming along nicely:

Memory – use as much of it as you can. 8 GB is the absolute minimum and even this amount may cause you some problems. If SQL Server starts paging to disk you’ll get no work done.
When using a hypervisor such as Hyper-V make sure you allocate more than 1 CPU core to your SharePoint VM.
Set a maximum server memory limit in SQL Server.
Don’t create a search service application unless you need one. Those noderunner.exe processes will gobble up lots of memory. You can limit the memory usage by editing the noderunner.exe.config file located in C:\Program Files\Microsoft Office Servers\15.0\Search\Runtime\1.0. Look for the memoryLimitMegabytes attribute.
If you have a search service application disable continuous crawling and don’t set any crawl schedules. Crawl your content when you need to.
Use Set-SPEnterpriseSearchService -PerformanceLevel Reduced to reduce the CPU impact the search service has on your dev environment.
Pause the search service application if you’re not using it.
Keep the number of web applications to a minimum. Lots of IIS application pools means increased memory usage.
Configure an agressive diagnostic log storage limit. You probably won’t need days or weeks of trace log history at your fingertips.
Set the recovery model of your SharePoint databases to Simple. This will eliminate the need for a SQL maintenance plan. Many developers overlook SQL log file rotation until their dev machine runs out of storage.
Disable usage data collection (unless you need it).
Don’t use your regular domain account to run SharePoint services and don’t make it a local administrator of your development box. Develop and test using different user accounts.
Keep in mind that these tips are designed to make your personal development environment responsive and easy to work with. A production SharePoint environment would not need these changes as it should be properly resourced and managed.

SharePoint 2013 Hosting with ASPHostPortal :: Scenario pages for SharePoint 2013

SharePoint 2013 has many great ways to help you get things done. We want to highlight a few of these, so we have created scenario pages that explain a specific scenario and provide content to help you understand, implement, and use it easily.

Scenario pages allow you to view key resources based on selected stages of evaluation or adoption. These stages are represented by colored tiles. Click a single tile for a specific stage or Ctrl-click multiple tiles for multiple stages. As you click the tiles, the scenario page lists the resources for each selected stage.

Content and resources are drawn from many Microsoft Web properties: IT content from TechNet, developer content from MSDN, and Information Worker content from Office.com are all integrated into the scenario page experience. All of the resources you need are available in one place, whether you want to understand:

Which features must be configured to support the scenario and how to manage them
What namespaces and methods to use to develop customizations for the scenario (MSDN content) Or how to accomplish a specific task in the scenario (Office content)

The following scenario pages are now available:

eDiscovery in SharePoint Server 2013 and Exchange Server 2013 . eDiscovery allows you to place electronic holds on documents and email for a legal case or audit. eDiscovery is a great example of a solution that benefits from a scenario page because it provides links to key resources published for SharePoint 2013, Exchange Server 2013, and Lync Server 2013.

Personal sites (My Sites) in SharePoint Server 2013 . My Sites technology provides profile data, activity feeds, tagging capabilities, and search results for each SharePoint user in your organization.

When you deploy My Sites, each user gets a starting place in SharePoint that brings together the sites, documents, and other information that they care about and helps them share what they know.

Best and Affordable SharePoint Hosting with ASPHostPortal.com

Everything about SharePoint Hosting, SharePoint Tips Tutorial and SharePoint for Business

Category Archives: SharePoint Development

Sharepoint 2013 hosting – ASPHostPortal.com :: Solving Sharepoint cannot Login Problem by Using WAADby

Cheap and Recommended SharePoint 2013 Hosting

Sharepoint 2013 Hosting – ASPHostPortal.com :: User Profile Property Cannot be Deleted in SharePoint 2013

Cheap and Recommended SharePoint 2013 Hosting

SharePoint 2013 Hosting – ASPHostPortal.com :: How to Fix SharePoint 0x8004010F Error

Cheap and Recommended SharePoint 2013 Hosting

SharePoint 2013 Hosting – ASPHostPortal.com :: How to Solve Cannot generate SSPI context in SharePoint

Cheap and Recommended SharePoint 2013 Hosting

SharePoint 2013 Hosting – ASPHostPortal.com :: How to Fix SharePoint Cannot Show The Value of Filter

Multi-valued PeoplePicker Column that can be filtered using PowerShell

What is multi-valued field?

How to Fix

Cheap and Recommended SharePoint 2013 Hosting

FREE ASP.NET Hosting for SharePoint :: How to Solve Stuck Deploying status in SharePoint 2010

Signs :

Trouble:

Alternative:

Best Recommended SharePoint 2013 Hosting

SharePoint 2013 Hosting with ASPHostPortal :: Configures the Application Server and Web Server

SharePoint 2013 Hosting with ASPHostPortal.com :: How to Access SharePoint Data from Provider-Hosted Apps Use the Right Context

Host webs and app webs

Accessing data in the host web

A note about the app-only authorization policy

SharePoint 2013 Hosting With ASPHostPortal.com :: Tips How to Creating a SharePoint development environment

SharePoint 2013 Development Environment

SharePoint 2013 Hosting with ASPHostPortal :: Scenario pages for SharePoint 2013