Posts tagged trick SharePoint 2013 Hosting

SharePoint 2013 Hosting – HostForLIFE.eu :: Wildcard Search Of Users Using CSOM In SharePoint

Dec 13th

Posted by Peter in European SharePoint Server 2013 Hosting

In this blog, I will explain how to find users using ClientPeoplePickerSearchUser class. There are many ways in CSOM to get the users from SharePoint site or the web but I could not find any proper way to perform a wildcard search of users from SharePoint site using CSOM. For example, let’s say I want to find all the users present in the site collection where the first name starts with “John” or the last name starts with “Patt”.

This below-mentioned code sample will help us to perform both wildcard and explicit search. The output will be matching the result whether it is a collection of users or a single user.

The script for this is given below.

using Microsoft.SharePoint.Client;  
using System;  
using System.Collections.Generic;  
using System.Linq;  
using System.Security;  
using System.Text;  
using System.Threading.Tasks;  
namespace FindUserDetailsByPeoplepickerQuery {  
    class Program {  
        static void Main(string[] args) {  
            string userToFind = "userToFind"; //it may be full or partial name of the user  
            string webUrl = "<site url>";  
            string userName = "<user name>";  
            string password = "<password>";  
            SecureString passWord = new SecureString();  
            try {  
                //creating the context of the SharePoint site  
                using(ClientContext clientCtx = new ClientContext(webUrl)) {  
                    foreach(char c in password.ToCharArray())  
                    passWord.AppendChar(c);  
                    clientCtx.Credentials = new SharePointOnlineCredentials(userName, passWord);  
                    clientCtx.ExecuteQuery();  
                    //preparing the search query options  
                    Microsoft.SharePoint.ApplicationPages.ClientPickerQuery.ClientPeoplePickerQueryParameters peoplePickerQuery = new Microsoft.SharePoint.ApplicationPages.ClientPickerQuery.ClientPeoplePickerQueryParameters();  
                    peoplePickerQuery.AllowEmailAddresses = true;  
                    peoplePickerQuery.AllowMultipleEntities = false;  
                    peoplePickerQuery.ForceClaims = false;  
                    peoplePickerQuery.MaximumEntitySuggestions = 60;  
                    peoplePickerQuery.PrincipalType = Microsoft.SharePoint.Client.Utilities.PrincipalType.All;  
                    peoplePickerQuery.PrincipalSource = Microsoft.SharePoint.Client.Utilities.PrincipalSource.All;  
                    peoplePickerQuery.QueryString = userToFind;  
                    peoplePickerQuery.AllUrlZones = true;  
                    peoplePickerQuery.SharePointGroupID = 0;  
                    peoplePickerQuery.WebApplicationID = new Guid("00000000-0000-0000-0000-000000000000");  
                    //Using peoplepicker webservice and searchquery getting the matched userInformations from SharePoint  
                    ClientResult < String > resultData = Microsoft.SharePoint.ApplicationPages.ClientPickerQuery.ClientPeoplePickerWebServiceInterface.ClientPeoplePickerSearchUser(clientCtx, peoplePickerQuery);  
                    clientCtx.ExecuteQuery();  
                    if (resultData != null) {  
                        Object[] queryMatchesFound = (Object[]) clientCtx.ParseObjectFromJsonString(resultData.Value);  
                        for (var i = 0; i < queryMatchesFound.Length; i++) {  
                            try {  
                                Dictionary < string, object > obj = (Dictionary < string, object > ) queryMatchesFound[i];  
                                try {  
                                    string loginName = obj["Key"].ToString();  
                                } catch {} //this will give the loginName of the user  
                                try {  
                                    string email = obj["Description"].ToString();  
                                } catch {} //this will give the email of the user  
                                try {  
                                    string Title = obj["DisplayText"].ToString();  
                                } catch {} //this will give the title/DisplayName of the user  
                                try {  
                                    string entityType = obj["EntityType"].ToString();  
                                } catch {} //this will give the type of the object whether it is a group or user  
                            } catch {}  
                        }  
                    }  
                }  
            } catch {}  
        }  
    }  
}

using Microsoft.SharePoint.Client;

using System;

using System.Collections.Generic;

using System.Linq;

using System.Security;

using System.Text;

using System.Threading.Tasks;

namespace FindUserDetailsByPeoplepickerQuery {

class Program {

static void Main(string[] args) {

string userToFind = "userToFind"; //it may be full or partial name of the user

string webUrl = "<site url>";

string userName = "<user name>";

string password = "<password>";

SecureString passWord = new SecureString();

try {

//creating the context of the SharePoint site

using(ClientContext clientCtx = new ClientContext(webUrl)) {

foreach(char c in password.ToCharArray())

passWord.AppendChar(c);

clientCtx.Credentials = new SharePointOnlineCredentials(userName, passWord);

clientCtx.ExecuteQuery();

//preparing the search query options

Microsoft.SharePoint.ApplicationPages.ClientPickerQuery.ClientPeoplePickerQueryParameters peoplePickerQuery = new Microsoft.SharePoint.ApplicationPages.ClientPickerQuery.ClientPeoplePickerQueryParameters();

peoplePickerQuery.AllowEmailAddresses = true;

peoplePickerQuery.AllowMultipleEntities = false;

peoplePickerQuery.ForceClaims = false;

peoplePickerQuery.MaximumEntitySuggestions = 60;

peoplePickerQuery.PrincipalType = Microsoft.SharePoint.Client.Utilities.PrincipalType.All;

peoplePickerQuery.PrincipalSource = Microsoft.SharePoint.Client.Utilities.PrincipalSource.All;

peoplePickerQuery.QueryString = userToFind;

peoplePickerQuery.AllUrlZones = true;

peoplePickerQuery.SharePointGroupID = 0;

peoplePickerQuery.WebApplicationID = new Guid("00000000-0000-0000-0000-000000000000");

//Using peoplepicker webservice and searchquery getting the matched userInformations from SharePoint

ClientResult < String > resultData = Microsoft.SharePoint.ApplicationPages.ClientPickerQuery.ClientPeoplePickerWebServiceInterface.ClientPeoplePickerSearchUser(clientCtx, peoplePickerQuery);

clientCtx.ExecuteQuery();

if (resultData != null) {

Object[] queryMatchesFound = (Object[]) clientCtx.ParseObjectFromJsonString(resultData.Value);

for (var i = 0; i < queryMatchesFound.Length; i++) {

try {

Dictionary < string, object > obj = (Dictionary < string, object > ) queryMatchesFound[i];

try {

string loginName = obj["Key"].ToString();

} catch {} //this will give the loginName of the user

try {

string email = obj["Description"].ToString();

} catch {} //this will give the email of the user

try {

string Title = obj["DisplayText"].ToString();

} catch {} //this will give the title/DisplayName of the user

try {

string entityType = obj["EntityType"].ToString();

} catch {} //this will give the type of the object whether it is a group or user

} catch {}

}

} catch {}

}

In this example, I am getting the values in a JSON String format. Then, I am converting it into an object and by looping the collection, we can get the required information of the users like loginname, displayname, email etc.

Conclusion

In this blog, I have explained how you can get multiple users based on wildcard search. I hope this information will help you out in a few scenarios.

SharePoint 2013 Hosting Recommendation

HostForLIFE.eu’s SharePoint 2013 Hosting solution offers a comprehensive feature set that is easy-to-use for new users, yet powerful enough for the most demanding web developer expert. Hosted SharePoint Foundation 2013 is the premiere web-based collaboration and productivity enhancement tool on the market today. With SharePoint 2013 Foundation, you can quickly access and manage documents and information anytime, anywhere though a Web browser in a secure and user friendly way. SharePoint hosting services start at only at €9.99/mo, allowing you to take advantage of the robust feature set for a small business price. HostForLIFE.eu offers a variety of hosted SharePoint Foundation 2013 plans as well as dedicated SharePoint 2013 Foundation options

Sharegate Tips And Tricks For Migration To SharePoint

Dec 7th

Posted by Peter in European SharePoint 2013 Hosting

No comments

There are numerous third party tools available in the market to migrate the content from SharePoint OnPremise to SharePoint Online. Sharegate is one of the most widely used migration tools. In this article, we will discuss the tips and tricks that can be useful to carry out smoother migration and avoid any common mistakes.

Sharegate Migration Overview

From a SharePoint perspective, Sharegate supports two types of migration.

Copy Structure
This option helps to copy the site collections, sites, lists, libraries, permission and more directly from SharePoint (any version) to SharePoint (any version).
This option is useful when we want to migrate the site from source to target environment as it is without any change in data or location.
Copy Content
Copy content is a more granular way of migrating the content to the target environment. It helps to copy documents, list items, folders, and document sets from SharePoint (any version) to SharePoint (any version).
This option is useful when we want to migrate individual content (like document, list item) selectively from source to target environment.

Copying Document Libraries

Tip# 1: Missing Documents

This point is not specific to Sharegate but as a general perspective of SharePoint users. Even though after successful migration of documents, the number of documents appears less in the target location.

The major reason for this is SharePoint users who do not check-in any version of their files. Follow the below steps to avoid these kinds of situations,

Open Document library in SharePoint source environment.
Click Library Settings.
Under “Permissions and Management”, click “Manage files which have no checked in version”.
Select the listed documents.
Click “Take ownership of selection”.
Switch back to Sharegate, refresh the view.
The missing documents should be now available to migrate.

Tip#2 – Insane mode for a document copy

It is always preferable to use the insane mode to copy documents faster to source SharePoint environment. Here, we can also specify the custom storage account to use. Also, the insane mode will help to maintain the IDs of items from the source environment.

Migration of Choice Fields

In SharePoint, we commonly use Choice fields as part of our information architecture. The major issue with using choice field is that it does not keep track of changed values.

As an example, if we create a choice field called Status with below values to start with,

Draft
Approved
Rejected

Over time, we realize that we need to drill down more into the business process and need more choices to support our business scenarios. We then change the choice values as below,

Draft
Approved by Manager
Approved by HR
Approved by all
Rejected

Notice how the Approved status is broken down to support the business process. In this scenario, the items in the list which were created before with Status as Approved remain as they were. SharePoint does not complain about it. But when it comes to migration as we are no longer supporting “Approved” status, the items tagged with the “Approved” status start to complain. At this point, it might not be feasible to go back and change all approval statuses.

A simple resolution to this is to set the problematic choice column to allow fill-in choices.

This will allow Sharegate to enter any value in the choice column and proceed with the migration.

Version Mismatch or missing versions of documents

When any document has huge versions, it might occur that a few versions go missing. Sharegate simply skips the versions. To resolve this kind of issue, simply re-migrate the document with any of the below options.

Copy and Replace
Copy if newer (incremental)

Lookup Lists

Lists which have lookup are always troublesome to migrate. Firstly identify and start from parent list to avoid any reworking of migration.

Another solution is to set the default value in Sharegate to use when the source item contains an invalid value for the destination lookup column.

Support from Sharegate

Sharegate provides the best support to resolve our migration issues. For any outstanding issues, we can email support@sharegate.com and their representative will help us further.

Summary

Sharegate is one of the best migration tools available in the market. We cannot consider the migration will be always as easy as lifting and shifting the content. We may face few challenges due to data inconsistency. The above tips and tricks will definitely help to tackle common behaviors.

SharePoint 2013 Hosting Recommendation

SharePoint 2013 Hosting – HostForLIFE.eu :: Fetching All Attachments From A List Using SharePoint Framework WebPart

Dec 6th

Posted by Peter in European SharePoint 2013 Hosting

No comments

Often, in forums and SharePoint events, I receive a query on how to get all the attachments from all items in a SharePoint List. We can achieve this in several different ways as mentioned below.

Accessing the attachments folder from the SharePoint List using SharePoint Designer
Mapping the attachments folder to File Share.
Accessing the attachment folder of the list based on the path using a program
Get the attachments of each list item in a list using a program

Here, we are going to follow the last method for accessing the attachments in a list using PnP JavaScript library and render that in SharePoint Framework webpart.

First of all, create a SharePoint Framework webpart project using the Yeoman generator with the following command.

PS> yo @microsoft/sharepoint

1	PS> yo @microsoft/sharepoint

Generate the project with No JavaScript option, because I am going to show the example without any JavaScript framework so that, you can use the snippet of any JavaScript framework on creating the webpart.

After the creation of the project, add the PnP JS library dependencies by running the following npm commmand.

PS> npm install –save @pnp/common @pnp/sp @pnp/logging @pnp/odata

1	PS> npm install –save @pnp/common @pnp/sp @pnp/logging @pnp/odata

To access the item and attachment objects using PnP library, add the following import statements to the webpart’s TypeScript file.

import { sp, Item } from "@pnp/sp";

1	import { sp, Item } from "@pnp/sp";

If we want to download or upload the attachment files from the webpart, we have to include the following import statement below the sp import statement.

import { AttachmentFile, AttachmentFiles, AttachmentFileInfo } from '@pnp/sp/src/attachmentfiles';

1	import { AttachmentFile, AttachmentFiles, AttachmentFileInfo } from '@pnp/sp/src/attachmentfiles';

To show the attachments from all list items in a webpart, add the below methods under the _WebPart class within the _webpart.ts file.

//Retrieve all the attachments from all items in a SharePoint List  
  private getSPData(): void {  
    let attachmentfiles: string = "";  
   
    sp.web.lists.getByTitle("My List").items  
    .select("Id,Title,Attachments,AttachmentFiles")  
    .expand("AttachmentFiles")  
    .filter('Attachments eq 1')  
    .get().then((response: Item[]) => {  
       
      response.forEach((listItem: any) => {  
        listItem.AttachmentFiles.forEach((afile: any) => {  
          attachmentfiles += `<li>(${listItem.Id}) ${listItem.Title} - ${afile.FileName}</li>`;  
        });  
   
      });      
      attachmentfiles = `<ul>${attachmentfiles}</ul>`;;  
      this.renderData(attachmentfiles);  
    });  
  }  
private renderData(strResponse: string): void {  
  const htmlElement = this.domElement.querySelector("#pnpinfo");  
  htmlElement.innerHTML = strResponse;  
}

//Retrieve all the attachments from all items in a SharePoint List

private getSPData(): void {

let attachmentfiles: string = "";

sp.web.lists.getByTitle("My List").items

.select("Id,Title,Attachments,AttachmentFiles")

.expand("AttachmentFiles")

.filter('Attachments eq 1')

.get().then((response: Item[]) => {

response.forEach((listItem: any) => {

listItem.AttachmentFiles.forEach((afile: any) => {

attachmentfiles += `<li>(${listItem.Id}) ${listItem.Title} - ${afile.FileName}</li>`;

});

attachmentfiles = `<ul>${attachmentfiles}</ul>`;;

this.renderData(attachmentfiles);

});

}

private renderData(strResponse: string): void {

const htmlElement = this.domElement.querySelector("#pnpinfo");

htmlElement.innerHTML = strResponse;

}

The getSPData() method gets the attachment files from all items from the list “My List“. Add the “Attachments eq 1” to the filter to retrieve the items which contain attachments. Use the expand method to get the attachment files of the list items in a single request.
In response, we are generating the HTML as a list of attachment files with the associated Item Id and Title. The renderData() method adds the generated HTML to the webpart.Replace the render() method with the below code snippet. This is used to call the getSPData() and update the retrieved values within the element pnpinfo.

public render(): void {  
  this.domElement.innerHTML = `  
    <div class="${ styles.pnPDemos}">  
      <div class="${ styles.container}">  
        <div class="${ styles.row}">  
          <div class="${ styles.column}">  
            <div id="pnpinfo"></div>  
          </div>  
        </div>  
      </div>  
    </div>`;  
  this.getSPData();  
}

public render(): void {

this.domElement.innerHTML = `

</div>

</div>`;

this.getSPData();

}

After running the webpart in the SharePoint page, it will display the Item id, title, and attachments. It will be nice to have a download link in the attachment file.

attachmentfiles += `<li>(${listItem.Id}) ${listItem.Title} - ${afile.FileName}</li>`;

1	attachmentfiles += `<li>(${listItem.Id}) ${listItem.Title} - ${afile.FileName}</li>`;

Replace the above line with the following code snippet. Then, the webpart renders the download link of each attachment file.

let downloadUrl = this.context.pageContext.web.absoluteUrl + "/_layouts/download.aspx?sourceurl=" + afile.ServerRelativeUrl;  

attachmentfiles += `<li>(${listItem.Id}) ${listItem.Title} - <a href='${downloadUrl}'>${afile.FileName}</a></li>`;

let downloadUrl = this.context.pageContext.web.absoluteUrl + "/_layouts/download.aspx?sourceurl=" + afile.ServerRelativeUrl;

attachmentfiles += `<li>(${listItem.Id}) ${listItem.Title} - <a href='${downloadUrl}'>${afile.FileName}</a></li>`;

SharePoint 2013 Hosting Recommendation

SharePoint 2013 Hosting – HostForLIFE.eu :: Get Current User Information Using PnP Library In SharePoint Framework

Nov 22nd

Posted by Peter in European SharePoint 2013 Hosting

No comments

PnP JavaScript library contains a lot of methods and properties for accessing SharePoint Data. We will see how to use this library in SharePoint Framework to get the current user information. Use the below command to create a SharePoint Framework project,

yo @microsoft/sharepoint

Create a SharePoint Framework project with “No JavaScript” option. So the below code snippet does not have any JavaScript Frameworks and you can reuse it in any JavaScript framework APIs.

After the project creation, use the below npm command to install the PnP JavaScript dependencies to the SharePoint Framework project.

npm install –save @pnp/common @pnp/sp @pnp/logging @pnp/odata

After importing the PnP JS dependencies, import the classes from PnP JS to the web part by adding below lines in the _webpart.ts file.

import { sp } from "@pnp/sp";  
import { CurrentUser } from '@pnp/sp/src/siteusers';

1 2	import { sp } from "@pnp/sp"; import { CurrentUser } from '@pnp/sp/src/siteusers';

So the object is the starting point for accessing all the SharePoint related PnP objects and methods.

CurrentUser object returns the following properties for now. In the future, it may change based on the new properties introduced to the SharePoint and open source contributions to this library. We have to import CurrentUser object from SiteUsers class from the @pnp/sp.

Email: string;
Id: number;
IsHiddenInUI: boolean;
IsShareByEmailGuestUser: boolean;
IsSiteAdmin: boolean;
LoginName: string;
PrincipalType: number;
Title: string;

Add the below code snippet under the _WebPart class in _webpart.ts file in the project. getSPData method calls the PnP request method to fetch the current users’ data from SharePoint. renderData method is used to generate the HTML and pass the value for rendering. Render method renders the HTML in the browser.

//Get Current User Display Name  
private getSPData(): void {      
  sp.web.currentUser.get().then((r: CurrentUser) => {  
    this.renderData(r['Title']);  
  });  
}  
   
private renderData(strResponse: string): void {  
  const htmlElement = this.domElement.querySelector("#pnpinfo");  
  htmlElement.innerHTML = strResponse;  
}  
   
public render(): void {  
  this.domElement.innerHTML = `  
    <div class="${ styles.pnPDemos}">  
      <div class="${ styles.container}">  
        <div class="${ styles.row}">  
          <div class="${ styles.column}">  
            <div id="pnpinfo"></div>  
          </div>  
        </div>  
      </div>  
    </div>`;  
  this.getSPData();  
}

//Get Current User Display Name

private getSPData(): void {

sp.web.currentUser.get().then((r: CurrentUser) => {

this.renderData(r['Title']);

});

}

private renderData(strResponse: string): void {

const htmlElement = this.domElement.querySelector("#pnpinfo");

htmlElement.innerHTML = strResponse;

}

public render(): void {

this.domElement.innerHTML = `

</div>

</div>`;

this.getSPData();

}

Below is the output based on the code snippet. This returns the current user title value. We can also use other user properties to display in the webpart.

Get Groups of Current User

Based on the current user, we can also get the groups where the current user is the member. CurrentUser.Groups return the collection of SharePoint Groups associated with the current user. Replace the getSPData method with the following code, which is used to fetch the groups associated by the current user in SharePoint site.

//Get collection of SharePoint Groups for the current User  
private getSPData(): void {      
  sp.web.currentUser.groups.get().then((r: any) => {  
    let grpNames: string ="";  
    r.forEach((grp: SiteGroup) =>{  
      grpNames += "<li>"+grp["Title"]+"</li>"  
    });      
    grpNames = "<ul>"+grpNames+"</ul>";  
    this.renderData(grpNames);  
  });  
}

//Get collection of SharePoint Groups for the current User

private getSPData(): void {

sp.web.currentUser.groups.get().then((r: any) => {

let grpNames: string ="";

r.forEach((grp: SiteGroup) =>{

grpNames += "<li>"+grp["Title"]+"</li>"

});

grpNames = "<ul>"+grpNames+"</ul>";

this.renderData(grpNames);

});

}

I hope, you have learned how to access the current user details in SharePoint Framework webpart using PnP JavaScript Library.

SharePoint 2013 Hosting Recommendation

SharePoint 2013 Hosting – HostForLIFE.eu :: Fetching SharePoint List Items Using A Simple HTTP REST Command

Nov 15th

Posted by Peter in European SharePoint 2013 Hosting

No comments

In this article, I will introduce you to an online service I created that allows you to code against certain services without using an SDK, simply by sending HTTPS REST commands. In this article, I will demonstrate how this works against SharePoint Online; however other services are also available.

Please note that I built this service with the community in mind, and as a result, it is free for simple use. The service stores your configuration settings securely so that the actual service secrets (such as your SharePoint password) are not stored on the client code.

Developing without an SDK makes it much easier to code IoT, web and Mobile projects, and works regardless of the operating system or programming language. That’s because you can make simple REST commands instead of using an SDK; the call returns a JSON payload with the data.

Let’s see how we can fetch SharePoint List Items using a simple HTTP REST command. The REST method to call is called GetListItemEx. Let’s first look at a raw HTTP command that you can send using Postman for example. There are a few variables to change, which we will review.

GET ENZO_URI/bsc/sharepoint/getlistitemsex HTTP/1.1
authToken: YOUR_AUTH_TOKEN
_config: myconfigname
viewname: mylist
where: State=’FL’

The following variables should be replaced in the above code:

ENZO_URI: this is the URI of your Enzo service endpoint that is assigned to you on the portal
YOUT_AUTH_TOKEN: this is your assigned authToken, also available on the portal
myconfigname: this is a configuration name that you created in the portal that points to SharePoint
viewname: the name of the SharePoint list
where: an optional WHERE clause that looks like a SQL where clause

For example, the following Postman screenshot shows you the REST command I sent to my server, which in turn connected to SharePoint Online to fetch items from the US States list. The name of the configuration is called sharepointroggero (we will see this shortly).

As you can see, there are no SharePoint-specific secrets here; all the details are stored on the portal under the configuration setting called sharepointroggero. Let’s go to the portal and review the configuration settings; once you log in to the portal, click on the SharePoint service on the left, and click on Create. You will see a screen similar to this where you can store your configuration settings.

Now let’s create a small C# Console project to make the same REST call. To try the following source code, you will need to sign up on the Enzo Online portal here, create a configuration setting for SharePoint Online and access your Enzo URI and AuthToken by selecting Enzo Accounts from the menu. The code does essentially the same thing as above: it retrieves the content of a list called MyList using a configuration setting called myconfigname. As discussed previously, this code does not use the SharePoint SDK; it relies entirely on HTTPS REST calls.

using System;  
using System.Collections.Generic;  
using System.Linq;  
using System.Net;  
using System.Text;  
using System.Threading.Tasks;  
  
namespace Sample  
{  
class Program  
{  
static void Main(string[] args)  
{  
    string url = "https://ENZO_URI/bsc/sharepoint/getlistitemsex";  
    string authId = "YOUR_AUTH_ID";  
    WebRequest wr = WebRequest.CreateHttp(url);  
    try  
    {  
        // Add the required HTTP headers for the call  
        wr.Headers.Add("authToken", authId);  
        wr.Headers.Add("viewname", "mylist");  
        wr.Headers.Add("_config", "myconfigname");  
        wr.Method = "GET";  
        var resp = wr.GetResponse();    // Execute the command  
        using (var stream = resp.GetResponseStream())  
        {  
        }  
        Console.WriteLine("HTTP Response: " + ((System.Net.HttpWebResponse)(resp)).StatusCode);  
  
    }  
    catch (Exception ex)  
    {  
        Console.WriteLine("ERROR: Response from " + baseUrl + command + ":" + ex.Message);  
    }  
    Console.ReadKey();  
}  
}  
}

using System;

using System.Collections.Generic;

using System.Linq;

using System.Net;

using System.Text;

using System.Threading.Tasks;

namespace Sample

{

class Program

{

static void Main(string[] args)

{

string url = "https://ENZO_URI/bsc/sharepoint/getlistitemsex";

string authId = "YOUR_AUTH_ID";

WebRequest wr = WebRequest.CreateHttp(url);

try

{

// Add the required HTTP headers for the call

wr.Headers.Add("authToken", authId);

wr.Headers.Add("viewname", "mylist");

wr.Headers.Add("_config", "myconfigname");

wr.Method = "GET";

var resp = wr.GetResponse(); // Execute the command

using (var stream = resp.GetResponseStream())

{

}

Console.WriteLine("HTTP Response: " + ((System.Net.HttpWebResponse)(resp)).StatusCode);

}

catch (Exception ex)

{

Console.WriteLine("ERROR: Response from " + baseUrl + command + ":" + ex.Message);

}

Console.ReadKey();

}

Similarly, here is a Python sample code that does essentially the same thing.

import sys  
import urllib  
import urllib2  
import requests  
  
enzourl_receiveMsg="https://ENZO_URI:ENZO_PORT/bsc/sharepoint/getlistitemsex"  
enzo_guid="YOUR_AUTH_ID"  

#create the headers this call expects  
headers={  
    'authToken': enzoguid,  
    'viewname': 'mylist',  
    '_config': 'myconfigname'    
}  
response=requests.get(enzourl_receiveMsg,headers=headers)

import sys

import urllib

import urllib2

import requests

enzourl_receiveMsg="https://ENZO_URI:ENZO_PORT/bsc/sharepoint/getlistitemsex"

enzo_guid="YOUR_AUTH_ID"

#create the headers this call expects

headers={

'authToken': enzoguid,

'viewname': 'mylist',

'_config': 'myconfigname'

}

response=requests.get(enzourl_receiveMsg,headers=headers)

The purpose of this article was to introduce you to a new development approach that simplifies development, and removes complex SDKs from client code using SharePoint as an example. Additional documentation and sample code is available online.

SharePoint 2013 Hosting Recommendation

SharePoint 2013 Hosting – HostForLIFE.eu :: Access Denied Error

Nov 1st

Posted by Peter in European SharePoint 2013 Hosting

No comments

We have a SharePoint 2013 farm and were retracting a solution; we were using Chrome browser. In the browser our site was open in two tabs and in one tab was central admin. When we were trying to retract a solution through central admin we were getting an “Access Denied” error. We are logged in with user having Administrator rights so it seems not to be a user permission issue.

It was a very small fix but I thought to share, as maybe it can save you time.

Error and Stack Trace
Access denied. Only machine administrators are allowed to create administration service job definitions of type

Microsoft.SharePoint.Administration.SPSolutionDeploymentJobDefinition, Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.Application error when access /_admin/RetractSolution.aspx, Error=Access denied. Only machine administrators are allowed to create administration service job definitions of type: Microsoft.SharePoint.Administration.SPSolutionDeploymentJobDefinition, Microsoft.SharePoint, Version=15.0.0.0,Culture=neutral,PublicKeyToken=71e9bce111e9429c. at Microsoft.SharePoint.Administration.SPAdministrationServiceJobDefinition..ctor(String name, SPService service, SPServer server, SPJobLockType lockType) at Microsoft.SharePoint.Administration.SPSolutionDeploymentJobDefinition..ctor(String solutionName, Guid solutionId, UInt32 lcid, SPTimerService service, SPCompatibilityRange compatibilityRange) at Microsoft.SharePoint.Administration.SPSolutionLanguagePack.CreateSolutionDeployTimerJob(DateTime... e4a5099e-e182-6064-8575-d8b087e7d93cGeneral 8nca Medium ... dt, Collection`1 webApplications, SPSolutionDeploymentJobType jobType, Boolean globalInstallDlls, Boolean force, Boolean isRestore, SPCompatibilityRange compatibilityRange) at Microsoft.SharePoint.ApplicationPages.SolutionPageBase.CreateDeploymentJob(Boolean deploy, String strSelectedWeb, Boolean globalInstall, DateTime dt, Boolean localDeployment) at Microsoft.SharePoint.ApplicationPages.RetractSolutionPage.BtnSubmit_Click(Object sender, EventArgs e) at System.Web.UI.WebControls.Button.OnClick(EventArgs e) at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsy... e4a5099e-e182-6064-8575-d8b087e7d93c

Microsoft.SharePoint.Administration.SPSolutionDeploymentJobDefinition, Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.Application error when access /_admin/RetractSolution.aspx, Error=Access denied. Only machine administrators are allowed to create administration service job definitions of type: Microsoft.SharePoint.Administration.SPSolutionDeploymentJobDefinition, Microsoft.SharePoint, Version=15.0.0.0,Culture=neutral,PublicKeyToken=71e9bce111e9429c. at Microsoft.SharePoint.Administration.SPAdministrationServiceJobDefinition..ctor(String name, SPService service, SPServer server, SPJobLockType lockType) at Microsoft.SharePoint.Administration.SPSolutionDeploymentJobDefinition..ctor(String solutionName, Guid solutionId, UInt32 lcid, SPTimerService service, SPCompatibilityRange compatibilityRange) at Microsoft.SharePoint.Administration.SPSolutionLanguagePack.CreateSolutionDeployTimerJob(DateTime... e4a5099e-e182-6064-8575-d8b087e7d93cGeneral 8nca Medium ... dt, Collection`1 webApplications, SPSolutionDeploymentJobType jobType, Boolean globalInstallDlls, Boolean force, Boolean isRestore, SPCompatibilityRange compatibilityRange) at Microsoft.SharePoint.ApplicationPages.SolutionPageBase.CreateDeploymentJob(Boolean deploy, String strSelectedWeb, Boolean globalInstall, DateTime dt, Boolean localDeployment) at Microsoft.SharePoint.ApplicationPages.RetractSolutionPage.BtnSubmit_Click(Object sender, EventArgs e) at System.Web.UI.WebControls.Button.OnClick(EventArgs e) at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsy... e4a5099e-e182-6064-8575-d8b087e7d93c

It seems to be a weird error. No user permission issue.

We Googled a lot and then got the below article related to the same issue but not the exact one.

https://social.technet.microsoft.com/wiki/contents/articles/30757.sharepoint-troubleshooting-access-denied-only-machine-administrators-are-allowed-to-create-administration-service-job.aspx

In the above article the exact issue isn’t mentioned but at least we got an idea. We have closed the browser, opened the central admin again with the run as administrator option, tried again and it worked like a charm.

SharePoint 2013 Hosting Recommendation

Posts tagged trick SharePoint 2013 Hosting

SharePoint 2013 Hosting – HostForLIFE.eu :: Wildcard Search Of Users Using CSOM In SharePoint

SharePoint 2013 Hosting Recommendation

Sharegate Tips And Tricks For Migration To SharePoint

Migration of Choice Fields

Summary

SharePoint 2013 Hosting Recommendation

SharePoint 2013 Hosting – HostForLIFE.eu :: Fetching All Attachments From A List Using SharePoint Framework WebPart

SharePoint 2013 Hosting Recommendation

SharePoint 2013 Hosting – HostForLIFE.eu :: Get Current User Information Using PnP Library In SharePoint Framework

SharePoint 2013 Hosting Recommendation

SharePoint 2013 Hosting – HostForLIFE.eu :: Fetching SharePoint List Items Using A Simple HTTP REST Command

SharePoint 2013 Hosting Recommendation

SharePoint 2013 Hosting – HostForLIFE.eu :: Access Denied Error

SharePoint 2013 Hosting Recommendation

BLOGROLL

Featured On

Posts tagged trick SharePoint 2013 Hosting

SharePoint 2013 Hosting – HostForLIFE.eu :: Wildcard Search Of Users Using CSOM In SharePoint

SharePoint 2013 Hosting Recommendation

Sharegate Tips And Tricks For Migration To SharePoint

Migration of Choice Fields

Summary

SharePoint 2013 Hosting Recommendation

SharePoint 2013 Hosting – HostForLIFE.eu :: Fetching All Attachments From A List Using SharePoint Framework WebPart

SharePoint 2013 Hosting Recommendation

SharePoint 2013 Hosting – HostForLIFE.eu :: Get Current User Information Using PnP Library In SharePoint Framework

SharePoint 2013 Hosting Recommendation

SharePoint 2013 Hosting – HostForLIFE.eu :: Fetching SharePoint List Items Using A Simple HTTP REST Command

SharePoint 2013 Hosting Recommendation

SharePoint 2013 Hosting – HostForLIFE.eu :: Access Denied Error

SharePoint 2013 Hosting Recommendation

BLOGROLL

Featured On

Tags