We have an exciting announcement about badges coming in May 2025. Until then, we will temporarily stop issuing new badges for course completions and certifications. However, all completions will be recorded and fulfilled after May 2025.
Ansys Products

Ansys Products

Discuss installation & licensing of our Ansys Teaching and Research products.

The COM engine is not registered or registered incorrectly

TAGGED: ,

    • nkirkby
      Subscriber

      Hello, I have just installed AnsysEM v242 and rsm on a remote Ubuntu 22.04.4 LTS system.

      I am running AEDT v231 on a Windows 11, and have configured the remote Ubuntu system as a remote solver. I find the following error when clicking Analyze All:

      Checking Machine
          Pinging machine
              32 bytes from :icmp_seq=0 time=5 ms TTL=129
              32 bytes from :icmp_seq=1 time=5 ms TTL=129
              32 bytes from :icmp_seq=2 time=5 ms TTL=129
              32 bytes from :icmp_seq=3 time=5 ms TTL=129
              4 packets transmitted,4 packets received, 0%packet loss. Round-trip (ms)  min/avg/max = 5/5/5
          Checking AnsoftRSMService availability on machine
              AnsoftRSMService is alive
              This machine has multiple network cards. Additional configuration may be required...
              The IP addresses for this machine are:
                   
                   
              AnsoftRSMService is listening at : 32958
              AnsoftRSMService is configured to allow remote solves
          Checking list of registered engines on machine
              enscomengine:2024.2 is registered and available from /home//AnsysEM/v242/Linux64/ENSCOMENGINE
              EXTRACTOR2DCOMENGINE:2024.2 is registered and available from /home//AnsysEM/v242/Linux64/EXTRACTOR2DCOMENGINE
              HFSSCOMENGINE:2024.2 is registered and available from /home//AnsysEM/v242/Linux64/HFSSCOMENGINE
              ICEPAKCOMENGINE:2024.2 is registered and available from /home//AnsysEM/v242/Linux64/ICEPAKCOMENGINE
              MAXWELL2DCOMENGINE:2024.2 is registered and available from /home//AnsysEM/v242/Linux64/MAXWELL2DCOMENGINE
              MAXWELLCOMENGINE:2024.2 is registered and available from /home//AnsysEM/v242/Linux64/MAXWELLCOMENGINE
              MECHANICALCOMENGINE:2024.2 is registered and available from /home//AnsysEM/v242/Linux64/MECHANICALCOMENGINE
              Q3DCOMENGINE:2024.2 is registered and available from /home//AnsysEM/v242/Linux64/Q3DCOMENGINE
              RMXPRTCOMENGINE:2024.2 is registered and available from /home//AnsysEM/v242/Linux64/RMXPRTCOMENGINE
              desktopjob:ElectronicsDesktop2024.2 is registered and available from /home//AnsysEM/v242/Linux64/desktopjob
              nexxim:2024.2 is registered and available from /home//AnsysEM/v242/Linux64/nexxim
              spexporter:2024.2 is registered and available from /home//AnsysEM/v242/Linux64/spexporter
          Checking for jobs running registered engines on machine
          There are no jobs running registered product engines on this machine
      Testing Completed.
      Success! All tests successful.

       


      What might the problem be?

    • nkirkby
      Subscriber

      Here are the contents of AnsysEM/rsm/Linux64/ansoftrsmservice.log:

      cat ansoftrsmservice.log
      *** Dependency verification test disabled by default ***
          [ Use 'export ANS_DEPCHECK=1 ; ./ConfigureSoftware.bash --fullconfig' ]
      -----------------
      [Error] AnsoftRSM initialization warning: This machine has multiple IP addresses. In case of communication issues, refer to product documentation for multiple IP addresses.

    • randyk
      Ansys Employee

      Hi Nkirby,

      Please do the following:

      1. make sure the version on your Windows is exactly the same as the Linux:
      Linux: cat /home/AnsysEM/v242/Linux64/product.info
      Windows:  type  "C:\Program Files\AnsysEM\v242\Win64\product.info"

      2. On Linux, make sure the default tempdirectory is referencing a writable location - like /tmp
      This is specified in file:   /home/AnsysEM/v242/Linux64/config/default.cfg

      3. On Linux, confirm solver functionallity:
      mkdir ~/anstest


      cd ~/anstest

      cp /home/AnsysEM/v242/Linux64/schedulers/diagnostics/Projects/HFSS/OptimTee-DiscreteSweep-FineMesh.aedt   ~/anstest/OptimTee-DiscreteSweep-FineMesh.aedt

      /home/AnsysEM/v242/Linux64/ansysedt -ng -monitor -useelectronicsppe=1 -distributed -machinelist list=localhost:-1:4:90% -auto -batchoptions "" -batchsolve TeeModel:Nominal:Setup1  ~/anstest/OptimTee-DiscreteSweep-FineMesh.aedt

      Examine the ~/anstest/OptimTee-DiscreteSweep-FineMesh.aedt.batchinfo/*.log    to confirm successful completion  (should solve 3-5 min)

      If success, clear all but the ~/anstest/OptimTee-DiscreteSweep-FineMesh.aedt

      rerun with the following change:
      /home/AnsysEM/v242/Linux64/ansysedt -ng -monitor -useelectronicsppe=1 -distributed -machinelist list=$(hostname):-1:4:90% -auto -batchoptions "" -batchsolve TeeModel:Nominal:Setup1  ~/anstest/OptimTee-DiscreteSweep-FineMesh.aedt

      Is this successful?

      If so, make sure:
      1. Passwordless SSH is enabled on Linux
      2. all firewalls are disabled on both Windows and Linux (for this test)
      3. both machines are on the same network
      4. Open AEDT in Windows and run:

      Copy "C:\Program Files\AnsysEM\v242\Win64\schedulers\diagnostics\Projects\HFSS\OptimTee-DiscreteSweep-FineMesh.aedt"  to  c:\temp

      Open C:\temp\OptimTee-DiscreteSweep-FineMesh.aedt

      AEDT : Tools->Options-> General Options->Remote Analysis
               [x] Specified User
               Username: 
               Password: 
               Domain:  blank

      AEDT : Tools->Options->HPC and Analysis options
      Design type: HFSS
      [Copy]
      Configuration name:
      [x] Use automatic settings
      Num variations to distribute [1]
      Select/rename "localhost"  to the name of your Linux hostname
      Cores=4
      GPUs=0
      RAM Limit=90%
      Enabled [x]
      [OK]
      [Make Active]
      [Ok]

      Expand the project -> Analysis -> Setup1 
      rt-click on "sweep"  and select "Analyze"

      Is this successful?

      If so and you require firewalls on your Windows machine - there are multiple options:
      1. you could open all ports between your Windows and Linux machine
      2. you could open all ephemeral ports with something like (assuming Windows Defender FW)
      From Elevated CMD (rt-click and "run as admin"):
         netsh advfirewall firewall add rule name=HFSS dir=in protocol=tcp localport=49152-65535 action=allow
      3. recursively add all binaries from the AnsysEM installation to your firewall exceptions


      thanks
      Randy

    • nkirkby
      Subscriber

      It seems I am facing the same issue as this post:

      I had some troubles in the past with versions 13-15. There were TCP ports necessary to open, not properly documented in the manual. Try disabling firewalls completely, for determining, is it the case. RMS and the EDT should be of the same version, btw.

      Facing issues while distributing the tasks on different machines

      Could you please list the exact ports that must be open on the server? This machine cannot run with firewall (ufw) completely disabled. 

       

       

    • randyk
      Ansys Employee

      Hi nkirkby,

      For firewalls, you would need to open the complete ephemeral port range (TCP only) for our solvers.
      You can obtain the starting port and range with the following commands:
         Linux:  cat /proc/sys/net/ipv4/ip_local_port_range 
         Windows: NetSh INT IPV4 Show DynamicPort TCP

      Also, you would want TCP 32958 for ansoftrsmservice and whatever ports your selected MPI uses.



      "Determining memory availability"  is MPI related settings and most likely not firewalls.

      Some MPI related items to look when solving on remote Linux solves are:
      - using IMPI 2021 in RHEL8.x OS variants 
      - Passwordless SSH 
      - Environments to use the correct network (if multiple networks are available on each machine)
      - specifying the user/password in AEDT-Tools-Options-General Options-Remote Analysis

      Some MPI related items to look when solving on remote Windows solves are:
      - installing the correct Intel MPI version, creating the service
      - registering the user password on each machine
      - Environments to use the correct network (if multiple networks are available on each machine)
      - specifying the user/password in AEDT-Tools-Options-General Options-Remote Analysis

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