Troubleshooting
Fix offline simulation port 8000 already in use error
Short answer
The error means another program on your PC already listens on TCP 8000, the project's default inter-terminal communication port. End the leftover simulator process if Task Manager shows it; otherwise change the port on the Model tab of the project's system parameters and match it in every HMI-to-HMI partner project.
On this page
EasyBuilder 8000 refuses to start offline simulation because TCP port 8000 on your PC is already taken, and you cannot stop the program that holds it. The fix is in the project, not the registry: open Edit > System parameters, select the Model tab and set the inter-terminal communication port to any free number. Every project that talks to this terminal over HMI-to-HMI communication must be changed to the same number. If the holder turns out to be a leftover simulator process, the vendor's documented fix is even simpler: end com_e30.exe in Task Manager and run the simulation again. This article shows how to identify which case you have, how to pick a replacement port that will not collide later, and how to prove the change works with the other program still running.
What the port 8000 error means #
Port 8000 is the number EasyBuilder 8000 uses for communication between HMI terminals, and it is stored inside the project file, not in the operating system. When you launch offline simulation, the simulator starts the panel's runtime on your PC and opens a listening socket on that port. A TCP listening port can be held by only one program at a time, so when another application already listens on it, the simulator's bind fails and you get the occupied-port message before any screen runs. Nothing about your tags, screen objects or PLC driver settings causes this fault, and editing them cannot release the port. Two fixes exist, and the check in the next section tells you which one applies. Once simulation starts, it runs the whole project on the PC with no panel attached, which is the fastest way to exercise screen logic and the step that comes before testing HMI simulation against a live PLC.
Find the program that owns the port #
Windows lists every listening TCP socket with the ID of the process that owns it. Run netstat with the options for listening sockets and owning process IDs, and filter for the port:
netstat -ano | findstr :8000
An example line, with an illustrative PID, looks like this:
TCP 0.0.0.0:8000 0.0.0.0:0 LISTENING 2210
The last column is the process ID. Open Task Manager's Details tab, sort by PID and read the image name next to that number:
- If the image is com_e30.exe, a simulator process left over from an earlier session, use the first fix below.
- If the image is another application, such as plant software that must keep running, use the second fix.
Before you end any process, confirm what it is: on a PC that also talks to live equipment, killing the wrong service can drop a running connection.
Fix the leftover simulation process first #
If Task Manager shows com_e30.exe, the port is held by a simulation task that never released its socket. The vendor's FAQ for this exact error gives the documented procedure: close all open simulation windows, open the Processes tab of Task Manager, end com_e30.exe if it is present, and start the simulation again. No project setting changes, and the port stays at its default. If the error reappears on a later run, check the Processes tab again first, because a simulation closed without fully exiting can leave the process behind.
Move the inter-terminal port when another program owns it #
When the holder cannot be stopped or reconfigured, move the HMI listener instead of touching the other program. The port is not hidden in a registry key; it is a project setting:
- Save a copy of the project.
- Open Edit > System parameters and select the Model tab.
- Change the inter-terminal communication port to a free number.
- Confirm the dialog and save the project.
- Reopen the setting and read back the saved value before simulating.
Any free TCP port works. For a durable choice, use the dynamic range 49152–65535, which IANA's port number registry reserves for private use; the default sits in the registered range of 1024–49151, where software installed later can claim ports. Because the value travels with the project file, each project carries its own number, and changing this one leaves every other project untouched.
Keep every HMI-to-HMI partner on the same port #
A TCP client connects to an address and a port number, never to an application name, so every project configured to exchange data with this terminal must target the new port too. Open each partner project, find its HMI-to-HMI destination for this terminal and enter the same number. A mismatch does not reproduce this error; it produces the opposite fault, where simulation starts but the partner never connects. If inter-terminal traffic crosses a firewall between subnets, allow the new port through it. The controller connection is separate: the PLC driver, its serial or Ethernet parameters and its tag addresses stay exactly as they are.
Worked example: choose 49250 and prove it free #
The numbers below are an illustrative run on a PC where plant software, not a simulator, holds the port. netstat reports a listener on TCP 8000 owned by PID 2210, and Task Manager's Details tab shows the plant's production software, so the second fix applies. The candidate port is 49250. The range check is 49152 ≤ 49250 ≤ 65535, inside the dynamic range, which spans 65535 − 49152 + 1 = 16,384 ports. Repeating the check on the candidate, netstat -ano | findstr :49250, returns no line, so 49250 is free. Set the inter-terminal communication port to 49250 in Edit > System parameters (Model tab) and save. This project has one partner terminal that displays shared alarms, so that project's port is set to 49250 as well. Relaunch offline simulation with the production software still running: the simulator starts with no port message, and netstat now shows the production software still listening on 8000 while the simulator holds 49250.
Decision #
- If Task Manager shows com_e30.exe: close all simulation windows, end that process, and rerun offline simulation on the default port. Nothing in the project changes.
- If another program owns the port: set the inter-terminal communication port in Edit > System parameters (Model tab) to a free number, with 49152–65535 as the durable choice, set the same number in every HMI-to-HMI partner project, then rerun simulation with the other program still active. A clean start proves the conflict is gone.
- No registry edit belongs in either case; the port lives in the project file, and if a new number also reports occupied, the netstat check on that number takes seconds and the same fix applies.
Questions asked
Can two programs share TCP port 8000 on one PC?
No. A TCP listening port is held exclusively: the first program to open a listener owns it, and the second program's bind attempt fails, which is exactly the message you are seeing. It makes no difference that the two programs serve different purposes; the operating system allows one listener per address and port combination, so one of them has to move.
Which port number should I choose instead?
Any TCP port that is free now and stays free works. The dynamic range 49152 through 65535 is reserved for private use, so a listener placed there is least likely to collide with a registered service that starts later. Avoid numbers below 49152 that other installed software is known to use, and write the chosen value into the project notes so the next engineer finds it.
Do I need to change the PLC driver or tag addresses too?
No. The port on the Model tab is used for communication between HMI terminals, not for the controller connection. The PLC driver selection, its serial or Ethernet parameters and all tag addresses stay as they are. Only the projects that talk to this terminal over HMI-to-HMI communication need the new number.
Why does offline simulation need the port at all if no second HMI is configured?
Offline simulation starts the panel's runtime services on your PC, and those services open the project's inter-terminal listening port whether or not a partner terminal is configured. The bind happens at startup, before any screen logic runs, which is why an occupied port stops the simulation immediately.
The error came back after I changed the port. What now?
Close every simulation window first, because a previous simulator instance can still hold a socket, then check the Processes tab of Task Manager for com_e30.exe and end it. If both are clean, run the listening-port check on the new number itself: the replacement port may be claimed by something else, and the same fix applies to it.