Aveva Intouch 2023R2 : License manager problem

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!

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

That should normally not be an issue, setting up a All-In-One Node, but let me ask some basic questions that might help us in sorting things out.

First of all, downloading the ISO file, did you unblock the installation media?
(right click on file - select properties, unblock).
Might not be the reason for your issue but it a good practice, support has told me that 'weird stuff can happen'.

Is the server connected to a Domain or a workgroup?

Do you have multiple NIC's on your server or just one?

Is the NIC connected or disabled?

Also, please verify the NIC identification state, Public, Home or Domain network.
A NIC that identifies as a Public network can create some issues.

Is it a virtual machine? VMware/HyperV

Still, it would be of interest to get the logfiles from the machine, especially the Windows Event log.

What OS are you building your installation on?

Sys you install SQL Server manually prior to SP installation or did you use the bundled with installer? 

Any other software installed on the server? Or does it have any additional role (for example, running GR on the same node as a Domain controller is not advised).

Does you computer-name contain special characters?

If you create a new (empty) galaxy, and create a Platform, Engine, and a area can you deploy objects there? (you can not have your existing galaxy deployed while testing this).

What status does your Platform and engine show in OCMC -> Platform Manager

I stop for now, enough questions for one post

First of all, downloading the ISO file, did you unblock the installation media?
(right click on file - select properties, unblock).
Might not be the reason for your issue but it a good practice, support has told me that 'weird stuff can happen'.

  I will try this

Is the server connected to a Domain or a workgroup?

 This is presently a stand alone system. The connection is a workgroup.

Do you have multiple NIC's on your server or just one?

  there are presently two network cards.  Wireless until I have a functional system. One Hardwired (presently disconnected)

Is the NIC connected or disabled?

  hardwired is not disabled.  wireless is presently connected

Also, please verify the NIC identification state, Public, Home or Domain network.
A NIC that identifies as a Public network can create some issues.

  wireless is now set to private

Is it a virtual machine? VMware/HyperV

  it is a physical machine.  probably should have been HyperV...

Still, it would be of interest to get the logfiles from the machine, especially the Windows Event log.

What OS are you building your installation on?

  Windows 11 Pro 22H2

Sys you install SQL Server manually prior to SP installation or did you use the bundled with installer? 

   SQL Express

Any other software installed on the server? Or does it have any additional role (for example, running GR on the same node as a Domain controller is not advised).

  This is a fresh install.  System Platform is all that has been installed.

Does you computer-name contain special characters?

  No special characters

If you create a new (empty) galaxy, and create a Platform, Engine, and a area can you deploy objects there? (you can not have your existing galaxy deployed while testing this).

  I did create a new empty galaxy, platform, engine, and area.  nothing else.  deployed each individually.  crashed on area.

What status does your Platform and engine show in OCMC -> Platform Manager

presently nothing as I am having trouble getting anything to deploy

I stop for now, enough questions for one post

I am headed to a family event.  more to follow...

Thank you for your responses, It is still a guessing game since there are many unknowns and without Logfiles, (Export from OCMC and Win Eventlogs) it is just comments based on previous experiences.

But some clarifications are needed, You State that you have SQL Express, but did you install this manually (separate install) or the one bundled, reason for asking is that SQL Express can set it self to dynamic ports and System Platform needs the port 1433 to be used. But since you can access your Galaxy using IDE i guess you should be fine.

You state that Deploy of Platform and Engine is successful, (and it fails on area).
But still no Platform or engine is visible in Platform Manager, this indicates that Platform and Engine is indeed not running as it should and therefore you can not expect to be able to deploy additional objects, such as areas.

It is for this case good that you do not have a domain joined computer since it removes the issues of having Domain Policies that could case issues. But i would anyway make sure that your local administrator group contains the service accounts still.

You could also try and reconfigure your Network Service Account

Windows 11 is a Workstation OS and could also create some conflicting scenarios where it prohibits access compared to a Server OS (such as Windows Server 2022).
And "Microsoft Account/Online accounts" as Windows Account and special User restrictions could come in to play.

Your NIC setup could also be a cause of issues, reasoning behind this is that in some cases the binding order could be cause of issue.
Windows create a priority order on all Adapters as they are applied and system platform should use the one with highest priority. This is managed by setting Metrics on you interfaces.

https://www.ghacks.net/2021/11/09/how-to-change-network-adapter-priorities-on-windows-11/

Also the System Management Server could act up if you change IP now and then on your NIC that the galaxy uses.

I must admit that most of my experience is setting up System Platform on Server OS so I have to refresh my know-how here to see if there are any obvious things that needs to be done.

I don't know the features of the forum and if it allows for uploading files such as logs, but since they are such a good indication on what's going on I still would stress that these are the best things to provide to figure out what's going on. even screenshots of the log after restart and on first deploy, would be helpful.
Send a private PM if log files contains sensitive data and you don't want to post publicly.

Still, if your WIFI was on Public, this could be a reason for issues, and you need to test again after changing this.
Also if your SQL Express is using dynamic ports this has to be fixed, (installed manually).

I would set fixed IP Address on your wire NIC, 192.168.0.10, use your WIFI as secondary NIC, 
Set Wire Nic to metrics 10 and WIFI Nic to 20 (Higher).

I understand that it would be lovely to just download an entire installation (including OS) as a package but there are so many things that causes problems for AVEVA with this. Not least the OS license, Server Name (renaming after install is not advised). Different needs, hardware requirements, OS versions, etc.
So I believe the next best things are providing a good installation manual. But it would be cool with a System Platform Docker solution, but we are not there.. yet :)

At least we have AVEVA Development Studio, witch is a cloud solution that does precisely what you are requesting.

I will check to see if I can get a SP2023 R2 Alive and kicking in a Windows 11 22H2 setup, then we might have something to compare with.

So… I dumped everything again. I installed it on a Hyper-V Windows 10 Pro 22H2 machine. Everything is working so far… I think I did this to myself when I added a driver and used the AVEVA Communication Drivers Pack 2023 R2 instead of the original System Platform 2023 install package. 

I was installing on a Windows 11 Pro 22H2 system and the The Communication Drivers Pack 2023 R2 release is supported on the following Windows client and server operating systems 

Windows 10 20H1 SAC Professional, Enterprise, and IoT Enterprise
Windows 10 20H2 SAC Professional, Enterprise, and IoT Enterprise
Windows 11 20H1 SAC Professional, Enterprise, and IoT Enterprise
Windows 11 20H2 SAC Professional, Enterprise, and IoT Enterprise

I think that I resolved my problem. I posted what I did to solve the problem, but it was flagged as spam or abuse. I filed an appeal. Hopefully, they agree to post my resolution.

In response to Richard.  I used bundled SQL Express.  I appreciate all the time you spent trying to help me with the problem. I believe this was unintentional self sabotage.  I tried to install additional drivers and I was not using the original install package.  I tried to use the Communication Drivers Pack 2023 R2 which doesn't appear to be compatible with my OS revision.

Happy to share experiences and its great that you managed to move forward.

Your question led me down to installing a out of the box Windows 11 22H2 and SP 2023 R2.
The first issue I encountered was that my License Server fail to start, similar as reported by the Thread Creator, Nara Rakngam, but in her initial post it is mentioned that she was using Windows 10.

Once this is sorted out i will install CDP 2023 R2 to see what happens.

Just want to check, but are you both working on the same system or did you just add on to Nara's initial discussion in this post?

My issues after clean install on Win 11:

Edit: Turning off System Management Server resolves my issue with License Server, once turned on again it started fine after a reboot...

It is interesting that you found that CDP 2023 R2 does not list Windows 11 22H2 as supported. But 21H2 and 23H2 is.

As mentioned, it would be interesting to check if my setup, once it is running, breaks if I install CDP 2023 R2.

There is a techalert published for issues using CDP 2023 R2 (And Logger), but that relates to all other versions except SP 2023 R2.
softwaresupportsp.aveva.com/

"Operations Control Logger 23.1 breaks the deployment of objects in Application Server versions lower than SP2023 R2"

But since you are using 2023 R2 you should not be affected by this particular issue i hope.

If I find anything else of interest in this matter I will make sure to post it here, but since you have managed to resolve your problem and I hope Nara Rakngam also have a running system I believe the urgent issues are resolved.

I hijacked the post because the problems were similar.  I thought we could both benefit from this session.

Very interested in this post, as I am doing a fresh install of 2023 R2 on two machines. The first one, development, went fine. It is the SMS and License server. The second one which is a runtime, is giving me fits. I cannot configure the SMS to the primary server nor the License Server on the other machine. I have done everything I can find on-line to try, but still get "Could not connect to the Primary License Server. The reason could be either firewall is enabled on the node SCADA-6 or License Server is not running on the port 55559 or Check that the specified machine is accessible and has a License Server installed." and "Failed to configure the device" on the SMS even though in Configurator it will populate the existing SMS field, so I know it sees it on the network. I have been working on this for 3 days now. Probably need to contact tech support on this. I have checked and double checked and still no go. The CSP shows a solution error - 

 and 

I did try to repair, then reinstall as suggested and had no joy. Don't know what else to do.