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

# sk171869 - Processes in PND state after mds_restore

| Property | Value |
|----------|-------|
| Solution ID | sk171869 |
| Date Created | 2021-02-16 |
| Last Modified | 2021-02-23 |
| Technical Level | General |
| Products | Multi-Domain Security Management Server |
| Versions | R82.10, R81.20, R82, R82.20 |
| OS | Gaia |

## Symptoms

- * After mds_restore completes successfully, most domains are in pending state, and some domains are in down state.

* Following errors are found in the file $MDS_TEMPLATE/log/cpm.elg:  

  `
  com.checkpoint.infrastructure.utils.runtime.CpAssertionError: Uncaught exception org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dleServerInitializerBean' defined in class path resource [com/checkpoint/management/dleserver/dle-server-config.xml]: Invocation of init method failed; nested exception is CpmGeneralException{base='com.checkpoint.management.is.exceptions.CpmGeneralException: java.lang.reflect.InvocationTargetException', errorCode='CP_ERR_UNSPECIFIED', errorFamily='null', messageForUser='null', message='java.lang.reflect.InvocationTargetException'} in thread Thread[main,5,main]`  
  `
  at com.checkpoint.infrastructure.utils.runtime.CpAssert$DefaultAssertionErrorCreator.createAssertionError(CpAssert.java:2)`  
  `
  at com.checkpoint.infrastructure.utils.runtime.CpAssert.doFail(CpAssert.java:19)`  
  `
  at com.checkpoint.infrastructure.utils.runtime.CpAssert.fail(CpAssert.java:17)`  
  `
  .........`  
  `
  Caused by: java.lang.NullPointerException`  
  `
  at com.checkpoint.infrastructure.cpprod.CpprodUtilsIs.readRegistryFileVersion(CpprodUtilsIs.java:152)`  
  `
  at com.checkpoint.infrastructure.cpprod.CpprodUtilsIs.registryChanged(CpprodUtilsIs.java:160)`

## Cause

In rare scenarios, registry files collected by mds_backup may have invalid values when used on the restored machine.

## Solution

This problem was fixed. The fix is included in:

* [Jumbo Hotfix Accumulator for R80.40](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk165456) starting from Take 87
* [Jumbo Hotfix Accumulator for R80.30](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk153152) starting from Take 227
* [Jumbo Hotfix Accumulator for R80.20](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk137592) starting from Take 187
* [Jumbo Hotfix Accumulator for R80.10](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk116380) starting from Take 288

If you choose not to upgrade, Check Point can supply a **Hotfix** . [Contact Check Point Support](https://www.checkpoint.com/support-services/contact-support/) to get a Hotfix for this issue.  
A Support Engineer will make sure the Hotfix is compatible with your environment before providing the Hotfix.  
For faster resolution and verification, please collect [CPinfo files](http://supportcontent.checkpoint.com/solutions?id=sk92739) from the Security Management Server and Security Gateways involved in the case.

**Hotfix installation instructions:**   
Refer to [sk168597 - How to install a Hotfix](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk168597).

In case you are unable to upgrade at the moment, the following workaround can be used:

1. Stop services on the Multi-Domain Manaement Server/Multi-Log Management server: `# mdsstop`

2. Run this function to check which domain is causing the issue:

   **`# for cma in $($MDSVERUTIL AllCMAs | sort); do mdsenv $cma ; grep -q "version=" $CPDIR/registry/HKLM_registry.data ; if [ $? != 0 ]; 
   then echo "Did not find version in registry for $cma" ; fi ; done`**
3. Once confirmed, copy the registry file from the existing original Multi-Domain Management Server from where the backup was taken if possible. If not, copy the old registry file to replace the corrupted one for the relevant CMA:

   **`# mdsenv <CMA>`
   `
   # cp -pv $CPDIR/registry/HKLM_registry.data.old $CPDIR/registry/HKLM_registry.data ; rm $CPDIR/registry/HKLM_registry.data.corrupt*`**

   Repeat the steps for all the problematic CMAs.
4. Start services:`# mdsstart`

5. All CMAs should be in pnd state now. Wait until post restore SOLR rebuild is completed for all processes to come up.

---

# 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