SyntaxError Unexpected token in JSON at position 0

Hello everyone,

Today I will talk about a problem concerning the use of PNP JS Core on an environment 2013 OnPremise.


Like many I started using PNP JS Core for my developments. After retrieving some information and doing some conclusive tests on an Office 365 environment, I wanted to reuse my code on a SharePoint 2013 OnPremise.

And there .. Boom!

SyntaxError: Unexpected token < in JSON at position 0

The code does not have anything complicated, it will only read the contents of a list.


Looking a bit, I saw that the return of the REST call was XML and not JSON. It seems that this comes from the basic configuration of SharePoint 2013 SP1


The solution to this problem is to pass a configuration before making the call:

        headers: {
            "Accept": "application/json; odata=verbose"

Simple but when you start using PNP JS it can be useful to know.

Hoping it helps.

NB : Thanks to Yannick for helping the noobie I was in this situation !


ESPC16 Feedback – Part 2

Hello everyone,

Today I will continue on the subject of the previous post by talking about tools that I’ve seen in action at the ESPC16.

QUnit :

JavaScript library for Unit tests:


jQuery Mockjax :

JavaScript library for mocking Ajax calls:


Selenium webdriver :

Available as a Nuget package, it allows ,among other things, to do UI tests by simulating different browsers:


Approval Test :

A tool allowing you to make tests on .Net code, very useful also to refactor existing code!


Swagger :

A tools that helps you design, build, document, and consume your RESTful APIs.


Graph Explorer:

A tools helping you to create your graph requests


Don’t forget that you can find many sessions video in the resource section of the ESPC website:


Hope this helps !


ESPC16 Feedback


Hello everyone,

As I told you in the previous post, the ESPC16 conference was full of information! Both for announcements made and for the tools used during the different sessions.

I will try to collect my notes on the various subjects to share them with you.

Some statements:

  • ContentTypeHub : there are a lot of features in SharePoint, and not all of them are good
  • Feature pack planned to be release every 3 or 6 month
  • Bulk download of files is planned
  • Add link as a document in document library is planned
  • Sooner or later save site as template will disappear
  • Upcoming SharePoint integration means you’ll be able to launch PowerApps directly from the SharePoint mobile app.
  • “It’s build on #SharePoint because I can ! ” Wrong reason!
  • “Data are more secured in the cloud than onprem !”
  • Power Apps : Only 500 requests by minute allowed by connection.
  • Stop using Appweb!

Technology to follow:

Another important point, Microsoft is listening to our experiences, so if you want to provide feedback , go to

Enjoy your reading!


Back on track

Hello everyone,

Wow, it’s been a long time since I said that! About a year and a half!


I had lost the passion to be part of the community but I was lucky enough to be able to take part in the European SharePoint Conference in Vienna this month and I confess I had a lot of fun chatting with the people there.


From the “simple” lambda to the expert / MVP / pnp member / etc .., everyone was motivated and passionate about what he / she did on SharePoint.


Seeing all this I tell myself that I will go back to publishing on SharePoint / Office 365, probably starting soon with a summary of the useful things I learned at this event.

Hopefully this will help you … again


Link in alert mail incorrect


Hello everyone,

Today I’ll talk about a problem with standard SharePoint alerts.

It can happen that the links in those emails use inaccessible url by end users, ie the URL of the server. This comes from bad information that can be found everywhere on the net, namely that the url is generated based on the URL used to specify the alert.

After making several tests on a SharePoint to date, I have always had the same urls little import the url used to set the alarm (perhaps a residual bug …)

The result of the tests is that the link used for alert messages is the link specified in the “Default Zone” of “alternate access mapping”.

So just change the order of URLs in AAM to have URL accessible by everyone in the default area.

Hope this helps,


Edit Control Block incomplete


Hello everyone,

Today I’ll talk about a problem that may occur in lists and libraries SharePoint 2013.

One of the new SharePoint 2013 feature is the evolution of “Edit Control Block” menu. Now it displays an ellipse for selection. The purpose of this article is not to discuss the artistic choices of this change but to report bugs that may arise.

Once clicked the first ellipse, you see the new “Call-Out Menu” including links to open and share the document and an ellipse which should open following options. Yes .. should ..


Indeed it may be that when you clicked on this link, instead of displaying the following the menu, nothing happens.

The problem I had is that NOTHING was happening at the click! No JavaScript error, not server error. Nothing at all!

My first thought was of a permissions problem, but tests on several libraries with the same settings had different results! After several tries, I was able to isolate the fact that the problem arose in subfolders of some lists created based on a template. Template itself creates via the SharePoint interface.

Another test was to create a new view with the same parameters, and BINGO it works properly! That means that an error occurred during the creation of the list. After investigation, it turned out that the list was created by PowerShell, perhaps an error has occurred in creation.

The quickest solution to keep your data is to recreate the views for lists with this problem.

Hope this helps,


Alert mail not received


Hello everyone,

Today I’ll talk about a problem that may occur when you set alerts for users.

The error in question is the fact that the user receives the mail saying that an alert was created for him, but he is not receiving alerts generated by adding / modifying element.

One reason could be found if you configure the log to “Verbose” for the “Alert” category.

To configure the logs level, follow this procedure:

  • Go to the central administration
  • Click on the “Monitoring
  • In the “Reporting” section, click on the link “Configure diagnostic logging
  • In the “Event throttling” section, just expand the “SharePoint” section and select “Alerts
  • In the dropdown “Least critical event to report to the track log” choose “Verbose
  • Click ok

Note: This operation does not cause recycle or IISRESET, it can be done live on production farm. By cons when you have finished your test, be sure to return to the previous configuration state (choosing “Reset to default” from the dropdown list, failing which your log files grow very large).


This configuration will allow you to see such entries

“Alert for Immediate subscription {GUID}, event ID, USERNAME succeeded permissions check”

If instead you see such entries

Alert for Immediate subscription {GUID}, event ID, user USERNAME failed permissions check

You have your culprit!

Indeed, when sending an alert, a test is made in advance to find out whether the user can log in to the site! If you have not yet given access to the user, although it will receive the email telling him that an alert was created for him, he will not receive the actual alerts!


Hope this helps,