System status and license
Sometimes Xchange locks something: a button is gray, a run does not start, a change cannot be saved. Usually there is a state behind it that Xchange shows with a name and a reason. This page says which states exist and what each of them means for your work.
Three things that are locked separately
Xchange distinguishes what you are trying to do:
| What is meant by it | |
|---|---|
| Reading | Viewing routes, connections and value tables |
| Changing | Working on the configuration and activating a snapshot |
| Executing | Starting runs and processing jobs |
A halt locks specific ones of these three. In most stopped states you can still look at what is configured — you just cannot set anything in motion. Which state releases which of the three is described on System Status.
When everything is running, all three are open. That is the state Operational, and that is where a system normally is.
Why Xchange prefers to stop
Xchange stops as soon as it has doubts about whether it would work correctly — for example because the database fits a different version or because a piece of information that routes rely on is out of date.
This spares a target system from wrong data. A stopped system catches up; a target system that was supplied wrongly would have to be corrected by someone by hand.
That is why: A halt waits for an action and ends only with it. Every halt states on System Status what it is waiting for.
The license locks only executing
The license is the second reason something is locked — and it acts more narrowly than a halt: it locks only executing. Reading and changing stay open, whatever the state of the license.
A run starts only in two license states: Valid or Grace period. Every other state locks new runs — including the two that merely report that a check did not take place.
In the grace period the license portal is currently unreachable for Xchange. The license itself is fine. Work continues, and the notice names the remaining days. If the portal is reachable again by then, the grace period ends without consequences.
What the license locks is told to you by the screen you are on: a run that fails because of the license says so when you try to start it — the reason for it is on System Status.
The waiting state after a change to the database
When Xchange has changed something in the database — during setup or an update — it then waits for the SAP Business One Service Layer to be restarted.
The Service Layer remembers which structures exist in the database and learns about the change only through the restart. Until then, processing stays stopped.
How you see that the restart is done:
| Before | After |
|---|---|
| Operating state Processing Stopped | Operational |
| Database Restart pending | Up to date |
Between the two lies a button: after the restart you confirm it on System Status, and only this confirmation completes the procedure. The way is described in Run a database update.
How you notice a halt
A halt reports itself. It appears on the Overview under Action required — with the reason, where one is known, and a jump to System Status.
Three things can be behind a gray button:
- The action requires a permission that you are missing.
- The action currently fits a different state.
- A halt locks the reading, changing or executing that the action belongs to.
Only the last case appears under Action required.
See also
- Run a database update (guide) — the way out of the most common halt
- System Status (reference) — every state, every reason and what it releases
- Permissions (core concept) — the other reason something is locked