• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 4 replies
  • Subscribers 12 subscribers
  • Views 1164 views
  • Users 0 members are here
Options
Related

Port 443 in use when configuring a System Management Server.

Jakob Agustsson

Hi, I am doing a fresh All in one Node installation of System platform 2023 R2. 

When configuring the System Management Server it reports the default port 443 being in use and thus not available.  When checking which process is using that port it shows me the intouch access anywhere service. (PID 4360)  This is a totally fresh installation with everything installed at the same time. 

I then uninstalled the intouch access anywhere from the fresh installation and then I could configure the SMServer to use 443.  Is this conflict normal?

regards 

Jakob

  • +1

    Hi Jakob,

    Looks like this conflict will be 'normal'. As a technical support engineer with a local AVEVA distributor, I have access to AVEVA's case reports database, where I am able to find multiple case reports which detail exactly what you are running into. 

    Customers have reported that they would have a new download with all of the System Platform components, but when they attempted to configure SMS, they get something along the lines of "Error while configuring System Management Server (SMS), Failed to configure the device, The https port 443..."

    A majority of these cases list the solution as what you followed: Uninstalling InTouch Access Anywhere. One case even mentions that after doing the uninstall, and then configuring SMS on port 443, the customer was able to re-install ITAA and have it work correctly. So my guess is that the installer for System Platform 2023 installs ITAA first, and then the SMS components, which then creates this conflict. 

    I tried to look for if AVEVA has officially published anything in regards to this behavior, but only came up with the following technote[000033508]: softwaresupportsp.aveva.com/

    I know that technote discusses Plant Scada Access Anywhere, but I think the overall points made in consideration with SMS will be the same for InTouch Access Anywhere. 

  • 0 in reply to Adam Rego

    ok, thanks a bunch for the feedback!

    took a while before I realized that this was the issue, for a newbie like me installing everything at once on one node this can cause serious headache Slight smile seems like something that could easily be fixed and avoided. 

  • 0 in reply to Jakob Agustsson

    Hi, the recommendation is to install Intouch Access anywhere in a different machine and not the same machine

  • 0 in reply to RAINER CARLTON DSOUZA

    Hi, Rainier thank you, noted.   That was the intention in the first place.  However in my opinion doing a full install should not result in this error. There are multiple parts of the SP installation that is not necessarily used on the same node but are still installed. It is hard for the inexperienced user to realize what is causing the problem.  There should at least be a warning in my opinion.

© 2024 AVEVA Group Limited or its subsidiaries. All Rights Reserved.