Skip to main content
The tray app is the ERP Sync agent’s face on the computer it runs on. It shows what the Windows service is doing and lets you act on it. It does no work itself: closing it does not stop the service, which carries on in the background.

​
Start the tray app

The tray app starts by itself for everyone who signs in to the agent computer. The service also starts it for everyone who is signed in after an installation or an update. Its icon, a database, sits in the notification area next to the clock. If you do not see it, click the Show hidden icons arrow. To start it by hand, open Omnilinker ERP Sync from the Start menu. Only one copy runs at a time. Starting it again opens the running copy’s panel. To close the tray app, right-click its icon and select Exit ERP Sync (Hide the tray icon on an agent not yet updated). Sync keeps running in the background, and the icon comes back when you sign in again or when the ERP Sync service restarts. To stop the agent’s work, pause it, or stop the Windows service: Stop-Service OmnilinkerErpSyncService in PowerShell as Administrator. The tray app follows the Windows display language: Polish on a Polish Windows, English otherwise.

​
The icon

The icon is a database with a small badge. The badge’s shape tells you the state, so you can read it without colour: Hover over the icon for one line about the connection, for example Up to date or Can’t reach the Wapro database.

​
The panel

Click the icon to open the panel above it. Click the icon again, press Esc or click elsewhere to close it. From top to bottom it shows:
  • The connection: its name in Omnilinker, the company, and the ERP on its server, for example Pinio · Wapro Mag on SERWER\WAPRO. Only an operator of this computer sees the server; anyone else sees Pinio · Wapro Mag (see Who can do what). The gear opens Settings.
  • How the agent is doing, in one sentence, with the one thing to do about it when something is wrong. For example Can’t reach the Wapro database. says how long the server has not answered, and offers an operator Test the connection and Connection settings (Troubleshoot instead, for anyone who is not an operator).
  • Connections: Omnilinker and the ERP database, each Connected, Unreachable, Slow or Checking…, with the server and how fast it answered. Anyone who is not an operator sees Visible to operators only instead of the database’s server. The database row can also show the state of the agent’s connector, for example Not started, Starting, Resting, Restarting or Needs attention (see Settings > Connector).
  • What syncs: one line about what the agent does with your ERP: “Prices sent from Omnilinker are written to ‹ERP›, and its lists of price levels, warehouses and products are read so you can map them in Omnilinker.” Prices are written only when someone sends them. The line doesn’t mention stock or prices, which the agent also reads (see Wapro and How prices are read).
  • Pause sync (Resume sync while paused).
  • Open in Omnilinker opens this connection in your browser, and Troubleshoot opens Troubleshoot. The agent’s version is on the right.

​
Pause

Pause sync stops the agent’s work in your ERP until you select Resume sync: while paused, it writes nothing to your ERP and reads no lists, stock or prices from it. Its periodic check of the ERP connection still runs, so it may still connect to the ERP database. A pause does not survive a restart of the service. Only an operator can pause; anyone can resume.

​
Right-click menu

​
Notifications

The tray app shows a Windows notification only when the agent needs someone:
  • Can’t reach the Wapro database. or Can’t reach Omnilinker., once the problem has lasted two minutes. A database restarting at night does not raise one.
  • Omnilinker doesn’t accept this PC., when this computer’s key stopped working. Connect again opens setup.
  • Nothing is written to the ERP until ERP Sync updates., when Omnilinker needs a newer version of the agent. The agent updates itself overnight, or use Install now in Settings.
  • Wapro needs attention, when the agent’s connector to the ERP needs someone, for example because it keeps stopping. Troubleshoot shows why.
Turn them on or off in Settings > On this PC > Tell me when sync needs attention. The choice is yours alone: each person signed in to the computer sets their own.

​
Troubleshoot

Troubleshoot checks everything the agent needs, right now:
  • the ERP Sync service on this computer,
  • whether Omnilinker can be reached, and how fast,
  • whether Omnilinker still accepts this computer,
  • the agent’s connector for the ERP, for example Wapro connector: its state and version, and what its last check found (Wapro connection checks), or Not checked yet,
  • the agent’s version and whether an update is ready.
For Wapro, Troubleshoot can also show a warning row (not a failure) Old registration in Wapro’s change tracking: Present. An earlier Omnilinker agent registered itself in Wapro’s change tracking, and Wapro still writes a change row for every article change that nobody reads. The row has nothing to press; its hint points to the SQL in Removing the old registration, which your database administrator or Wapro partner runs. If the agent cannot read that table, the row doesn’t appear. Two more warning rows concern product images: Where Wapro keeps product images: In an image folder (disk mode) (images in that folder are not read) and Daily check of image contents: Off (SQL Server older than 2016) (an image replaced by one of exactly the same size is not noticed). See How product images are read. Problems come first. The first one is shown as a card with what to do and a button for it, such as Connect this PC, Connection settings, Restart connector, Restart service or Repair. Check again repeats the checks. Only an operator of this computer gets the buttons that change the agent. Anyone else sees “Only an administrator of this PC or a member of “Omnilinker ERP Sync Operators” can change this.” in their place. When the connector’s check fails, only an operator sees its details, because they can name the server. Copy report copies what was checked and found, for Omnilinker support or your IT. The report has no passwords, keys or ERP data in it. Open logs folder opens the service’s log files. See Troubleshooting for specific problems.

​
Settings

Settings has these sections:
  • This connection: the connection this computer serves, its company and ERP, and Open in Omnilinker. Connect to another company… runs setup again, which replaces this connection.
  • The ERP database (for example Wapro database): Server, Database, Sign in with and the Company number. Anyone who is not an operator sees Visible to operators only instead of the server, database, user and company. Change… opens the connection form (the same as in setup): a change is saved only after a Test connection that passed, and after you change Server, Database or User, the form asks for the password again. Test connection checks the saved settings through the connector, so it needs an operator too.
  • Connector: the part of the agent that connects to the ERP database. It shows its State, its Version, Restarts in 24 h, its Last exit (operators only), when it was last Checked, and the Lists it sends to Omnilinker (Price levels, Warehouses, Products, Stock, Prices, and Orders sent from Omnilinker). Check connector starts it if needed and checks it now, showing each step as it goes. Restart restarts it. Refresh lists reads every list and the stock from the ERP now and sends them to Omnilinker, then says what arrived, for example “Lists refreshed. Price levels: 2 · Warehouses: 1 · Products: 6 · Stock: 120”; while it reads stock, the step says “Reading stock”, while it reads prices, “Reading prices”, and while it reads the orders sent from Omnilinker, “Reading orders sent from Omnilinker”. The prices are read, and have a step, only while Omnilinker asks for them (see Prices), and the orders only while the connection has sent an order in the last 90 days. All three need an operator.
  • On this PC: Tell me when sync needs attention. See Notifications.
  • Updates: the agent’s version, and whether a newer one is downloaded. Updates install overnight. Install now installs a downloaded update straight away when nothing is running. Check now looks for one.
Open logs folder at the bottom opens the service’s log files.

​
Who can do what

Everyone signed in to the agent computer can see how the agent is doing in the tray app, and can use Resume sync, Check again in Troubleshoot and Check now for updates. Where the ERP database is, is for operators only: the server, the database, the SQL Server user and the company number. Anyone else sees Visible to operators only in their place. The connector’s last exit and its check details are for operators only too. These change the agent, and need a member of the local group Omnilinker ERP Sync Operators or an administrator:
  • setup, changing the ERP database, and Test connection,
  • Pause sync,
  • Check connector, Restart and Refresh lists in Settings > Connector,
  • Install now for an update.
Anyone else sees “Only an operator of this PC can do this: a member of “Omnilinker ERP Sync Operators”, or an administrator.” A person just added to the group must sign out of Windows and sign in again first. See Who can change the agent.