Troubleshooting

Note:

Functionality featured in the example(s) in this section applies to multiple design types.

Problem:

When you try to solve from local to remote machine, a COM engine process starts on the remote machine, but the user interface hangs indefinitely.

This occurs if the remote solve option is enabled after the COM daemon is started, or when the option "Don't allow exceptions" is selected for the Windows firewall.

Resolution:

Remote solve needs either firewall exceptions to be turned on, or firewall to be completely turned off.

 

Problem:

When you try to solve from a local to a remote machine, you receive the following error message:

[error] Unable to locate or start COM engine on 'nomachine' : Unable to reach AnsoftRSMService. Check if the service is running and if the firewall allows communication. (10:57:13 PM Aug 13, 2019)

Resolution:

This message can happen if the machine is not present, the network connection is down, if there are firewall issues, or if the service is not running.

 

Problem:

A solve that is distributed to multiple hosts using MPI fails because the AnsysEM installation path is different on different hosts.

Resolution:

Ansys Electronics Desktop must be accessible from all remote machines as well as on the local machine. If the analysis uses MPI, then the path of the Ansys Electronics Desktop installation must be the same on all of the machines used for the analysis (remote and local). This may be a shared network path accessible from all hosts. Alternatively, it may be a local installation on each host; in this case the installation path must be the same for all hosts. If using a shared network path, there should not be a local installation of the same Ansys Electronics version on any of the hosts. See Distributed Analysis for information on whether MPI is needed for the analysis.

 

Problem:

The command ansoftrsmservice stop will not work as root.

Resolution:

Use systemctl command to stop the service:

sudo systemctl stop ansoftrsmservice

Remote Solve Node = Windows

Error:

"Unable to locate or start COM engine on <remote node> : Unable to reach AnsoftRSMService. Check if the service is running and if the firewall allows communication."

Resolution:

  1. Try disabling the firewall.
  2. Confirm that you have not changed the Service Port in Tools > Options > General Options > General > Remote Analysis. If you have, change it back to the default (32958), restart Ansys Electromagnetics Desktop, and try to solve again.
  3. Make sure that the local machine is able to contact the RSM port on the remote node. Open a command prompt on the local machine and type:
    telnet <remote node name> 32958
    If the terminal appears to hang, the connection was successful.
  4. Make sure the user listed in the service is an administrator.
  5. Make sure the COM engine is registered with the RSM Service. From the Windows menu, choose Start > All Programs> Ansys EM Suite 2024 R2 > Register with RSM to register the engines.
  6. If none of these steps fixes the problem, contact Ansys Support.

 

Error:

"Unable to locate or start COM engine on <remote node>: Engine is not registered with the Ansoft RSM service which is running on this machine."

Resolution:

  1. To register the engine from the Windows menu, select Start > All Programs > Ansys Electromagnetics Suite 2024 R2 > Register with RSM.

Remote Solve Node = Linux

Error:

"Unable to locate or start COM engine on <remote node>: Unable to reach AnsoftRSMService. Check if the service is running and if the firewall allows communication."

Resolution:

  1. Try disabling the firewall.
  2. Confirm that you have not changed the Service Port in Tools > Options > General Options > GeneralRemote Analysis. If you have, change it back to the default (32958), restart Ansys Electromagnetics Desktop, and try to solve again.
  3. Make sure that the local machine is able to contact the RSM port on the remote node. Open a command prompt on the local machine and type:
    telnet <remote node name> 32958
    If the terminal appears to hang, the connection was successful.
  4. Check to make sure Remote Simulation Manager is running.

    To do this:

    1. Go to the rsm subdirectory of the Remote Simulation Manager installation directory, <RSM installdir>/rsm.
    2. Type
      ./ansoftrsmservice status
    3. If the status query indicates that the service is stopped, type ./ansoftrsmservice start.
  5. Make sure the COM engine is registered with RSM. Type:
    ./RegisterEnginesWithRSM.pl status
    from within the Electronics Desktop installation directory. If the status query indicates "Not registered", type:
    ./RegisterEnginesWithRSM.pl add
  6. If none of these steps fixes the problem, contact Ansys Support.

 

Error:

"Unable to locate or start COM engine on <remote node>: Engine is not registered with the Ansoft RSM service which is running on this machine."

Resolution:

  1. To register the engine, go to the Ansys Electromagnetics product installation directory and type:
    ./RegisterEnginesWithRSM.pl add