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
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:
Message: Could not load file or assembly ‘System.Diagnostics.DiagnosticSource, Version=220.127.116.11, 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:
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
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.