> Source: [sk118953](https://support.checkpoint.com/results/sk/sk118953)

# sk118953 - During migration of HA MDS, some CMAs will not start the FWM, (or fwmha in later releases), process

| Property | Value |
|----------|-------|
| Solution ID | sk118953 |
| Date Created | 2017-07-13 |
| Last Modified | 2026-03-12 |
| Technical Level | Advanced |
| Products | Multi-Domain Security Management Server |
| Versions | R82.10, R81 (EOS), R81.10 (EOS), R81.20, R82 |
| OS | Gaia |

## Symptoms

- * When migrating a primary HA MDS without also exporting it's secondary at the same time, some or all of the CMAs FWM processes will not start.
* FWM process is down for these CMAs, and `fwm -d` in the cma context returns messages:

  ```
  FwmMghaInit failed with error 80004005
  FwmMghaInit failed (0x80004005)
  ```

* Logging into SmartConsole produces the following error: "Unable to connect to server. Please make sure that all processes of the server are up and running"

## Cause

The actual cause here is due to the HA mechanism failing. Elsewhere in the `fwm -d`, you may notice failure messages related to mgmt ha. This can also happen in cases where the secondary MDS has been removed prior to the upgrade.

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content