Discovery Import

Discovery Import

License activation issue

    • tim.dukes
      Subscriber

      We have a customer who is running into issues activating there license. 

       

      They are getting 'Not connected to a license server for licensing actions' then ' ANSYSLI exited or could not read server port ANSYSLI_FNE_PORT

       

      I have seen another post re. above which suggests it may be a firewall issue with notes to enable communication. Is there any documentation on how they would do this.

       

      Firewall Exception Rules

      • Enable https communication over port 443 (in-going and outgoing) to the server located at https://ansys-fno.flexnetoperations.com/
      • Exclude the ansysls_client.exe (subscription handler) process on your company firewall

      ANSYS Discovery products licensing requests might also be denied by your antivirus software or by missing user permissions in Windows. If you are still experiencing issues after adding the aforementioned firewall exception rules, please try the following troubleshooting recommendations.

       

        

    • Subashni Ravichandran
      Ansys Employee

      Hi  Tim Dukes

      As these changes are made on the company's firewall, you may suggest the customer take help of their company's IT personnel while implementing them. 

    • tim.dukes
      Subscriber

      Hi there customer still having issues even after implementing firewall changes and completely removing the firewall software itself. Running into the same errors.

       

      We have taken a look at this and added the exceptons to BitDefender and re-tested. It came up with the same Error. We have completely removed bit defender and disabled the onboard windows firewall and tested with the same error. I can confirm the user has write access to both of the directories listed and this was also tested.

      Let us know if you have any other suggestions you need us to try.

    • Subashni Ravichandran
      Ansys Employee

      Tim Dukes

      Can you please go through the Troubleshooting document, especially the point 5A and let me know if it was helpful to you.

Viewing 3 reply threads
  • You must be logged in to reply to this topic.