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.

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.

Hello Glenn,

Was the install media "unblocked" before use?  In general, this sounds like a networking issue of some sort, where things are blocked between the two computers.  

We looked at that before we installed, but there were not options regarding unblocking in the properties.

I agree it is a networking issue, but we have opened up everything, it should be communicating.

Hi Glenn!

What System Management server is configured on your license server?

And is your node configured to use the same?

Connection to license server can fail if they are not set up correctly. 

-Edit- You state in your post that your Dev node is license server and SMS.
Still, a remote connection to license server is out of the box dependent on a correct SMS Setup.
And it will fail with connection issues if this is not working

ports on the SMS are 80 and 443, runtime machine the same, when I try to connect to the SMS, the computer name will populate itself in the Connect to an existing SMS field so it is being found. not sure what else I can configure there.

ports on the SMS are 80 and 443, runtime machine the same, when I try to connect to the SMS, the computer name will populate itself in the Connect to an existing SMS field so it is being found. not sure what else I can configure there.

So is the Connection to the remote System Management Server correct on the remote node?

The configurator will ask for SMS Servers on the network and it is expected it should identify and autofill the remote SMS Server node.

You stated "I cannot configure the SMS to the primary server", so we need to sort this out first, 

On your remote machine, when you click 'Configure' do you get any issues, password prompts, errors displayed, in SMC, is the cause of the problem logged here?

Do you get the Green checkmark on your System Management Node?

Oh, and what OS is used on the remote client?
I have been struggling with some editions of Windows 11 to get this working 

Also, is you computer joined to a domain or part of a workgroup?
please check the network status, it should not identify itself as Public on your SMS Server node.

windows 11 pro 23H2 brand new dells build 22631.4317 , domain controller not ready yet, we are on a workgroup, private network

Ok, Please check my previous questions.

But unfortunately there could be several reasons for the issue, and perhaps your quickest route is to contact techsupport, they can assist you in checking each thing necessary and they have the experience of all other customers contacting them with issues to pull from.

Since both machines are Workstation computers (Win 11) and both are on Workgroup, there might be some standard policy's or security settings restricting your setup. 

At the moment I still have some issues with my Win 11 setup (also in Workgroup), Connecting a Windows Server 2022 works without any issues. I have managed to get past the SMS config and License server but other config fails.

no green checkmark, I get "Failed to configure the device". I am doing some updates on these computers right now, so I will report out tomorrow. Thanks

Any resolution to this? I am having the same issue...

This is a large thread with several symptoms/problems being described.  I recommend giving a full description of what you are seeing, or contacting your local support provider to create a ticket.

I have created a support ticket for this issue. They have recommended several workarounds, still no success. It has been over a week now with no resolution.