Oh yes! I’m back to one of my favorite topics: Errors and warnings, causes and solutions – aka Troubleshooting! This time, once again, on BizTalk Server. Last week, I was installing a brand-new BizTalk Server 2020 environment – yes, a brand-new installation! For those who are wondering, questioning, or scratching their heads at the moment, let me tell you once again: BizTalk Server is not dead! Still, many companies rely on BizTalk Server for critical mission-critical integrations, and many are also migrating to BizTalk Server 2020 to facilitate and receive support while shipping their applications to the cloud – I have encountered the following error while trying to configure the first BizTalk Server machine:
Error Configuration Framework]Feature: [Group] Failed to configure with error message [Failed to create Management database “BizTalkMgmtDb” on server “SQL-SERVER\BIZTALK”.
BizTalk Server cannot access SQL server. This could be due to one of the following reasons:
1. Access permissions have been denied to the current user. Either log on as a user that has been granted permissions to SQL and try again, or grant the current user permission to access SQL Server.
2. The SQL Server does not exist or an invalid database name has been specified. Check the name entered for the SQL Server and database to make sure they are correct as provided during SQL Server installation.
3. The SQL Server exists, but is not currently running. Use the Windows Service Control Manager or SQL Enterprise Manager to start SQL Server, and try again.
4. A SQL database file with the same name as the specified database already exists in the Microsoft SQL Server data folder.
Internal error from OLEDB provider: “CREATE DATABASE permission denied in database ‘master’.
I was not surprised due to the several security restrictions on this environment.
📝 One-Minute Brief
This blog post will explore the route causes of the following issue [Group] Failed to configure with error message Failed to create Management database BizTalkMgmtDb on server while configuring BizTalk Server and it will provide the solution(s) for you to solve this error.
Cause
The error message gives you clear root causes for this problem:
- The SQL Server does not exist, or an invalid database name has been specified.
- The SQL Server exists, but is not currently running.
- A SQL database file with the same name as the specified database already exists in the Microsoft SQL Server data folder.
- Or access permissions have been denied to the current user.
But notice the last sentence of the error message. You will get the correct reason, at least in my situation, for this issue: Internal error from OLEDB provider: “CREATE DATABASE permission denied in database ‘master’.
Indeed, my user was not an SQL Server admin, nor did neither had permissions to create databases.
Solution
The solution to this issue is quite simple, and I believe that BizTalk Server administrators should have SQL Server administrator rights on the SQL Instance dedicated to BizTalk Server. So to solve this, you need to:
- Open Microsoft SQL Server Management Studio and connect to BizTalk Server SQL Server Instance
- On the left menu, expand the Security > Logins option.
- Check if your user is there; otherwise, create it by right-clicking on Logins and selecting New Login…
- On the Server Roles, ensure you choose sysadmin and click OK.
Now, if you try to apply the BizTalk Server configuration again, that problem will not appear.
Hope you find this helpful! So, if you liked the content or found it helpful and want to help me write more, you can consider buying (or helping to buy) my son a Star Wars Lego set.
Rather than give the BizTalk Administrators these rights, we ask for an BizTalk Installer account that has this right. As for your usual day to day administration you don’t need it. This way your BizTalk Admin account follows the principle of least privileges. Only when making configuration changes such as Adapters, Host Instances etc. would we use the BizTalk Installer account