Arriving at work and being met with a “connection could not be established” screen when trying to open Logo is one of the more stressful moments in a workday. Invoices can't be issued, orders can't be entered, and operations stall before the day even starts. The goal of this article is not to diagnose the issue — that isn't something that can be done remotely — but to help you ask the right questions in the middle of that panic, so you can tell apart what might be solvable on your own from what needs to be escalated, and gather the information that will speed things up once you reach support.
The one question to ask first: is it everyone, or just one user?
The first step when a connection error appears is to ask another user to try logging in at the same time. That single question splits the likely causes into two groups. If the problem affects only you, the cause is most likely tied to your own computer, session, or permissions. If everyone is affected at the same time, the cause is most likely in a shared component — the database server, the network, or the service layer. Skipping this distinction means any check you run afterward risks looking in the wrong layer.
Problems affecting a single user
If the problem is happening to only one person, the cause is usually specific to that user or that computer. The following are the areas to check first in this case:
- Session/user lock: A previous connection that dropped abruptly can leave the same user appearing as “still logged in”, causing the new login to be rejected.
- Local settings: Connection settings on the computer (such as server address or port) having changed or become corrupted can block a connection on that machine alone.
- Client installation: A missing or corrupted program file, or an update that didn't finish installing, can create a startup problem specific to that computer.
- Permissions: A user's access having been changed or revoked afterward can present itself as a message that looks like a connection error.
Problems affecting everyone at the same time
If the problem started for all users at the same time, the cause is not personal — it sits in a shared layer. In that case, these are the areas to check:
- Access to the database server: The server being down, unreachable over the network, or overloaded affects every user at once.
- The status of the relevant service: If the background service running the database engine has stopped for any reason, the application cannot reach the server at all.
- Network and DNS: The server name failing to resolve, or a break in network connectivity, can block the connection even when the server itself is healthy.
- Firewall: A recent change to a firewall or network policy can close off a connection path that used to be open.
- The server having been restarted: Overnight maintenance, an update, or a power outage after which the server hasn't fully come back up is a common cause of a connection error hitting everyone at once, first thing in the morning.
What a “connection error” actually means
A “connection could not be established” message does not mean the application itself has failed; it means the application cannot reach the database. This distinction matters, because in most cases the source of the problem is not the application itself, but the network or service layer between the application and the database. Rather than assuming “the program is broken”, the first step is understanding at which point the connection is being cut — and that is usually information visible to a system administrator or the support team.
License and session-related blocks
There is a general principle in client-server enterprise software: the system checks the defined number of concurrent users or the license/membership validation, and when that check fails, it can sometimes present the user with a message that resembles a connection error. A concurrent-user limit being full — for instance, because a session didn't close properly — is one such example. Whether something related to your LEM (Logo Enterprise Membership) membership is connected to this kind of block is something your technical team or reseller needs to check — rather than drawing a firm conclusion yourself at this point, the more reliable path is to include the exact wording of the message you saw in your support request.
Not opening after an update
If an update was applied recently and the program stopped opening afterward, the first possibility to consider is a version or client mismatch. If the server side was updated while the client side was left behind (or the reverse), the two sides may fail to recognize each other, and that can sometimes surface as a connection error. In these cases, the questions “when did it start” and “what changed beforehand” make diagnosis considerably easier.
Information to gather before opening a support request
Connection issues can range from something quickly fixable remotely to something that requires inspection on the server or network side. Whichever it turns out to be, having the following ready when you open a support request shortens the diagnosis time:
- The exact text of the error message: A screenshot or a verbatim copy is far more useful than a paraphrased summary.
- When the problem started: At a specific time, right after a restart, or during a particular operation?
- What changed beforehand: Was there an update, a maintenance job, a power outage, or a network/firewall change?
- How many users are affected: One person, a specific branch, or everyone?
When you shouldn't wait, and should call support directly
If the problem is affecting a single user and looks like a simple session lock, it is usually something that can be resolved quickly. But if the problem started for everyone at once, if the server can't be reached at all, or if the fix requires an operation on the database or the server, support should be contacted directly without losing time. Attempting fixes yourself in these situations — particularly around database or server settings — risks making the problem worse; the right move is to gather the information above and hand it to an expert.
iyibir's Logo support team first classifies connection-error reports by scope (a single user or everyone), then examines the database, server, network, and license layers together to pin down the source of the problem.