Azure Backup install fails with a SQL Server installation failed.

Question

Exit error message: The /IACKNOWLEDGEENTCALLIMITS command line parameter is missing or has not been set to true. An Enterprise Server/CAL license product key (as opposed to Enterprise Core) was entered, and this computer has greater than 20 physical cores (40 logical cores with Hyper-threading enabled). This is a required parameter for the setup action you are executing to acknowledge that the SQL Engine will only utilize up to 20 physical cores, or 40 logical cores with Hyper-threading enabled.

Start time: 2024-08-22 16:14:03

End time: 2024-08-22 16:14:14

Requested action: Install

Answer 1

@Sam Albright - Thank you for reaching out to the support, happy to assist you. MABS install Enterprise version for SQL server which has 20 core limit. Please find below the details.

So this limit is for SQL Licence which is shipped with MABS. You can either lower the cores of the server and try again installing MABS or you can use your own SQL Licence to install SQL and then install MABS application using the existing SQL instance.

Answer 2

Hi @Sam Albright ,

Thank you for your reaching out and welcome to Microsoft Q&A!

As Erland said, could you please post more information? We need more details on what you're doing.

In addition, please refer to this official documentation and ensure you are using the correct command prompt.

Thanks for your understanding. Your time and cooperation are much valued by us. We are looking forward to hearing from you to assist further.

Best regards,

Lucy Chen

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our Documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

https://docs.microsoft.com/en-us/answers/support/email-notifications

Answer 3

Thanks for providing the context. That makes it easier to understand your situation. For the record, SQL Server is my expertise, but I am not familiar with Microsoft Azure Backup Server.

This seemed so embarrassing for Microsoft, so I downloaded MABS and attempted to install it on a VM, but my attempt failed already during the check of the SQL Settings, referring my to the DPM logs, which I was not able to find.

Anyway, reading the message more closely, I think I understand what is happening, and it is unlikely that it would have happened to me if I had been able to run the install. To wit, it seems that the way the DPM installs SQL Server, it runs into problems on a better server like yours. Well, 20 cores is not really extreme, so it still is sort of embarrassing.

There seems to be a workaround, though. DPM accepts that you provided an existing instance at installation. And the DPM install media includes the SQL Server setup files, they are in the SQLServer folder where you extracted the MABS files. You need to be careful so that you install SQL Server with the settings that MABS requires. See https://learn.microsoft.com/en-us/azure/backup/backup-azure-microsoft-azure-backup for details. One thing I observed is that MABS seems to require that you have a named instance. Also, you need to install SQL Server Reporting Services separately, but the install file for SSRS is in the SqlServer folder.

If the machine you are installing on is a VM, another workaround could be to reconfigure it to have only 20 cores when you run the installation.