Troubleshoot the EdgeCmd utility
- Last UpdatedFeb 28, 2025
- 1 minute read
To troubleshoot issues with EdgeCmd utility, you can start with the following troubleshooting tips. If you are unable to resolve issues with EdgeCmd utility or need additional guidance, contact AVEVA Customer Portal.
-
To get more information on proper usage of EdgeCmd utility, use the help command on a particular command and facet.
For more information, see Retrieve EdgeCmd utility help. -
Check if your adapter is using the default port number 5590.
-
If the adapter is using any other port number, include -port <AdapterPortNumber> as an argument in your command.
-
If you do not know what port to use, check the appsettings.json file in the directory where the adapter is installed.
-
-
Check if the adapter is running.
EdgeCmd utility makes REST calls against an active adapter. If the adapter is not running, there is nothing to respond to those REST requests.
-
If you run a command like Reset, add a data source configuration, edit a large data selection, or so on. Wait 20 to 60 seconds before you attempt to make more calls; the adapter needs time to process the request.
-
If a command is not working in EdgeCmd utility, verify the command does not work in other REST clients like Postman either.