Aveva Intouch 2023R2 : License manager problem

Hi,

Judging by the log messages, it may not only be licensing that doesn't connect properly. On thing that is common to licensing, the InTouch Data Services, and that "PCS" thing that the logger speaks about, is secure communication. Therefore, it could be worth verifying that the security settings are completely configured.

To do so, open the "Configurator" application (available in the start menu under one of the AVEVA folders) and check 2 things:

1. That a System Management Server is defined and configured (unless you're aware of a different computer already being used as System Management Server in your network, you can simply make this node the System Management Server)
2. That the license server is configured for secure access.

I'll see if I can dig up some more information about this and a documentation reference. I don't have the software in front of me right now.

I did it but I still got errors. TT

AnnounceOnline could not announce to local discovery service due to communication error: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

"License Manager cannot connect to the License Server on port 55555.
Possible reasons:
Invalid port configuration. (or) FireWall Settings - Connection refused due to blockage of port. (or)
License Server is not running.

The log messages report that PCS.Proxy.Wcf failed to register InTouch Data Service. Firstly, we should confirm that PCS framework is healthy.

• Launch Common Services Portal from Aveva from Windows Start Menu
• Click on Scan button from Troubleshooting tab on the left pane
• See if there is any error reported against PCS Framework

If any error is reported by Scan, you may have to either repair PCS framework.

If no error, it could be InTouch (including AEL license platform) installation related. Some dependent component is missing? Check if there is any error of missing component reported in Windows Event Viewer.

Also ensure Microsoft .NET 6.0.25 or latest is installed on the target machine.

Hi Nara,

I don't see where you've come back to post if you got this resolved or not.

Based on the License Proxy errors that I see in the log, you likely have an issue related to TLS.  To resolve, you can force all applications to use TLS 1.2, which is considered to be more secure.

Article I found informative on the settings - businesswintelligence.com/.../enforce-tls-strong-crypto

Microsoft Article - https://learn.microsoft.com/en-us/dotnet/framework/network-programming/tls 

Steps for you to follow to easily resolve....
Create a text file with the following contents....

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto" =dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto" =dword:00000001

Rename the file to have a .reg extension. Make sure you are showing the extensions when you try to make this change.

Once it is named to a .reg file, you can double click and it will add the entries to your registry.

Once that is done, reboot and test the licensing again.

Hi Devid
Thank you for your answer. I got resolved. The problem was some drivers of the embedded PC Maybe it's not support Wonderware Intouch 2023R2. So i try to install the driver and Wonderware intouch 2020R2 . Its work.

Hi Nara,

Could you explain what drivers you exactly mean?

the embedded PC is Nexcom NISE3900E . I reinstalled the Intel® Rapid Storage Technology Driver then .Net framework error in the log event disappeared. ฺAfter That I installed ww2023R2 but the .Net framework error happened again.

So I decided to use ww2020R2 instead. It works.

the embedded PC is Nexcom NISE3900E . I reinstalled the Intel® Rapid Storage Technology Driver then .Net framework error in the log event disappeared. ฺAfter That I installed ww2023R2 but the .Net framework error happened again.

So I decided to use ww2020R2 instead. It works.