Pilot installed on Mac launches a task, but seems to lag. You can select the file and launch with the workflow but it takes 3-6 minutes for the task to show in the Task Monitor and start the workflow.
The Pilot launches on other Mac computers and works fine. This problem is related to only one Mac computer.
The Pilot on a specific Mac lags and is slow. The Automation Engine server can not ping the Mac by name (open Command window and type
When you are using a DNS server, your IT department should register the Automation Engine Server computer and the workstations in the DNS server (also reverse DNS should be done!).
- First check if there is a DNS server configured:
- Open the Command window on the Automation Engine Server.
- If there is a DNS Server, check if the DNS Server is inside the LAN or outside the LAN.
- If the DNS Server is outside the LAN, go to step 5.
- If the DNS Server is inside the LAN, check if the computer is registered in the DNS Server:
- Open Command window.
If it is registered it will show name and address in the next line. If not it will show the name of the DNS Server and a message that the compute rname can't be found:
- The workaround is to adapt the
hostfile on the Automation Engine server.
- Modify the
hostswith WordPad file on the Automation Engine server.
- Browse to
- Right click the
hostsfile and open with WordPad.
- At the bottom of the file, add the IP address of the Mac then tab and add the computer name of the Mac (find it in System Preferences > Network > Sharing).
If the Automation Engine server is not registered in the DNS, then add to the
hostfile, the IP address and Name of the Automation Engine server.
On the Mac, add to the
hostfile all IP addresses and names of the Mac workstations and the Automation Engine server. Learn here how to edit the
hostfile on Mac:
DHCP is only allowed if the IP address is reserved!
- Browse to
Automation Engine all versions