---
title: "Error: Root Element Missing in Jet Data Manager"
description: "### Fixing the “Root Element is Missing” Error   If you’ve launched [Jet Data Manager](https://globaldata365.com/jet-data-manager-training/) and received the error message: > **An error occurred while reading the settings file. Root element is missing. Do you want to make another attempt…"
url: "https://globaldata365.com/helpcenter/error-root-element-missing-in-jet-data-manager/"
updated: "2026-10-25"
category: Jet Analytics
---

# Error: Root Element Missing in Jet Data Manager

### Fixing the “Root Element is Missing” Error

 

If you’ve launched [Jet Data Manager](https://globaldata365.com/jet-data-manager-training/) and received the error message:

> **An error occurred while reading the settings file. Root element is missing. Do you want to make another attempt reading the settings? If you answer no, be aware the application will exit and any changes cannot be saved.**

This typically means the application’s settings file, `Config.XML`, has become blank or corrupted.

 

#### Why This Happens

This issue usually occurs if something interrupted the creation or saving process of the Jet Data Manager settings file. When trying to sign in to your [Business Central](https://globaldata365.com/microsoft-dynamics-365-business-central/) Public Cloud data source, you encounter the following message:

 

As a result, the file is either empty or unreadable, triggering the "Root element is missing" error on startup.

![error root element missing](https://globaldata365.com/wp-content/uploads/2025/06/1-300x205.webp)

###  

#### How to Resolve It

Follow these simple steps to fix the error:

1. **Close Jet Data Manager** completely if it’s open.
2. **Open File Explorer.**
3. In the address bar, type:

   ```
   Set-ItemProperty -Path 'HKLM:SOFTWAREWow6432NodeMicrosoft.NetFrameworkv4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord Set-ItemProperty -Path 'HKLM:SOFTWAREMicrosoft.NetFrameworkv4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type Dword
   ```
       
   and press **Enter**.
4. Navigate to:
       `Jet Data Manager Server > Jet Data Manager Server > {version}`
   *(Replace `{version}` with your current version folder.)*
5. Locate the `**Config.XML**` file.
6. **Delete** or **rename** the file.
7. **Restart Jet Data Manager.**
8. When prompted, **re-enter your repository settings**.

Once restarted, Jet Data Manager will generate a new config file, resolving the issue.

 **Want to turn raw ERP data into powerful business insights?**
[👉 Join our Jet Analytics Training](https://globaldata365.com/jet-analytics-training/) and master building data warehouses, cubes, and advanced dashboards.

### Final Notes

 

This fix is quick, safe, and restores full functionality without impacting your existing projects or data. Always ensure you close Jet Data Manager before modifying system files to avoid further issues.

 

If the problem persists even after replacing the config file, it may indicate a deeper system or permission issue—consider reaching out to Global Data 365 support for further assistance.

 

#### If You Need Any Help, [Contact us](https://globaldata365.com/contact/) Now!

###### Still have Questions?

Ask us anything about this article – we’ll get backto you shortly.