Support
Milestone XProtect Recording Server or Cameras Offline
VMS Availability
Summary
Follow the four stages below to diagnose a Milestone recording server or its cameras show offline without losing evidence, configuration or device ownership.
Applies to
- Milestone XProtect VMS
- Management Client and Smart Client deployments
Difficulty and time
Difficulty: Advanced
Estimated time: 30 to 90 minutes
What you will need
- The exact model and current firmware or app version
- Administrator access where authorised
- A photo or screenshot of the current status
- One controlled test case and its exact time
What this guide covers
- Preserve and reproduce the fault
- Open the correct diagnostic screen
- Correct the proven cause
- Verify and document the result
Use this page when a Milestone recording server or its cameras show offline. It includes the menu or screen to look for, the status that matters and a repeatable proof test.
Exact labels can differ between recorder, controller, app and firmware versions. If the named screen is not present, do not guess at destructive options; note the model and current version for support.
Before you start
Protect the current system and record a baseline before changing anything.
- Write down the exact symptom: Smart Client reports server/camera unavailable, or live and recording stop for a group of devices.
- Photograph the current status, error text, wiring or timeline as applicable.
- Record the last known working time and anything changed immediately before the fault.
- Back up configuration and record database/device identities before deleting hardware or rebuilding a recording server.
Do not remove a recording server to clear an offline icon
Deletion or reinstallation can affect databases, licences and historical recording access. Diagnose services and connectivity first.
If the required option is missing or the result does not match this guide, stop and identify the exact model before continuing.
What usually causes this
- Recording Server service stopped
- Server cannot reach Management Server
- Camera address or credentials changed
- Licence/device replacement is incomplete
Step 1: Preserve the current state and reproduce the fault
Begin with a repeatable baseline so you know whether a later change genuinely helped.
- Reproduce the problem once and record: Smart Client reports server/camera unavailable, or live and recording stop for a group of devices.
- Note whether every device or user is affected, or only one.
- Compare one working path with the failing path if a comparison exists.
- Back up configuration and record database/device identities before deleting hardware or rebuilding a recording server.
Step 2: Open the correct screen and inspect the evidence
The primary diagnostic location is Management Client > Site Navigation > Devices/Recording Servers, then server tray/service status and Logs. Do not change anything until the displayed state is recorded.
- Open Management Client > Site Navigation > Devices/Recording Servers, then server tray/service status and Logs. Menu wording can vary by model and firmware; use the nearest equivalent label.
- Determine whether one camera, one recording server or the whole site is affected.
- Confirm the Recording Server service and server network identity.
- Open device status/logs and record the first error and exact failure time.
Step 3: Correct only the cause you proved
Use the matching correction below. Make one change, save it, then repeat the same test.
- Restore the Recording Server service and its connection to the Management Server.
- For one camera, verify power/network, address and credentials from the recording server.
- Resolve licence/device hardware changes through the supported replacement path.
- Avoid deleting/re-adding devices until recording database impact and configuration are understood.
Step 4: Verify, monitor and document the handover
A saved setting is not proof. Test the real outcome locally first, then test any app, cloud or client path separately.
- Confirm each affected device returns Online.
- Open live view from Smart Client.
- Create and retrieve a fresh recording.
- Monitor logs through a normal service restart and retention/archive cycle.
Controlled support test
Situation: The reported symptom was: Smart Client reports server/camera unavailable, or live and recording stop for a group of devices.
Solution used: The current state was recorded in Management Client > Site Navigation > Devices/Recording Servers, then server tray/service status and Logs, one matching correction was made, and the same test was repeated.
Why this was chosen: This separated the proven cause from unrelated settings.
Installation notes: The final screenshot and test time were saved with the handover record.
Official reference used for this guide
Menu names differ between releases. Confirm model-specific behaviour in Milestone XProtect Administrator Manual before firmware, reset, storage or security-sensitive work.
Common mistakes
- Changing several settings before repeating the original test.
- Using a factory reset, initialise or format option as an early troubleshooting step.
- Treating an app symptom as proof that the local hardware or recording has failed.
- Failing to record the model, version, exact error and test time before escalation.
- Assuming similar-looking models use identical menus or features.
Troubleshooting table
| Symptom | What to check | What to do next |
|---|---|---|
| Smart Client reports server/camera unavailable, or live and recording stop for a group of devices | recording service stopped, server-management link failed, camera network/credentials changed or licence/hardware mismatch | Open the named diagnostic screen, record the displayed state and use the matching correction above. |
| The named menu is not visible | Different firmware, permissions or model capability | Do not substitute a destructive menu. Capture the model and version and use its official manual. |
| The change saves but the fault remains | The selected cause was not the root cause | Undo the change if appropriate, return to the baseline and compare the failing path with a working one. |
| Local test works but app or client test fails | Account, permission, cloud or remote-network path | Keep the proven local configuration and diagnose the remote path separately. |
| Problem returns later | Intermittent power, cable, storage, network or schedule condition | Record the new failure time and status; correlate it with logs, events and the last known working interval. |
When to contact support
Contact SecurityWholesalers support when services and network paths are proven but the recording server will not register, or historical databases/licences are at risk.
Send the order number if available, exact model, firmware or app version, screenshot of Management Client > Site Navigation > Devices/Recording Servers, then server tray/service status and Logs, the failure time, and the result of the local proof test.
Related support guides
- Milestone XProtect Support Guides - Browse every guide in this support area.
- All Technical Support Guides - Return to the complete support library.
Related buying guides
- CCTV Buying Guide - CCTV system-planning guide.
Relevant product categories
- Milestone Products - Milestone licences and products.
Still stuck?
Need help choosing or setting up a system? Contact SecurityWholesalers support with your order number, product model and a clear description of the issue.
Frequently asked questions
-
Where should I click first for Milestone XProtect recording server offline?
Start at Management Client > Site Navigation > Devices/Recording Servers, then server tray/service status and Logs. Record the existing state before changing it because labels and available options can vary by model and firmware.
-
What should I look for on that screen?
Look for Recording Server service state, server/device Online status, first log error, camera credentials and licence state.
-
What must I avoid changing during the first check?
Deletion or reinstallation can affect databases, licences and historical recording access. Diagnose services and connectivity first.
-
How do I prove the correction worked?
Restore Online state, view live video, retrieve a new recording and observe stable logs after a controlled service restart.
-
Why might my menu names look different?
Recorder, controller, camera, app and firmware releases can use different labels. Use the closest equivalent only when its function is clear; otherwise record the model and version for support.
-
Should I factory-reset the device?
Not as an early step. A reset may erase users, network settings, recording configuration, licences or cloud ownership. Back up the configuration and confirm the recovery plan first.
-
What should I send technical support?
Send the exact model and version, screenshot of Management Client > Site Navigation > Devices/Recording Servers, then server tray/service status and Logs, exact error text, failure time, what changed before the fault and the result of the controlled local test.
-
Can configuration changes recover data or events that were never recorded?
No. A correction can restore future operation, but it cannot recreate footage, alarm events or access transactions that were never stored.