KB483065: How to Troubleshoot Topology

Topology uses API calls to request from Workstation to I-Server. Engineers can use the following tips to troubleshoot topology-related issues:

1. If the Topology dialog is empty or blank, there should be an error handler/placeholder in the editor with useful error message of the issue. If there isn’t any,
2. Check if an environment is selected in the top left of the dialog.
3. Check if the connected environment supports the use of topology. Topology is supported in Strategy 11.0 and above. The phrase Not Available is seen in parenthesis next to the environment if topology is not supported.
4. Check that the user has adequate administrator privilege(s) to view/use topology in Workstation. To view or use topology, users must have the monitor and administer privileges under administrator.
5. If topology produces an error and cannot display the Topology dialog, check if the consul service is up and running. Try to restart the Services Registration service and try again.
6. If topology produces the error, No private IPV4 address found, confirm that consul is running. You can do this by running the IPCONFIG command to see the IP address being used. If consul is not running, make sure it is configured with the supported IP range. Consul does not start when the IP is not in 10, 192, or 172 range. To resolve, add "bind_addr":"IP" to consul.json
7. [Windows] If topology produces the error, An error occurred while sending the request. The request was aborted: The request was canceled in the Topology dialog, make sure Fiddler is disabled on the machine. This problem is due to using Fiddler at the same time as Workstation. There is a Microsoft issue with using certain network libraries/requests and Fiddler at the same time. The solution is to not use Fiddler or if you need to capture the traffic for debugging purposes, disable Fiddler’s cache headers.
8. Use Fiddler/Charles to debug and capture the error message to identify the root cause.

See our product documentation under following link Troubleshooting Topology for additional information.