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.

Perhaps you could also verify the Port on the server, 

You can use PowerShell to find out which process is listening on the TCP port 55555. Just enter this command:
Get-Process -Id (Get-NetTCPConnection -LocalPort 55555).OwningProcess

Just want to make sure the port is available and not used by any other process.

Looks like the ports on the server are available...  the server just won't start.

Ok, There are many things that could be wrong and perhaps the quickest route for you is to contact your local support to sort out what's going on.
But it would be of interest to verify if you have any errors noted in Windows Event Log, if the service fail to start it might be a better clue on why it fails to start.

Many errors state errors like 'Address already in use', but reasons for this has to be sorted out.

Also, please let us know if this is a single server setup, License server/GR/System Management Server on the same node, or if you try to connect to a remote server. I think i precede this as all on the same node, just want to make sure.

Also please check on the server, how many Network Cards are in use, and is IPV6 enabled on NIC (disable if not in use)

If possible. Please do a restart of the system and upload an export of your SMC Log and Windows Event logs (Application and System).

Also, if you have done any repair of the installation, please check that you don't have any AVEVA related services stuck at 'Disabled', I have experienced some issues where I performed a repair and the installation did not enable all services after completion.

No other Antivirus installed on the server? Host files in use? 

Richard,

I connected the machine to the web and returned the licenses.  Then I dumped the build and started over.  Not sure what happened, but I am sure it was my fault...  the configurator looks different today...  The license server is running!

Hi Christopher, 

I'm happy that you managed to resolve your issue.

I have seen the appearance of the IDAS in other places (a customer upgrade), unfortunately I do not know why it happens and AVEVA support could not tell me either.

I tried to configure the node but that only ended up in repeating errors in SMC, but everything else worked though. I managed to remove the configuration but not the node.

It disappeared when i made a repair of the installation. (2023 P03).

The IDAS node does not normally exist on a node that has Historian installed.
But i leave Aveva engineers to comment that if needed.
Enjoy your weekend and hope everything else is working smoothly for you.

My license server is running, but I am still unable to deploy my entire project. Every time I attempt to deploy the first area, I encounter a communication failure. While I can successfully deploy the GR (Galaxy Repository), the view engine, and the app engine, nothing else seems to deploy. System Platform 2023 has been an incredibly frustrating package! I wish they would consider offering a preconfigured Hyper-V or VMware system that is ready to go. All I would need to do is install the proper licenses and then build the system. Creating a preconfigured virtual machine (VM) for all their Role-Based Installations would be a game-changer. Unfortunately, I’ve exhausted all my available hours trying to get this product launched. Now, I find myself working weekends and evenings, desperately trying to push this project across the finish line.

The system I am trying to build is an All-In-One no other devices to communicate with!