What SQL permissions do you need to upload a Dynamics NAV license file?

Whenever you get a new license file from your partner, in order to activate the new license file, you need to upload the license file to your server. However, sometimes, you may get an error when uploading the license file. So far, I have seen two error messages, that users usually get:

The following ODBC error occurred: Error: [Microsoft][ODBC SQL Server Driver] Database is invalid or cannot be accessed. State ID: HY024:

Error Database is invalid or cannot be accessed

This error means, that you have only “public” server role and “public” database role. You don’t have more permissions on SQL Server side.

The follow SQL Server error or errors occurred: 229,”42000″,[Microsoft][ODBC SQL Server Driver][SQL Server]The UPDATE permission was denied on the object ‘$ndo$srvproperty’, database ‘master’, schema ‘dbo’.

Error The UPDATE permission was denied

This error is different from the previous one, because you do have more sql permissions on the database from which you are trying to upload a license file. You have db_owner permission on the database side, but you still have only “public” Server Role.

Both of these errors mean that you lack permissions on SQL Server. So, what sql permissions do you actually need to upload a Dynamics NAV license file?

Well, firstly, you need to know what happens when you upload a license file. When you click Tools > License Information > Upload, system will upload the license file to the database you are connected to and then to the “master” database. Therefore, you need sql permissions on both of them.

This can be achieved one of the two ways:

1) You need to have “sysadmin” Server Role.
2) Or, you need to have “db_owner” role on database level for both your NAV database and master database. Then, from “Server Roles”, public role will be sufficient.

Having one of the two of the above, will allow you to upload the license file.

The server license was successfully uploaded

Technorati Tags: , ,

This entry was posted in databases, security, SQL and tagged , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *