Skip to main content
Start with the quick checks, then open the entry that matches what you see. Run the PowerShell commands on the agent computer.

​
Quick checks

In Omnilinker, open ERP Integration > Connected systems, open the connection and check its PC and connector tab (see Monitoring) and the Lists from ‹ERP› card on its Overview tab (see Lists and mappings). ERP Integration > Overview lists what needs you, worst first. On the agent computer, the tray app’s Troubleshoot… checks everything the agent needs and says what to do first.

​
Common problems

The Windows service writes one file per day and keeps the last 30:
That is usually C:\ProgramData\Omnilinker\ErpSync\logs. Everyone signed in to the computer can read it. To follow today’s file:
In the tray app, Open logs folder in Settings… or Troubleshoot… opens the same folder.Setup log. Setup, updates and uninstalling write what they could not do to setup.log in the same folder. See Setup finished, but there is no service.The agent does not write its own messages to the Windows event log. Windows records service start failures in the System log (see the next entry).
Get-Service OmnilinkerErpSyncService shows Stopped, or the service stops shortly after it starts. The tray icon shows a red square, and its tooltip says The ERP Sync service isn’t running.The service is set to restart itself after a failure (after 5, 10 and 30 seconds), so a service that keeps stopping has a problem that a restart does not fix.
  1. Open Event Viewer > Windows Logs > System and look for errors from the source Service Control Manager that name Omnilinker ERP Sync (Omnilinker ERP Sync Service on an installation made with install-service.ps1). For a crash, also check Windows Logs > Application for .NET Runtime or Application Error entries.
  2. Open the newest service log file (see Where are the logs?). If the service started far enough to log, the last lines say why it stopped. A fatal start-up error ends with Omnilinker ERP Sync Service terminated unexpectedly.
Common causes:
  • Logon failure. Someone changed the service to run under another account, and its password changed. The System log says the service did not start due to a logon failure. Open Services, open Omnilinker ERP Sync > Log On, select Local System account and click OK. The agent is designed to run as Local System.
  • The data folder cannot be written. The log says ERP Sync cannot write its data folder. The service must be able to write %ProgramData%\Omnilinker\ErpSync; check that nobody changed the folder’s permissions, or run Repair from the tray app’s Troubleshoot….
  • Broken appsettings.json. If you edited it, check that it is still valid JSON. From the install folder:
    An error means the file is not valid. Fix it or restore it from the original package.
Start the service again after a fix, in PowerShell as Administrator:
Setup completed, but Get-Service OmnilinkerErpSyncService finds no service, or the tray app does not start at sign-in. Setup never fails because of one step; it writes what it could not do to %ProgramData%\Omnilinker\ErpSync\logs\setup.log:
If there is no setup.log at all, setup could not even create the folder. Run it again as an administrator.
The tooltip says The ERP Sync service isn’t running, or setup shows “The Omnilinker ERP Sync service isn’t running.” or “The Omnilinker ERP Sync service is running but doesn’t answer.”
  1. Open Troubleshoot… in the tray app. When the service does not answer, it looks at the Windows service itself and offers the fix that fits, with an administrator’s approval:
    • Restart service, when the service is stopped, or running but not answering.
    • Repair, when the Windows service is missing or runs another copy of the agent. It sets the service up again for this installation and keeps the connection and its settings.
    On a copy not installed with the MSI, it offers Open Windows services instead. If the service keeps stopping, see The service does not start.
  2. If the tray app shows “Something other than the ERP Sync service answered. Restart the PC; if it happens again, contact support.”, another program answered on the agent’s pipe. The tray app talks only to the Windows service. Restart the computer.
  3. If it says “This app and the ERP Sync service don’t match (one of them was updated).”, right-click the icon, choose Exit ERP Sync (Hide the tray icon on an agent not yet updated), then start ERP Sync again from the Start menu.
You can see the agent’s status, but setup, changing the database, pausing, or Check connector, Restart and Refresh lists in Settings fail with “Only an operator of this PC can do this: a member of “Omnilinker ERP Sync Operators”, or an administrator.” The tray app may also show those buttons greyed out, and Visible to operators only instead of the database server and name. That is expected for anyone who is not an operator.Ask an administrator of the computer to add you to the local group Omnilinker ERP Sync Operators. Then sign out of Windows and sign in again: Windows reads your groups when you sign in, so the membership counts only after that. See Who can change the agent.An administrator can also close the tray app (Exit ERP Sync, or Hide the tray icon on an agent not yet updated) and start it again with Run as administrator.
Offline means Omnilinker has not received a heartbeat for more than 3 minutes. The PC’s line says since when it is off, and Last heartbeat under Technical, for support shows when the last one arrived. A running, accepted agent sends one every 60 seconds.Work through these in order:
  1. Is the service running? See The service does not start.
  2. Can the agent reach Omnilinker? See The agent cannot reach omnilinker.pl.
  3. Is the connection switched on? On ERP Integration > Connected systems, the connection’s status must not be Switched off. Omnilinker accepts nothing from the agent of a switched-off connection. To switch it on, click Switch on in the row’s menu.
  4. Does Omnilinker still accept the agent’s key? See Omnilinker doesn’t accept this PC.
If the tab says “No PC is connected to this connection yet.”, the agent has never reached Omnilinker with this connection’s key. Complete setup on the agent computer.
The tray icon shows a red square and the panel says Omnilinker doesn’t accept this PC. The agent’s log shows, repeatedly, that authentication failed for the connection with Status: Unauthorized.The agent’s key no longer works. Most often another computer was connected to the connection with a code, or this computer was connected again elsewhere: connecting a computer replaces the connection’s agent key straight away. The connection may also have been deleted.Connect this computer again:
  1. In Omnilinker, open the connection and get a connection code with Connect a PC. See Get a connection code.
  2. On the agent computer, click Connect again in the tray app’s panel (or Settings… > Connect to another company…) and complete setup with the code.
After an update from an older version, setup can also open because the agent no longer finds its connection where the older version kept it. Connect it again the same way.
Omnilinker can require a minimum agent version. When your agent is older, Omnilinker still takes its heartbeat and tells it to update, and the agent holds everything that would change the ERP or read from it until it does.What you see:
  • In Omnilinker, the connection’s PC and connector tab shows the PC online, and a banner says ERP Sync on the PC needs an update, with your version and the one Omnilinker requires. On Home, the ERP card counts the connection under ERP writes held: the agent needs an update and names it.
  • In the tray app, the panel says Nothing is written to the ERP until ERP Sync updates., and Windows shows a notification that says the same.
  • The ERP’s lists (price levels, warehouses, products) and prices are not read. A Refresh lists you start in Omnilinker waits for the update, but Omnilinker offers it to the agent for one hour only. If the update comes later than that, click Refresh lists again afterwards.
  • In the agent’s log, a warning: Omnilinker requires ERP Sync <minimum> or newer; nothing is written to the ERP and no list is read until it updates.
The agent updates itself at night when a newer version is published, so this should clear by itself. If it does not, check that automatic updates are on (AutoUpdateEnabled) and that the agent computer can reach releases.omnilinker.com, or run the new installer by hand. Once the agent runs a supported version, its next heartbeat ends the hold.While the agent waits for an update, prices you send from Omnilinker wait (Pending in the product’s ERP prices, Waiting under ERP Integration > Commands) and expire after 24 hours, the ERP unchanged, and whoever sent them is told; send them again once the agent has updated. See Prices to your ERP.
In the tray app, the icon shows a red square and the panel says Can’t reach Omnilinker. Troubleshoot… shows No answer for omnilinker.pl reachable.
  1. Test the connection from the agent computer:
    TcpTestSucceeded : False means a firewall or the network blocks it. The agent needs outbound HTTPS to omnilinker.pl on port 443. See Requirements.
  2. If your network requires a proxy, set it for the machine with the HTTPS_PROXY environment variable, then restart the service. The service runs as Local System, so it does not use the proxy settings of the person signed in:
  3. Check which server the agent uses: Troubleshoot… names it in the reachable check. It should be omnilinker.pl. To change it, run setup again and click Change next to Server.
While Omnilinker cannot be reached, the agent keeps working from its last downloaded configuration.
In the tray app, the icon shows an amber triangle and the panel says Can’t reach the Wapro database., or the connector’s check in Settings > Connector fails at Reach the database or Sign in to the database.An operator opens Settings… > Change… and clicks Test connection: the service starts the connector with the settings in the form and shows each step. It runs inside the Windows service, with the service’s account, so it behaves the same way as the agent. Troubleshoot… shows the connector’s last check too; only an operator sees SQL Server’s own message, because it can name the server.The server cannot be found. The Reach the database step fails.
  • Check Server. For a named instance use server\instance, for example erp-server\WAPRO.
  • Check that the agent computer can reach the SQL Server port:
    Use your instance’s port if it is not 1433. A named instance with a dynamic port also needs the SQL Server Browser service and UDP port 1434.
Login failed. The Sign in to the database step fails.
  • SQL Server login: check the user and password, and that SQL Server allows SQL Server authentication (mixed mode).
  • Windows account of the service: the agent logs in as the service’s account, Local System, not as you. That is the agent computer’s domain account (DOMAIN\COMPUTER$) on a remote SQL Server, or NT AUTHORITY\SYSTEM on SQL Server on the same computer. Give that account a login and the rights in Requirements, or use SQL Server authentication.
Certificate errors. The connection is encrypted when Encrypt the connection is ticked, or when SQL Server requires encryption, and most SQL Server installations use a self-signed certificate. Either install a certificate on SQL Server that the agent computer trusts, or open Settings… > Change…, tick Trust the server’s certificate under Advanced, test and save.
The connection form’s test, or the connector’s check in Settings > Connector, fails at one of these steps:
  • Wapro price procedure installed: the database has no dbo.Api_ProductPriceModify, or the SQL login may not execute it (SQL Server hides a procedure from a login without the right, so both look the same). Grant the login EXECUTE on it. See Requirements.
  • Company chosen: the company number is missing, or names a company that has no warehouse in this database. Enter the right Company number in Settings… > Change…. See Wapro.
The form saves only after a test that passed.
The Lists from ‹ERP› card on the connection’s Overview tab shows a list as not read yet, or says ERP Sync has not reported any list this connection’s connector sends., or Refresh lists answers “The Wapro Mag connector on this connection does not send any lists.”Check, in order:
  1. Is the agent online? See The PC and connector tab says Offline.
  2. Does the agent need an update? See Omnilinker requires a newer agent: an agent waiting for an update reads no lists.
  3. Is the connector ready? On the PC and connector tab, the connector’s state should be Ready, and its operations should include Read price levels, Read warehouses, Read products and Read stock, and, once orders are sent, Read orders sent from Omnilinker (the agent reads those only while the connection has sent an order in the last 90 days). An operation marked switched off means a check failed; its hint says which.
  4. Is the company number set? Without it the Wapro connector reads no list. See Wapro.
  5. Is the agent paused? A paused agent reads no lists. Resume it from the tray app’s panel or menu.
Then click Refresh lists on the connection’s Overview tab, or have an operator click Refresh lists in the tray app’s Settings. The tray app says which lists reached Omnilinker.
Stock Levels has no ERP stock column, a cell says not read yet, a cell shows —, or the age beside the figures is amber. Check, in order:
  1. Is the agent from this release? An older agent sends no stock at all; the Lists from ‹ERP› card shows no Receives stock line. See Omnilinker requires a newer agent.
  2. Is a warehouse mapped? Wapro stock is read every 5 minutes only while a warehouse of the connection is mapped; otherwise it is read once a day. Map the warehouse on the Warehouses and products tab.
  3. Is the warehouse ignored, or mapped more than once? An ignored ERP warehouse shows no stock, and so does an Omnilinker warehouse that more than one ERP warehouse of the connection is mapped to.
  4. Is the product linked? Stock appears only for products linked to an ERP product on the connection. See Link products.
  5. Is the pair in the ERP’s last list? A product the ERP no longer lists in a warehouse reads 0, marked “not in the ERP’s last list” (a stock line deleted in Wapro reads an unmarked 0 until the agent’s daily complete list).
  6. Is the agent paused, offline or updating? A paused agent reads no stock. See The PC and connector tab says Offline.
The PC and connector tab shows Read stock among the connector’s operations; if it is marked switched off, the hint says why (the same checks as for the lists). On a warehouse Omnilinker manages, ERP stock is shown for comparison only and does not change your own stock levels; on a warehouse your ERP manages, it is the warehouse’s stock.
The Lists from ‹ERP› card on the connection’s Overview tab shows a Prices line (Receives prices) once a price level of the connection is mapped. It can say:
  • reading prices is off for this account: Read prices from the ERP is off for your organization, so Omnilinker has not asked the agent for prices. It is off until Omnilinker switches it on; ask Omnilinker. See Prices and Modules and feature availability.
  • Update the ERP Sync agent to read prices: the connection’s agent is older than the release that reads prices, and its connector does not report Read prices among its operations on the PC and connector tab. Update it; see Omnilinker requires a newer agent.
The line is hidden while no price level of the connection is mapped.
Not compared yet means the comparison has not run since reading started. It runs a few minutes after the first prices arrive, and once a day. If it stays, or the time beside Compared with ‹ERP› at stays old, check, in order:
  1. Is a price level mapped? Prices are read only while a price level of the connection is mapped to a catalog price level. See Price levels.
  2. Is reading prices on for your organization? If the Prices line says reading prices is off for this account, it is not. See the previous entry.
  3. Is the agent from this release, online and not paused? A paused or offline agent reads nothing. See The PC and connector tab says Offline.
  4. Did Omnilinker support set the lists the agent reads by comparison? If the list in Configuration reference does not include Prices, the prices are read only with the daily complete read. Add Prices to it, one environment variable for each entry (ErpSync__Feeds__DiffStreams__2, and so on), as the page shows.
  5. Is Read prices switched off on the PC and connector tab? If the connector’s operation is marked switched off, the hint says why (the same checks as for the lists).
A product appears in the comparison only if it is linked to an ERP product on the connection. See Link products.
On the PC and connector tab, the connector’s Checks list Same prices in every warehouse with a hint. It is information: nothing is switched off and the connection works. It means your Wapro company has more than one active warehouse and Wapro does not keep an article’s price equal across them, so Omnilinker reads, and sends prices to, the article’s row in the main warehouse only. To keep the warehouses equal, set the company’s article synchronisation (SynchroArt) to “Wspólne dane i ceny podstawowe” in Wapro and turn synchronisation on for every price level. If the SQL login lacks the optional SELECT on ARTYKUL_CENA_IE, POZYCJAKONFIG and INTERFIRMAPOZYCJA, the check cannot tell, and it still shows with its hint: in the tray app its detail starts with “Not checked” and names the three tables, and the agent’s summary says the prices of the warehouses were not checked rather than that they may differ. Grant the SELECT and the next check tells; see Requirements. See How prices are read.
Open the product’s ERP prices (or the send’s result) to see its status, and ERP Integration > Commands for the command behind it. Failed names the reason, Not confirmed means Wapro may or may not have stored the price (check Wapro before you send it again), and Expired means the agent could not write it within 24 hours. See Prices to your ERP and When a price cannot be sent.
The tray app says “This ERP Sync does not include the Wapro Mag connector yet.”, the panel shows Wapro isn’t included in this ERP Sync, or the PC and connector tab shows the connector as Not installed.The agent cannot find the connector’s files in the connectors\wapro subfolder of its install folder. Install the agent again with the MSI: it brings the connector with it. If the message says the connector’s description could not be read, install the update again or contact support.
  • “This product is not linked to a product in the ERP. Refresh lists on the connection’s Overview tab, or link it on its Warehouses and products tab.”: the catalog product has no link on this connection. Click Refresh lists so Omnilinker links what it can, by the connection’s link key, or link it by hand. See Link products.
  • “Someone is changing which products the ERP manages. Try again in a moment.”: while you link, ignore or create products, or change who manages SKUs, another person is doing one of those, or Omnilinker is updating products from the ERP in the background (linking, creating, or applying a new product list). Try again.
  • An ERP product does not link by itself: Omnilinker remembers an unlink or an ignore, so the row shows Won’t link automatically or sits under Ignored. Click Link to link it by hand, or Stop ignoring. Otherwise look for a suggestion on the row and its reason, for example GTIN shared by 3 products; Link suggested links the suggested product. Which key links on its own (code, code then EAN, or EAN only) is set with Edit product settings on the Warehouses and products tab. See Products from your ERP.
  • “The ERP warehouse … is ignored on this connection. Stop ignoring it before you map it.”: click Stop ignoring on its row on the Warehouses and products tab. See Lists and mappings.
  • “This warehouse is not on the ERP’s warehouse list. Refresh lists and pick one.”: the source warehouse you entered is not one the agent sent. Click Refresh lists, then pick a warehouse from the list. See The source warehouse.
  • “This connection owns ‹what›. Make Omnilinker the owner of those first, then delete the connection.”: the connection manages something in Omnilinker, and the message lists it: Product identity (it manages SKUs), Product fields: ‹names› (it is the source of those fields), or a warehouse or price level. Make Omnilinker the owner first. For SKUs, click Change owner under Who manages SKUs in How products arrive from ‹connection› on the Warehouses and products tab and choose Omnilinker · Catalog. If the connection is switched off or its product settings cannot be used yet, Change owner is not offered there: open Catalog > Products, click Change owner next to Who manages SKUs there, or switch the connection on first. For fields, set each one to Off or Fill when empty with Edit product settings; the dialog shows the field table for them even when the settings cannot be used otherwise. See Products from your ERP.
  • “Omnilinker couldn’t check what this connection owns, so it wasn’t changed. Try again.”: Omnilinker could not read what the connection manages, so it deleted nothing. This is deliberate: it will not delete a connection it cannot check. Try again in a moment.
The check Order and customer procedures present failing means the SQL login lacks a right that orders and customers need, or your Wapro does not have a procedure. The check names what is missing. Grant the rights in Rights for orders and customers, or update Wapro. Until it passes, orders and customers stop; reading, stock and price writes continue.
Orders are saved in Wapro in the name of an ERP user, and none is set. Open the connection’s page, click Change next to ERP user for writes, enter the user’s number in Wapro and click Save. You need Change the ERP user for writes. See Monitoring.
The agent is older than the one that can place orders, so nothing is sent. It updates itself at night; see Update the agent to do it now.
More than one Wapro customer could be the buyer, or the only ones found are blocked or inactive in Wapro, and Omnilinker does not guess. Open the order, click Choose the Wapro customer and pick one, or create a new customer. A blocked or inactive customer cannot be picked: lift the block in Wapro and send the order again, or create a new customer if the block should not stop this order. See Choose the customer yourself.
The order is in a foreign currency and Wapro has no NBP rate for it within 7 days of the order date. Add the rate in Wapro, or let Wapro download it, and the order is sent again by itself (checked about once an hour). If Download NBP exchange rates is on and the receipt of the order’s command (ERP Integration > Commands) has a warning that the download failed, the SQL Server probably does not allow CLR or cannot reach the NBP site, or the login lacks EXECUTE on Api_CurrencyImport. See Currencies and Wapro.
The order goes to another EU country and Wapro has no cross-border (OSS) VAT set up for it: the switch for cross-border transactions, or an active standard rate for the destination country. An order with goods at a rate other than 23% waits for the same reason. Set it up in Wapro; the order is sent again by itself. See Cross-border VAT.
You cancelled the order in Omnilinker, but Wapro or the agent did not cancel it there. Cancel the order in Wapro, or click Try the cancel again on the order card once the cause is fixed. You need Change status for that.
The agent did not answer in time, so it is not known whether Wapro created the order. Look for it in Wapro. If it is there, click Send again: Omnilinker finds it by its reference and the order shows In Wapro. If it is not, click Send again too. Sending again is safe: Omnilinker’s reference on the order stops Wapro from creating it twice.
The order card says why. Refused: … names what Wapro found: the order is fulfilled, invoiced, closed or cancelled, someone changed its lines in Wapro, or a line is a set. Check the order in Wapro, then click Retry, Undo my change or Cancel and send again. See Change an order that is in the ERP.If the message says the agent “does not take changes to an order yet”, update the agent. If it says “ERP connection not ready” and the connection’s PC and connector tab shows Change orders switched off, the SQL login lacks the rights to change orders: see Requirements.
An ERP order comes from one warehouse. Move the order’s products to one warehouse, or enter the order in Wapro by hand and click Entered in Wapro by hand.
The source is set to Managed by another system, or to Do not send, or nobody answered the question Who imports orders into ‹connection› today? yet. Omnilinker sends nothing for such a source. Change it on the connection’s Orders tab; see Orders to your ERP.
The card’s ERP section says Not read back from Wapro yet: its status and invoices show here once Wapro reports them. for an order that is in Wapro. Check, in order:
  1. Is the agent from this release? An older agent does not read orders back, and the Lists from ‹ERP› card shows no Receives orders sent from Omnilinker line. See Omnilinker requires a newer agent.
  2. Was the order sent less than about 15 minutes ago? The agent reads orders back about every 15 minutes. Wait for the next read, or click Refresh lists on the connection’s Overview tab.
  3. Is the read switched off? The PC and connector tab should list Read orders sent from Omnilinker among the connector’s operations. If it is marked switched off, grant the SQL login the read rights in Requirements. The agent’s log names what is missing. If it is not listed at all, the agent is older than this release: see step 1.
  4. Is the agent paused or offline? A paused or offline agent reads nothing. See The PC and connector tab says Offline.
  5. Did Omnilinker support set the lists the agent reads by comparison? If the list in Configuration reference does not include SalesOrders, the orders are read only with the daily complete read. Add SalesOrders to it, one environment variable for each entry (ErpSync__Feeds__DiffStreams__0, ErpSync__Feeds__DiffStreams__1, and so on), as the page shows.
The read-back is for orders created in Wapro in the last 90 days. An older order says “Wapro no longer reports this order; its last known status is shown.” and is not read again.
Who changes this warehouse’s stock offers the connection only when the warehouse can be handed to it. The greyed-out option says why:
  • “Comes once ‹connection› has sent a complete stock list.”: the agent has not finished a complete read of stock yet. Check that it is online and from a release that sends stock; see No ERP stock is shown.
  • “This isn’t mapped on ‹connection›.” or “This has 2 mappings on ‹connection›.”: map the warehouse to exactly one ERP warehouse on the connection’s Warehouses and products tab.
  • “The connection ‹connection› is switched off. Switch it on first.”: switch the connection on.
See Hand a warehouse to your ERP.
“Orders from ‹sources› land in ‹warehouse› but aren’t sent to this ERP, so their stock would stay held for good.” An order source whose orders land on the warehouse (its warehouse, or your default warehouse for a source without one) is set to Do not send, Managed by another system, or sends to another connection, or nobody answered Who imports orders into ‹connection› today? yet. Set each named source to send to this connection on the connection’s Orders tab (see Choose how each source sends), or give it another warehouse, then try again.
“‹connection› must reserve the ordered stock while it manages a warehouse’s stock: turn on reservations in its order settings, and make sure its ERP Sync supports them.” Switch on Book a reservation in ‹connection› under Order settings, and update the agent if it cannot send orders yet. The same message refuses switching that setting off while the connection manages a warehouse: make Omnilinker the warehouse’s owner first.
Wapro cancelled or deleted the order while it is still open in Omnilinker, so Omnilinker holds its stock again (not for an archived order) and sent you a notification. Click Send to Wapro again to send it as a new order, Entered in Wapro by hand if someone created it in Wapro again, or cancel the order in Omnilinker if the sale is off. See Removed in the ERP.
The locked option says why under its name. “Reading prices from ‹ERP› is switched off for this account.”: ask Omnilinker to turn on Read prices from the ERP (see Modules and feature availability). “Waiting for the first full read of prices from ‹ERP›.”: no full read has arrived since the level was mapped; click Read prices now and wait a few minutes, and check that the agent is running and up to date. “This price level no longer exists in ‹ERP›, or it was ignored.”: map it again on the connection’s Price levels tab. “‹ERP› doesn’t send this list yet.”: update the agent. See Prices from your ERP.
“The price level ‹level› has no currency yet. Only prices in the level’s currency come from the ERP, so declare its currency first.” Declare the level’s Currency on Price levels, then try again.
“A price for ‹level› was still being written to the ERP after a wait, so the ERP cannot take the level over yet.” A send of this level was still running at the agent after the change waited 30 seconds for it, which can happen during a large send. Try again when it has finished; check ERP Integration > Commands. If the message also names withdrawn sends, they are sent again where the level is sent to the ERP automatically; otherwise send them again if they are still needed.
The ERP took the price level over while the send was queued, so the send was cancelled on purpose: the ERP sets that level now. Nothing was written to the ERP. If you gave the level back, send the price again. When the level has changed owner again since, the command reads “Withdrawn: ‹ERP› took over this level then.”; the reason stays the owner change of that time. See Where a send stands.
Open the connection’s Price levels tab and read the line under the level’s row, or click Details. Not linked: the product is not linked to an ERP product; link it. Other currency: the ERP price is in another currency than the level’s, and is never converted. No VAT rate: give the product a sales VAT rate. Failed: the price could not be stored and is tried again at the next read. Waiting: see the next entry. If the row shows no read time, the connection has not read prices: check that Read prices from the ERP is on, the level is mapped, and the agent is running and up to date. A price that has disappeared from the ERP, or is 0.00 / 0.00, keeps Omnilinker’s price on purpose. See What lands.
The price has not landed yet. It lands after the next read, usually within minutes. A price read before Omnilinker’s latest send waits for a newer read. The Price levels tab counts such a price under Waiting, retries included. A price that keeps failing ends up under Failed, and the product page then says it could not be stored.
Check, in this order: Read product images from the ERP is on for your organization (it is off until Omnilinker switches it on; see Features); the connection’s Images field is not Off (it starts Off, and nothing arrives until you save it on); the agent is up to date and its login can read Wapro’s images (the PC and connector tab shows Read product images switched off otherwise; see Wapro); and the product is linked to an ERP product. The first read of a large catalog takes hours. See Product images.
An image is not taken when it is larger than 10 MB, 25 megapixels or 12,000 pixels a side, or when it is not a JPEG, PNG, WebP, GIF or BMP (WMF, EMF, TIFF, SVG and HEIC are not taken). A product takes at most 20 images. An image Wapro keeps in its image folder (disk mode) is not read, and an image Wapro lists without its data is kept in Omnilinker as it was. An image replaced in Wapro by one of exactly the same size shows after the daily check at night. See What is read.Under How products arrive from ‹connection› on the Warehouses and products tab, the Images line counts these images by reason, for example “‹n› images are larger than Omnilinker takes: kept as they were in Omnilinker”, and “‹n› images still on their way” counts those the agent has not uploaded yet. See Where images stand.
Earlier versions of the agent answered a local API on http://localhost:5555. The agent no longer opens any network port, so that API is gone. Use the connection’s PC and connector tab in Omnilinker, the tray app, or the agent’s log files instead.

​
Get help

If none of this solves the problem, contact Omnilinker support. Include:
  • The connection name, and what you see on its PC and connector tab.
  • The agent’s version, from the PC and connector tab or the tray app’s Settings > Updates.
  • The report from the tray app’s Troubleshoot… > Copy report.
  • The service log files from the time the problem started.
Never send credentials.dat, and do not paste your ERP password into a message. Look through the log files before you send them.