Workflow Manager 1.0 Now Supported on Windows Server 2016 with CU4

SP2013

Hello everyone,

Today I’ll talk about a great news that can interest those who works with SharePoint On-Premises.

I have a customer where the infrastructure team wanted to upgrade our entire server to the latest version as a part of our migration from SharePoint 2013 to SharePoint 2016.

Seems pretty cool to be up to date but they warn us about one little problem

 

Windows Server 2016 does not support Workflow manager… ouch

 

As a reminder, Workflow Manager was introduced with SharePoint 2013 to run the custom workflows out of the SharePoint. That’s how you were supposed to develop your new Visual Studio Workflow to use it.

Workflow manager introduced also the possibility to create SharePoint 2013 Workflow with SharePoint Designer.

So in the end, many people used it one way or another.

 

Not so long ago, the workflow team announce the good news, Workflow Manager Server 1.0 now supports the following platforms when used in a SharePoint Server 2016 environment.

  • .NET 4.6+ (when using Service Bus Server 1.1 with KB3086798)
  • Windows Server 2016
  • Windows 10 x64 (for development purposes)
  • SQL Server 2014 & SQL Server 2016

 

More info here : https://blogs.msdn.microsoft.com/workflowteam/2017/07/25/workflow-manager-1-0-now-supported-on-windows-server-2016-with-cu4/

 

Hoping this helps,

 

Christopher

Advertisements

Crawl run endlessly without results

SP2013

Hello everyone,

Today I’ll talk about an error which may occur with search on-premise.

When you have a lot a document and not a big farm, the crawl can take a long time, but sometimes it takes a looooooooooooooooooooooong time without any result!

Something like this

searchnotstopping1

As you see in this crawl log, it has been more than 16 hours without nothing (no errors, no successes, nothing…)

If that happens to you, I would suggest those 3 simple steps

Go to the content source and stop all crawl

searchnotstopping2

Open services and reset SPSearchHostController Service. 

Warning : Doing this will cause an short interruption of the search in your farm, some user can experience a “Something went wrong” message if they perform a search shortly after the reset. Do this during planified maintenance hour if the search is already in use.

searchnotstopping3.png

Go to the content source and start all crawl

searchnotstopping4

After that, you should get some result in the crawl log

searchnotstopping5

 

Hoping this helps

Christopher

List of free tools for SharePoint

Hello everyone,

Today I’ll do some advertising for another blogger who makes a great post about free tools for SharePoint.

Some of them are new to me and seems pretty awesome! Great job Velin and Thank you for this one!

http://blog.velingeorgiev.pro/sharepoint-online-free-developer-tools-list-more-productivity

 

Hoping this helps,

Christopher.

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.

Problematic

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.

Reason

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 https://github.com/SharePoint/PnP-JS-Core/issues/125

Resolution

The solution to this problem is to pass a configuration before making the call: https://github.com/SharePoint/PnP-JS-Core/pull/127

pnp.setup({
        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 !

Christopher.