• State Suggested Answer
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 13 subscribers
  • Views 448 views
  • Users 0 members are here
Options
Related

License Server Not Working After PC Name Change

Chetan Prajapati

Dear AVEVA Support Team,

I hope this message finds you well.

I am facing an issue with the AVEVA Enterprise License Server after changing the PC name on our system. The previous PC name was `MRFLMCDUPLEX`, and it has now been updated to `MRF_LMC_DUPLEX`.

After this change:
- The License Server Agent is not binding to port 55559.
- The AVEVA Configurator shows an error: “Could not connect to the License Server.”
- The License Manager shows the server running, but no licenses are found.
- We also attempted to run the AEWorkgroupUtility and reconfigure using the current hostname, but the issue persists.

It seems the license service is still trying to register with the old PC name. Kindly assist us in either reactivating or rehosting the license to the current system hostname.

Please let me know if you require the `.req` file or any additional logs/screenshots.

Looking forward to your prompt support.

Parents
  • 0

    Hi Chetan, 

    Just to be clear, to reach the Tech Support Team you have to use other ways of contact, also uploading customer license files and information here is not advised. 
    With that said there are some resources on the topic available that might help you.

    Also, in similar scenarios, I have resolved my issue by going back to my old server name, de-activate my license, and then move forward to the new name again.

    https://softwaresupportsp.aveva.com/en-US/knowledge/details/000022120?lang=en_US

    Rename a License Server

    You can rename a license server, typically as part of managing computers on your network. There are several important points to keep in mind when renaming a license server:

    • By default, the license server name displayed in the License Manager is the same as the computer name.

    • You can change the license server display name inside License Manager without changing the computer (machine) name or the License Server ID.

    • The License Server ID is a unique identifier used by other components of the licensing platform, including License Manager and the authentication server. A portion of the License Server ID is the host computer name. The License Server ID consists of the computer name plus a unique GUID (Globally Unique Identifier).

      Important: As a highly recommended best practice, deactivate all licenses on the server before you rename the server. Reactivate the licenses after renaming the server.

    If you do rename a License Server without first deactivating all licenses on the server, use the procedures outlined in the following scenarios to complete renaming your license server and reactivate your licenses.

    Rename the License Server node

    Make sure all licenses are deactivated before renaming the node where the License Server is installed.

    If you rename the node while licenses are activated on the License Server, the licenses become invalid and cannot be acquired. Additionally, the licenses cannot be reactivated unless you contact technical support to recover your licenses.

  • 0 in reply to Richard Köhlerstrand

    Dear Richard,

    Thank you for your reply.

    I have checked the system, and the customer had already removed the license before changing the PC name. However, after renaming the PC, we noticed that the License Server Agent is no longer running on port 55559.

    Could you please advise what the next step should be in this case? Should we proceed with reactivation, or is there any reconfiguration required to restore the License Server Agent functionality?

    Looking forward to your guidance.

  • 0 in reply to Chetan Prajapati

    I don't have a solution at hand for you, only some experience based on similar scenarios.

    I'm thinking that renaming a machine with PCS (a component for encrypting communication between AVEVA products) installed is not such a great thing, and if you are using System Management Server in your system, there could be a scenario where your License server is included in this, and a certificate is created, based on the initial name of the machine.

    So it is not allowed to reach the license server since it has a new name that is not incorporated in the PCS framework.

    This assumption is that you ARE using System Management Server, if this is this the case I can suggest you to reconfigure your System Management Server, or even reinstall PCS.

    Based on previous discussion

     What about renaming the machine name? 

Reply
  • 0 in reply to Chetan Prajapati

    I don't have a solution at hand for you, only some experience based on similar scenarios.

    I'm thinking that renaming a machine with PCS (a component for encrypting communication between AVEVA products) installed is not such a great thing, and if you are using System Management Server in your system, there could be a scenario where your License server is included in this, and a certificate is created, based on the initial name of the machine.

    So it is not allowed to reach the license server since it has a new name that is not incorporated in the PCS framework.

    This assumption is that you ARE using System Management Server, if this is this the case I can suggest you to reconfigure your System Management Server, or even reinstall PCS.

    Based on previous discussion

     What about renaming the machine name? 

Children
No Data
© 2025 AVEVA Group Limited or its subsidiaries. All Rights Reserved.