Local Server failing to open MABS

Question

Local Server failing to open MABS

Jeff Graff 0

My MABS server ran out of disk space on the OS volume. I increased the drive and rebooted. I am receiving an error that Connection to the DPM service has been lost. Review the application event log for information about a possible service shutdown. Verify the following servers are not disabled. DPM DPM REplication Agent, SQLAgent$MSDPMINSTANCE, MSSQL$MSDPMINSTANCE Virtual Disk Server and Volume Shadow Copy. ID 917. The DPM Access ManagerService service is running and the DPM Writer. The others appear to start after these.

I got the DPM, DPM Agent Coordinator, DPMLA, and DPM RA to start ok. But when I start MABS, it fails again and those service shut back down.

Lots of application errors in event viewer (related to MSDPM, .net Runtime, and Application error (msdpm.exe)

I thought I could try to repair MABS but the only option I see is to uninstall.

Suchitra Suregaunkar 16,780 Reputation points Microsoft External Staff Moderator

2025-10-17T21:01:56.47+00:00

Hello Jeff Graff

Thank you for posting your query on Microsoft Q&A platform.

Could you please share us the details asked via private message and screenshot of the exact error message.

Thanks,

Suchitra.
Suchitra Suregaunkar 16,780 Reputation points Microsoft External Staff Moderator

2025-10-17T23:03:24.4933333+00:00
Hello Jeff Graff
After increasing the OS volume size on a Microsoft Azure Backup Server (MABS) and rebooting, the console fails to open with:

Error ID 917: “Connection to the DPM service has been lost. Review the application event log for information about a possible service shutdown.”

Services like DPM, DPMRA, SQLAgent$MSDPMINSTANCE, and MSSQL$MSDPMINSTANCE start and then stop.

Event Viewer shows multiple errors for MSDPM, .NET Runtime, and msdpm.exe crashes.

The installer only offers Uninstall, not Repair.

When the OS volume runs out of disk space, MABS cannot write critical data. This usually causes:

Database issues: The MSDPM SQL database may enter recovery mode or become inconsistent.

Service dependency failures: MABS relies on SQL and Volume Shadow Copy services. If they fail, the DPM console disconnects and throws error 917.

Configuration mismatches: Disk space problems can break scratch folder paths or registry entries.

As a workaround, You need to try below suggested steps as there is no in place repair option for MABS

Check Services

Make sure these services are running and set to Automatic:

DPM

DPMRA

SQLAgent$MSDPMINSTANCE

MSSQL$MSDPMINSTANCE

Virtual Disk Service

Volume Shadow Copy

If the services are started and you still experience the issue, check if the database is in recovery mode.

Validate Database

Run: DBCC CHECKDB;

If the MSDPM database is in recovery or inconsistent, repair it before restarting services.

Ensure Free Space & Scratch Folder

Keep at least 5–10% free space on the scratch folder volume.

If needed, move the scratch folder and update: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Azure Backup\Config

Sync Configuration: Run DPMSync.exe -sync as this helps fix mismatched state between services and the database.

5.Apply Latest Update Rollup: Install the latest Update Rollup for MABS/DPM from Windows Update or Microsoft site.

Reference document: https://support.microsoft.com/en-us/topic/update-rollup-1-refresh-for-microsoft-azure-backup-server-v4-45688e25-44db-4703-9ae9-cac611e46e07

6.Reinstall if Needed: If the issue persists reinstall

Backup DPMDB and configuration.

Uninstall MABS.

Reinstall using the same SQL instance and vault credentials.

Restore DPMDB if required.

Reference document: https://learn.microsoft.com/en-us/troubleshoot/system-center/dpm/troubleshoot-data-protection-manager-console-crash#error-917-connection-to-the-dpm-service-has-been-lost

Thanks,

Suchitra.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Suchitra Suregaunkar 16,780 Reputation points Microsoft External Staff Moderator

2025-10-17T23:23:58.45+00:00
Hello Jeff Graff After increasing the OS volume size on a Microsoft Azure Backup Server (MABS) and rebooting, the console fails to open with:

Error ID 917: “Connection to the DPM service has been lost. Review the application event log for information about a possible service shutdown.”

Services like DPM, DPMRA, SQLAgent$MSDPMINSTANCE, and MSSQL$MSDPMINSTANCE start and then stop.

Event Viewer shows multiple errors for MSDPM, .NET Runtime, and msdpm.exe crashes.

The installer only offers Uninstall, not Repair.

When the OS volume runs out of disk space, MABS cannot write critical data. This usually causes:

Database issues: The MSDPM SQL database may enter recovery mode or become inconsistent.

Service dependency failures: MABS relies on SQL and Volume Shadow Copy services. If they fail, the DPM console disconnects and throws error 917.

Configuration mismatches: Disk space problems can break scratch folder paths or registry entries.

As a workaround, You need to try below suggested steps as there is no in place repair option for MABS

Check Services

Make sure these services are running and set to Automatic:

DPM

DPMRA

SQLAgent$MSDPMINSTANCE

MSSQL$MSDPMINSTANCE

Virtual Disk Service

Volume Shadow Copy

If the services are started and you still experience the issue, check if the database is in recovery mode.

Validate Database

Run: DBCC CHECKDB;

If the MSDPM database is in recovery or inconsistent, repair it before restarting services.

Ensure Free Space & Scratch Folder

Keep at least 5–10% free space on the scratch folder volume.

If needed, move the scratch folder and update: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Azure Backup\Config

Sync Configuration: Run DPMSync.exe -sync as this helps fix mismatched state between services and the database.

5.Apply Latest Update Rollup: Install the latest Update Rollup for MABS/DPM from Windows Update or Microsoft site.

Reference document: https://support.microsoft.com/en-us/topic/update-rollup-1-refresh-for-microsoft-azure-backup-server-v4-45688e25-44db-4703-9ae9-cac611e46e07

6.Reinstall if Needed: If the issue persists reinstall

Backup DPMDB and configuration.

Uninstall MABS.

Reinstall using the same SQL instance and vault credentials.

Restore DPMDB if required.

Reference document: https://learn.microsoft.com/en-us/troubleshoot/system-center/dpm/troubleshoot-data-protection-manager-console-crash#error-917-connection-to-the-dpm-service-has-been-lost

Thanks,

Suchitra.
Suchitra Suregaunkar 16,780 Reputation points Microsoft External Staff Moderator

2025-10-17T23:25:53.8433333+00:00

Hello Jeff Graff Kindly let us know if the solution provided worked for you. If you need any further assistance, please feel free to reach out.

Thanks,

Suchitra.
Jeff Graff 0 Reputation points

2025-10-20T19:10:19.24+00:00

The solution did not help. They were things I had tried already. I tried to backup the DPM database, reinstall MABS and then import the database back in. Importing the DB back in fails and it says I dont have access to do that.

So now I am in worse spot then before. If I re-set up backups fresh, how can I have those match up with my backups in azure cloud. I dont really care about losing the local backups since I only keep few days on disk anyways. I do not want them creating all new backup servers in azure cloud though.

Will it automatically recognize those servers and just add as a new recovery point?
Suchitra Suregaunkar 16,780 Reputation points Microsoft External Staff Moderator

2025-10-22T18:01:30.76+00:00
Hello Jeff Graff If you reinstall MABS and cannot restore the original DPM database:

Register the new MABS server to the same Recovery Services vault using the original passphrase.

Azure will keep your old cloud recovery points in the vault. You can still restore from them.

You must recreate protection groups on the new server. These will start new backup chains.

Do not delete the old Backup Management Server entry in the vault, deleting it removes old recovery points.

Old backups stay in Azure for restore, but they won’t merge with new ones. New backups will create a separate lineage.

Thanks,

Suchitra.
Anonymous

2025-11-03T07:57:28.6466667+00:00

Hi Jeff Graff,

Could you please confirm whether the response provided my Suchitra helped you & please provide the required details in private message for us to investigate further.

Your answer

Suchitra Suregaunkar 16,780 Reputation points Microsoft External Staff Moderator

2025-10-17T21:01:56.47+00:00

Hello Jeff Graff

Thank you for posting your query on Microsoft Q&A platform.

Could you please share us the details asked via private message and screenshot of the exact error message.

Thanks,

Suchitra.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Suchitra Suregaunkar 16,780 Reputation points Microsoft External Staff Moderator

2025-10-17T23:25:53.8433333+00:00

Hello Jeff Graff Kindly let us know if the solution provided worked for you. If you need any further assistance, please feel free to reach out.

Thanks,

Suchitra.
Jeff Graff 0 Reputation points

2025-10-20T19:10:19.24+00:00

The solution did not help. They were things I had tried already. I tried to backup the DPM database, reinstall MABS and then import the database back in. Importing the DB back in fails and it says I dont have access to do that.

So now I am in worse spot then before. If I re-set up backups fresh, how can I have those match up with my backups in azure cloud. I dont really care about losing the local backups since I only keep few days on disk anyways. I do not want them creating all new backup servers in azure cloud though.

Will it automatically recognize those servers and just add as a new recovery point?
Suchitra Suregaunkar 16,780 Reputation points Microsoft External Staff Moderator

2025-10-22T18:01:30.76+00:00

Hello Jeff Graff If you reinstall MABS and cannot restore the original DPM database:

Register the new MABS server to the same Recovery Services vault using the original passphrase.

Azure will keep your old cloud recovery points in the vault. You can still restore from them.

You must recreate protection groups on the new server. These will start new backup chains.

Do not delete the old Backup Management Server entry in the vault, deleting it removes old recovery points.

Old backups stay in Azure for restore, but they won’t merge with new ones. New backups will create a separate lineage.

Thanks,

Suchitra.
Anonymous

2025-11-03T07:57:28.6466667+00:00

Hi Jeff Graff,

Could you please confirm whether the response provided my Suchitra helped you & please provide the required details in private message for us to investigate further.