Troubleshooting
When AOA Manager shows server stopped after install
Short answer
Server Stopped in AOA Manager is a service state, not an install state: open services.msc and confirm AOANginx, AOANodeRed and AOAPython are running. A standalone Node-RED install proves nothing about them. On Windows 7 Embedded 32-bit, AOA 2.6 is outside its documented requirements, which start at 64-bit Windows 10 or 11 Professional and 16 GB of RAM.
On this page
- Why does AOA Manager show Server Stopped after a successful install?
- Which three Windows services decide whether the AOA server runs?
- What does a separately working Node-RED prove about the AOA server?
- Can Windows 7 Embedded 32-bit run AOA 2.6 at all?
- Why does AOA Manager open on the PC but not from the phone?
- What order do you fix things in, from services to the phone?
- What proves the AOA server is really back up?
- Questions asked
Server Stopped in AOA Manager is a service state, not an install state: open services.msc and confirm that AOANginx, AOANodeRed and AOAPython are running before you change anything else. A completed installer and a separately working Node-RED editor prove nothing about those services. On Windows 7 Embedded 32-bit the outcome is decided one layer lower, because release 2.6 lists 64-bit Windows 10 or 11 Professional as its starting point: move the runtime to a supported machine, then fix the phone connection in that order.
Why does AOA Manager show Server Stopped after a successful install? #
Because the installer finishing and the runtime running are different milestones: Server Stopped reports the state of the application's services, and AOA_2.6.0.1048 completing after the .NET Framework 4.6.2 update says nothing about whether those services started.
The framework update cleared the prerequisite that had been blocking setup, so installation succeeded. The next gate is service startup, and the manager's lower-left corner reports it bluntly: Server Stopped means at least one of the three runtime services is not up. The support guidance for that status points at exactly those services. The same gap between an installer that completes and a runtime the operating system will not carry is what you meet when a PLC runtime installer fails on the controller OS.
| What you observed | What it establishes | What it still leaves open |
|---|---|---|
| AOA_2.6.0.1048 installed after the .NET Framework 4.6.2 update | The prerequisite check passed | Service startup and OS support |
| node-v13.14.0-x64.msi installed, Schneider nodes run | One standalone Node-RED instance executes | Whether the AOANodeRed service serves the application |
| A server startup was indicated | A startup action occurred | The state of all three services |
| Server Stopped in the manager corner | The service summary is down | Which service, and why |
Which three Windows services decide whether the AOA server runs? #
AOANginx, AOANodeRed and AOAPython, all visible in services.msc: the Server Stopped state in the manager's lower-left corner maps to these three services, and any one of them not running holds the whole server down.
Type services.msc into Start search, open each AOA service's properties, and record its state, its startup type and its executable path. Then read the failure shape:
- Stopped, and a manual start refuses: dependencies, file access or the service account are blocking it.
- Starts and exits within seconds: startup is failing — configuration, a missing dependency, or a port conflict.
- Running while the corner still says Server Stopped: the fault has moved past the services, so test the configured manager URL directly.
Three services means three separate checks. Watching one process, or opening the standalone Node-RED editor, leaves the web-server and Python sides unchecked.
What does a separately working Node-RED prove about the AOA server? #
Nothing: node-v13.14.0-x64.msi running Schneider nodes in its own editor only proves that one standalone Node-RED instance executes, while the AOANodeRed service runs the application's own runtime with its own paths and configuration.
A Node-RED you installed by hand and the one behind AOANodeRed are different installations — different executable paths, different flow and settings files, and possibly different service accounts. Hand-picking another Node-RED release is not on the fix path for Server Stopped; version choice is a deliberate, tested decision, the discipline behind stable Node-RED gateway flows with vendor-pinned nodes.
There is also an architecture flag in that package name: x64 marks a 64-bit build, and a 64-bit binary does not execute on 32-bit Windows. Before trusting the report that the package installed, read the machine's actual architecture in System properties and the installed executable's details. Where a standalone instance is genuinely what you want, take the same care you would to install Node-RED natively on an edge computer.
Can Windows 7 Embedded 32-bit run AOA 2.6 at all? #
No: the documented requirements for release 2.6 start at 64-bit Windows 10 or 11 Professional, and a 32-bit installation cannot become 64-bit through any update, so this machine sits outside support before services or Node-RED enter the question.
The published requirement list for release 2.6 names Windows 10 or 11 Professional (64-bit), a 3.5 GHz Intel or AMD processor of 6 to 12 cores, 16 to 64 GB of RAM, and a 500 GB SSD. Run the memory arithmetic on the reported machine:
- A 32-bit address space spans 2^32 bytes = 4,294,967,296 bytes = 4 GiB, about 4.3 GB — and usable RAM is normally lower once hardware reserves its address ranges.
- The documented floor is 16 GB.
- 4.3 GB ÷ 16 GB = 0.27: the ceiling is roughly 27% of the minimum, a quarter, no matter which modules you fit.
Decision: stop tuning this installation and put the runtime on hardware that meets the list. When the old box is not worth rehosting, replace it with a fanless industrial mini PC running a supported 64-bit Windows and install there.
Why does AOA Manager open on the PC but not from the phone? #
Because the phone must reach the server's own address on a routable network, while a listener bound to the local computer, or a URL holding a loopback host, stops at the PC itself: fix binding and addressing before suspecting the application.
Record the configured manager URL — scheme, host, port where one is specified, path — and test that endpoint, not a Node-RED default. Then check what the box actually listens on: netstat -ano lists the listening sockets with their owning process IDs, and PowerShell's Get-NetTCPConnection -State Listen gives the same by address and port. A socket bound to 127.0.0.1 accepts nothing from a phone; it must bind the interface's address or all interfaces.
On the phone, keep the port and path but point the host at the server's reachable address — a URL starting with a loopback host names the phone itself. When the address is right and the connection still fails, work through listener binding, a scoped firewall rule, name resolution, and wireless client isolation, in that order. Read the browser's outcome the same way:
- Nothing loads, connection fails: listener or network path.
- A page loads with an application error: the application logs.
- A login is rejected: the request reached authentication, so work the account, not another Node.js installation.
What order do you fix things in, from services to the phone? #
Services first, endpoint second, network third: record the states of AOANginx, AOANodeRed and AOAPython, then test the manager URL locally, and only then test the phone path, so each step isolates one layer.
- Record the AOA release, the Windows edition and architecture, the configured manager URL, and the exact failure the browser reports.
- Open services.msc and log each service's state, startup type and executable path.
- Start any stopped service; if it exits again, read the matching Windows event and application log entry before restarting it.
- On a port conflict, identify the owning process with
netstat -anoand resolve it in configuration — moving a port without updating everything that references it creates a second failure. - Test the manager locally at the configured URL and log in.
- Test from the phone against the server's reachable address, working binding, the scoped firewall rule and name resolution in that order.
- Restart once, deliberately, in a maintenance window and confirm all three services come back on their own.
What proves the AOA server is really back up? #
All three services running after a restart, the manager page loading, and a login completing from the phone: the disappearance of Server Stopped alone is not evidence, because that status is only a summary of the service states.
Set the three services to Automatic so the server recovers from a power loss without someone logging in. Exercise the application's own function, separately from the standalone Node-RED editor. Keep the recorded URL, the service states and the event log entries from the failure: they are the baseline for the next incident, and they are the numbers you compare against, not a feeling that it seems to work.
Questions asked
Why did the AOA installer complete if Windows 7 Embedded is not supported?
An installer only enforces the checks it was written to make, and the .NET Framework 4.6.2 update satisfied the one that had been blocking AOA_2.6.0.1048. The runtime still has to start three services under an operating system the release was not built for, and that is where Server Stopped shows up. Treat installation and runtime support as separate gates.
What does it mean when AOANodeRed starts and stops again within seconds?
It means startup is failing, not that the service is beyond repair. Open Event Viewer and the application log, read the error attached to the exit, and check for a port conflict with netstat -ano before starting it again. Repeated blind restarts overwrite the evidence and change nothing.
Should I open the firewall completely to test phone access quickly?
No. Create one inbound rule scoped to the TCP port the manager endpoint uses, on the profile the phone traffic arrives on, and test with that. An any-port rule or a disabled firewall turns a five-minute test into a standing exposure on a plant-floor machine.
Can more RAM bring a 32-bit machine up to the AOA 2.6 requirement?
No. A 32-bit address space is 2^32 bytes, about 4.3 GB, so the ceiling sits near a quarter of the documented 16 GB floor no matter which modules you fit. The requirement also names a 64-bit operating system, which no memory change converts. The decision is a 64-bit machine.
What address should the phone use for AOA Manager?
The server computer's address on a network the phone can route to, with the same port and path as the local URL. Anything beginning with a loopback host such as 127.0.0.1 or localhost points the phone at itself. If the address is right and it still fails, suspect listener binding, an isolating wireless network or a firewall rule.