Exata is working from commandline but not from GUI. How can I fix it?
Article If Exata 2.0.1  is working from command line but not from GUI, the likely reason is that GUI is not able to connect on the port. The error occurs when the GUI is attempting to create a socket server on port 4000 so that it can animate events from the simulator and gets a clash. This is no longer a problem in GUIs version Qualnet 5.0 and later, because the GUI in 5.0 will simply ask the user to specify another port to use.

The work around for Exata 2.0 would be to kill the exata command line process running in the background that is likely taking up port 4000 already. Or it
 could be that another service is operating on 4000, in which case that process would have to be terminated or forced to run on another port. Please check
 what is operating on port 4000 and free up the port.

Article Details
Article ID: 65 Created On: 20 Jan 2010 3:01 PM

This article was helpful  This article was not helpful

 User Comments Add a Comment