Skip to content

Troubleshooting

Common problems around the Warehouse Client and how to solve them – separated by app operation and setup in Business Central. The app's interface is German; its messages and buttons are quoted as they appear on the device.


Connection & sign-in

Symptom Cause Solution
"Nicht verbunden" (not connected) Connection data missing/incorrect Check the Settings; rescan the QR; BC-Verbindung testen
"Gerät nicht angemeldet" (device not signed in) Device sign-in missing or expired In the app run Einstellungen → Gerät anmelden – the app never prompts for a Microsoft sign-in by itself (Sign-in)
Sign-in fails Entra Client ID missing/incorrect Enter the Entra Client ID (MAUI App) in the Setup; regenerate the QR
Employee has to sign in again after a restart Intended behavior Badge + PIN after every app start; the device sign-in remains
Badge sign-in rejected Warehouse user disabled, badge barcode unknown or no PIN set Check the warehouse user: Enabled, Badge Barcode, Set PIN (Employees)
HTTP 401 / unauthorized Token invalid/expired Run Gerät anmelden again; check the Entra app registration
HTTP 403 Missing permission Assign the ALN MCWC API User permission set
Timeout Network/firewall Is the BC environment reachable? Internet on the device?

Quick test

Run BC-Verbindung testen in the Settings – the message names the cause of the error (reachability, permission, setup).


QR pairing

Symptom Cause Solution
QR not recognized Poor light / small code Display the QR larger, adjust distance/lighting – or on Windows use QR-Code aus Bild laden
No sign-in possible after scan Entra Client ID was missing when generated Enter the Client ID in the Setup, regenerate the QR
Wrong terminal/location QR of a different terminal Use the QR or setup sheet of the correct terminal

Scanner

Symptom Cause Solution
Scan does nothing Wrong scanner type Select the type in the Settings (keyboard/DataWedge/camera)
Changed scanner type has no effect The scanner is only set up at app start Restart the app
Zebra trigger does not respond DataWedge profile missing or intent action does not match Restart the app – it creates the "MC Warehouse Client" profile at start; a changed DataWedge Intent Action must match the profile
Barcode unknown Code not maintained on the item Maintain GTIN/EAN or item reference in BC

Scale & printer

Symptom Cause Solution
„Versenden" greyed out, hint „Gewicht erforderlich" Require Weight Entry active, weight 0 (no gross weights, no scale) Maintain item gross weights or connect a scale; otherwise switch the requirement off on the terminal
No weight Host/port/command incorrect Check the scale settings; Waagenverbindung testen
Label not printed ZPL printer not reachable Check the printer IP/port; ZPL-Verbindung testen; network/printer switched on?
Delivery note not printed No A4 printer, Android device, report not set up, or the terminal account may not run it Set the PDF Printer Name on the terminal (Windows only); check the report selection. The client names the reason in the status line
Label: no shipment provider No active shipment connector belongs to the document's shipping agent Activate the connector or correct the shipping agent on the document – there is no silent fallback to another provider (carrier resolution)
Label arrives late Shipment connector generates asynchronously Wait briefly; if it fails permanently, check the connector (Shipping)

Goods issue

Symptom Cause Solution
Goods issue finds nothing Filtered by location or allowed shipping agents Check the terminal; in the Sales Orders mode the app states the number of open orders that do not match the terminal
Goods Issue Mode Inventory Picks cannot be selected Warehouse Mode without BC warehouse management Set the Warehouse Mode to BC Warehouse Picks (with WMS) (Setup)
Warehouse Mode cannot be switched back Goods Issue Mode is set to Inventory Picks Change the Goods Issue Mode first
Pick List or Warehouse Activity cannot be enabled Module does not match the Warehouse Mode Switch the Warehouse Mode or use the matching module
Shipping agent cannot be assigned to the terminal No active merchantCENTRAL shipment provider belongs to the shipping agent Enable the shipment provider in the Hub

License & modules

Symptom Cause Solution
Module is not activated No license/demo Register a demo (Licensing); Activate in Hub on the setup page
App reports "Modul nicht aktiviert" / "Lizenz nicht gültig" (module not activated / license not valid) Extension inactive in the Hub or license expired Check the license, activate in the Hub, then Erneut prüfen (check again) in the app
Write action denied License missing or module off at the terminal Check the license; set the terminal override to Enabled
Demo cannot be restarted Demo consumed in the production system Unlock via the license manager; in a sandbox a demo does not count as consumed
Tile missing in the app Module disabled globally/at the terminal Check the Setup or terminal
"Keine Retourengründe hinterlegt" / "Keine Reklamationsgründe hinterlegt" (no return/complaint reasons) No return reason released for the terminals Set Show on Warehouse Terminal in the Return Reasons (Return Reasons)

Terminals & locks

Symptom Cause Solution
New terminal is rejected Terminal limit reached Disable terminals or License / Change Terminals (Terminals)
Document "in progress" Lock of a different terminal Wait for release; the lock expires after the Lock Timeout
Lock stuck after crash Terminal closed without releasing Cleanup Expired Locks on the setup page
Terminal "idle" No activity Adjust the idle threshold via Terminal Idle Minutes in the Setup Wizard
KPI "Shipments per hour" looks wrong Wrong start of day Set the Workday Start Time in the Setup to the start of the shift

Badges & counters

Symptom Cause Solution
Badge shows 0/too few Filtered by allowed shipping agents/location Terminal: check the allowed shipping agents and location
Number outdated Not refreshed Return to the main menu – the counters are reloaded

Further help