Written by Jason Feemster, POS specialist with 15+ years of experience helping restaurants and retailers troubleshoot POS systems, payments, and hardware issues.
Common Issue: MICROS database shows offline, terminals lose data, or menu changes in BOH don’t sync to workstations.
Fast Fixes: Restart CAL and database services, reboot BOH server, check disk space, verify backups, and force a data download to terminals.
Need official help? See our MICROS POS Support Guide
Want guided troubleshooting? Try the POSUSA POS Support Assistant (Free).
MICROS database offline or menu changes not syncing? You might see terminals running old menus, missing new items, or throwing errors when trying to save checks. In some cases, the system may not launch at all from the BOH.
Here’s how to diagnose and fix MICROS database and sync issues so your menu and terminals stay in sync.
Table of Contents
- 1 Common Reasons MICROS Database Goes Offline or Stops Syncing
- 2 How to Fix MICROS Database Offline / Sync Problems
- 2.1 1. Restart MICROS Database and CAL Services
- 2.2 2. Reboot the BOH Server
- 2.3 3. Check Disk Space on the BOH Server
- 2.4 4. Force a Data Download to Terminals
- 2.5 5. Verify Network Connectivity Between BOH and Terminals
- 2.6 6. Review Recent Menu or Configuration Changes
- 2.7 7. Check for Database Error Messages or Logs
- 3 When to Contact MICROS Support
- 4 MICROS Database & Sync Issues – FAQs
- 5 Try the POSUSA POS Support Assistant
- 6 Thinking About Switching POS Systems?
Common Reasons MICROS Database Goes Offline or Stops Syncing
- MICROS database or CAL service stopped on the BOH server
- Server rebooted and services didn’t restart properly
- Low disk space on BOH preventing database operations
- Corrupted database files or logs
- Terminals not receiving updated data files
- Network issues between BOH and workstations
How to Fix MICROS Database Offline / Sync Problems
1. Restart MICROS Database and CAL Services
This is the first place to look when menus don’t update or the system reports database errors.
- On the BOH server, open Windows Services
- Find and restart the MICROS Database service
- Restart the MICROS CAL service as well
If services restart successfully and stay running, many database connection issues resolve immediately.
2. Reboot the BOH Server
If services won’t restart or the system feels unstable, a full BOH reboot is often the fastest way to clear stuck processes.
- Close any open MICROS or management applications
- Reboot the BOH server from Windows
- After reboot, confirm MICROS Database and CAL start automatically
After the reboot, test menus and logins from a single workstation before rolling back into full service.
3. Check Disk Space on the BOH Server
Low disk space can prevent the database from writing logs or saving configuration changes—causing sync failures and instability.
- Open File Explorer and check free space on the system drive
- Delete unneeded temp files, old logs, and outdated backups
- Aim to keep at least several GB of free space available
If space is critically low, resolve that first before restarting database services again.
4. Force a Data Download to Terminals
If the database looks healthy but menu changes don’t show up on the workstations, they may not have received updated data files.
- From BOH, run a manual data transfer to all or selected terminals
- Restart one terminal after the download completes
- Check whether new menu items or prices appear correctly
If one terminal updates and others don’t, the issue is likely terminal-specific or network-related.
5. Verify Network Connectivity Between BOH and Terminals
Database sync depends on stable communication. If workstations can’t reliably reach the BOH server, they won’t receive updated configurations.
- From each workstation, ping the BOH server’s IP address
- Check switches and routers for link lights or error indicators
- Look for patterns—e.g., only one side of the restaurant having issues
Network segmentation or failing hardware can cause partial sync problems that only affect certain terminals.
6. Review Recent Menu or Configuration Changes
Sometimes a recent configuration change can trigger unexpected behavior or partial failures.
- Identify recent menu, price, or configuration changes
- Rollback or temporarily disable complex changes if issues began afterward
- Test sync again with a simpler configuration
If rolling back changes resolves sync problems, reintroduce updates gradually with testing between steps.
7. Check for Database Error Messages or Logs
Persistent database issues often leave clues in MICROS or Windows logs.
- Review MICROS database logs for corruption or connection errors
- Check Windows Event Viewer for disk, service, or application warnings
- Note any recurring errors to provide to your support provider
Serious or repeated database errors usually need attention from a MICROS support professional.
When to Contact MICROS Support
- Database or CAL services will not start or stay running
- Terminals cannot connect to the database at all
- Menu changes never sync despite manual data transfers
- You see signs of database corruption or severe performance issues
👉 MICROS SUPPORT – Phone & Online Customer Service
MICROS Database & Sync Issues – FAQs
What does it mean if the MICROS database is “offline”?
Can low disk space cause database problems?
Try the POSUSA POS Support Assistant
Need help walking through MICROS database or menu sync issues step by step?
- POSUSA POS Support Assistant
- Select MICROS
- Type: “database offline” or “menu not syncing”
- Follow the guided troubleshooting flow
Ideal when you need clear steps during a busy shift and can’t wait on hold with support.
Thinking About Switching POS Systems?
If you’re dealing with repeated POS issues, it might be time to compare more reliable options built for restaurants and retail businesses.
Takes 30 seconds • No sales pressure
