Sitecore Publishing Service Update 3.1.3

A few days ago a new update for Sitecore publishing service appeared on download site. After lecture of release notes I take a decision to apply this update because a lot of issues were fixed.

I started my adventure on test environment where previously version 3.1.1 was installed on Sitecore 9 update 1. First I updated Sitecore Publishing Service to a new version, this was easy and fast. I check the status with a URL
http://<hostname>/api/publishing/operations/status 

Then check logs if there are any errors – but nope – service is up and running – another boring Friday.

Now easier part, just installation of publishing module. I run installation, and after few minutes module was installed. I go to Publishing Dasboard and go message:

In logs I found an exception:


Exception: Sitecore.Framework.Publishing.Client.Http.HttpServiceResponseException
Message: Could not load file or assembly ‘System.Diagnostics.DiagnosticSource, Version=4.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51’ or one of its dependencies.

I checked bin folder but ‘System.Diagnostics.DiagnosticSource ‘ was there in a good condition :-). What to do, what to do ? – Let’s open a ticket in support.

Sitecore support can not reproduce issue.

I opened ticket in Sitecore support, but very fast I got answer – please send us support package. In that case the first thing that I do is try to reproduce issue on new Sitecore installation.

I run my brand new Sitecore 9 update 2 installation, and start installing a Publishing Service module, during module installation I got an error:

Could not load file or assembly ‘System.Net.Http, Version=4.1.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ or one of its dependencies

I cannot tell you what I think at this moment. But I take decisions to run installation again, and when I run Sitecore, I saw a similar error

Solution

After some discussion on Slack, I got inspirational question:

Quick question. On the machine in question (assuming it’s a local development machine). Do you have .Net Framework 4.7 or greater installed?

Well, let’s check with a simple Powershell command:

Get-ChildItem 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full\' `
|  Get-ItemPropertyValue -Name Release

So check value here – How to determine which versions are installed. Moreover, yes I have .NET framework 4.7, but my inner voice spoke to me – install a higher version, install a higher version.

After installation of .NET Framework 4.7.2 – Publishing Service works on both environments.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: