ANSYS EDT 2019 R1: Unable to locate COM engine with RSM analysis
One of our student subscribers has been setting up a remote compute node in the following manner.
Submit (user) node: Windows 10, 64-bit; ANSYS EDT 19.3
Remote (compute) node: Windows 10, 64-bit; ANSYS EDT 19.3
The following is his problem report. We have asked him if his group is using a job scheduler on the remote node, and await his reply.
Do you have any suggestions for him? A search of your Knowledge Base doesn't seem to have any directly relevant solutions if we type in search terms from his internal support case. He is using IP addresses for his network cards.
Our IT expert suggested that he turn off any firewalls between the two nodes. The 'ping' failure could be caused by the 'ping' feature being turned off (security?). We will have to confirm this to be true.
I have installed ANSYS EDT 2019 R1 on two Windows 10 systems. Both systems can run local analysis without issue. The 'remote' computer has port 3xxxx open. When attempt to run a remote analysis from the 'client' computer to the 'remote' computer, I receive this error:
"Unable to locate or start COM engine on '127.xxx.xxx.xxx' : no response from COM engine, timed out (2:59 PM Apr 08, 2019)"
When running a test of the machine from client to remote, I get the below;
"Checking Machine 127.xxx.xxx.xxx
Pinging machine 127.xxx.xx.xxx
Error: Unable to ping machine 127.xxx.xxx.xxx, Reason: Request timed out.
Checking AnsoftRSMService availability on machine 127.xxx.xxx.xxx
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 127.xxx.xxx.xxx : 3xxxx
AnsoftRSMService is configured to allow remote solves
Checking list of registered engines on machine 127.xxx.xxx.xxx
enscomengine:2019.1 is registered and available from Program Files/AnsysEM/AnsysEM19.3/Win64/ENSCOMENGINE.exe
EXTRACTOR2DCOMENGINE:2019.1 is registered and available from Program Files/AnsysEM/AnsysEM19.3/Win64/EXTRACTOR2DCOMENGINE.exe
HFIECOMENGINE:2019.1 is registered and available from Program Files/AnsysEM/AnsysEM19.3/Win64/HFIECOMENGINE.exe
HFSSCOMENGINE:2019.1 is registered and available from Program Files/AnsysEM/AnsysEM19.3/Win64/HFSSCOMENGINE.exe
ICEPAKCOMENGINE:2019.1 is registered and available from Program Files/AnsysEM/AnsysEM19.3/Win64/ICEPAKCOMENGINE.exe
MAXWELL2DCOMENGINE:2019.1 is registered and available from Program Files/AnsysEM/AnsysEM19.3/Win64/MAXWELL2DCOMENGINE.exe
MAXWELLCOMENGINE:2019.1 is registered and available from Program Files/AnsysEM/AnsysEM19.3/Win64/MAXWELLCOMENGINE.exe
MECHANICALCOMENGINE:2019.1 is registered and available from Program Files/AnsysEM/AnsysEM19.3/Win64/MechanicalComEngine.exe
Q3DCOMENGINE:2019.1 is registered and available from Program Files/AnsysEM/AnsysEM19.3/Win64/Q3DCOMENGINE.exe
RMXPRTCOMENGINE:2019.1 is registered and available from Program Files/AnsysEM/AnsysEM19.3/Win64/RMXPRTCOMENGINE.exe
SimplorerCOMEngine:2019.1 is registered and available from Program Files/AnsysEM/AnsysEM19.3/Win64/SimplorerCOMEngine.exe
desktopjob:ElectronicsDesktop2019.1 is registered and available from Program Files/AnsysEM/AnsysEM19.3/Win64/desktopjob.exe
nexxim:2019.1 is registered and available from Program Files/AnsysEM/AnsysEM19.3/Win64/nexxim.exe
spexporter:2019.1 is registered and available from Program Files/AnsysEM/AnsysEM19.3/Win64/spexporter.exe
Checking for jobs running registered engines on machine 127.xxx.xxx.xxx
There are no jobs running registered product engines on this machine
Error: Some tests have failed. "
I believe the ping test failure isn't an issue?
Any suggestions on what could be the issue?