We've received calls where an update to .net has caused issues where errors occur such as "Failed to read licence file" or “There is no valid licence for your system”.

This means you are unable to access System Administration or Sage 200 Professional itself.

For this issue to be determined as the above, you can check the following:

• Windows Event Log: It will display an error similar to “Windows cannot find the local profile and is logging you on with a temporary profile”
• Sage 200 Secured Services log: Sage server – C:\inetpub\Sage 200 App Services\Sage200SecuredServices\Log – error text will show : Sage.UK.SSDP.SLS.Infrastructure.DocumentValidator Validate - Caught exception. Returning DocumentCertificateInvalid: System.Security.Cryptography.CryptographicException: An internal error occurred.

We've determined this to be linked to recent .net 4.6.1 / 4.7 updates changing the way .net applications work with Windows infrastructure. This issue should only affect users on Windows 2008 / 2008 R2 and test setups using Windows 7 as a server. If you have any other occurrences on other versions of Windows, please let us know.

.Net Update Issue

When getting the following message when logging on to Sage 200 Professional after installing latest version of .Net, including .Net 4.6.2, .Net 4.7 and Windows Update KB4014606 for .Net 4.6/4.6.1:

Failed to read licence details

Versions affected:

• Sage 200 Professional 2013
• Sage 200 Professional 2013 R2
• Sage 200 Professional 2015
• Sage 200 Professional 2016

Windows Operating System affected:

• Windows 2008 R2
• Windows 7, if this is being used as a Server installation

To resolve this issue, please download and install the following update:

• .Net hotfix

Workspace Issue

The same .Net updates cause a 'Server/ System Error' message to appear on all workspaces.

Versions affected:

• Sage 200 Professional 2015
• Sage 200 Professional 2016

Windows Operating System affected:

• Windows 2008 R2
• Windows 7, if this is being used as a Server installation

A hot fix is available for Sage 200 Professional 2015 sp3 and Sage 200 Professional 2016 sp2 only, and need to be applied after applying the .Net update hotfix.

• Sage 200 Professional 2015 sp3 - 2015 workspace hotfix
• Sage 200 Professional  2016 sp2 - 2016 workspace hotfix

If you're unable to apply the update immediately, a workaround is to temporarily assign a full domain admin user to the Secured Services application pool in IIS, then run an IISReset.

[BCB:19:UK - Sales message :ECB]