License Server Not Working After PC Name Change

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
  • Computer name cannot have an underscore.  I am assuming the Licensing version is 4.x and the License Server cannot accept a computer name with an underscore.

    • DNS (Domain Name System) rules, which many systems follow for hostnames, only allow:
      • Letters (a–z)
      • Numbers (0–9)
      • Hyphens (-)
    • Hostnames cannot contain:
      • Underscores (_)
      • Spaces
      • Special characters like @, #, !, etc.

    Exceptions:

    • NetBIOS names (used in older Windows networking) can include underscores.
    • Some internal systems or applications might allow underscores, but it's not recommended for compatibility and standardization reasons.
Reply
  • Computer name cannot have an underscore.  I am assuming the Licensing version is 4.x and the License Server cannot accept a computer name with an underscore.

    • DNS (Domain Name System) rules, which many systems follow for hostnames, only allow:
      • Letters (a–z)
      • Numbers (0–9)
      • Hyphens (-)
    • Hostnames cannot contain:
      • Underscores (_)
      • Spaces
      • Special characters like @, #, !, etc.

    Exceptions:

    • NetBIOS names (used in older Windows networking) can include underscores.
    • Some internal systems or applications might allow underscores, but it's not recommended for compatibility and standardization reasons.
Children
No Data