Rapid Start Permissions issue on new install NAV 2013

(0) Share

Report

Posted on by Community Member

We have recently setup a new NAV 2013 installation but are getting permission errors when we try to open or edit Rapid start Configuration package in our test database. The package was exported from the Cronus database and imported successfully into our Test database. Our test database was created by backing up and restoring our production database. We do not have the problem in our Production database.

The message we are getting is:

"The user does not have permissions to perform this action. Page-Edit - Config. Package Card - BASICCONFIG must close. "

We have verified that our license is uploaded successfully and our user has db_owner rights in SQL Server in both the production and test databases. We have also give the user sysadmin role on the SQL server.

Any help would be appreciated.

*This post is locked for comments

All responses (5)

Answers (1)

Suggested answer

Community Member on at

Like (0)

Report

RE: Rapid Start Permissions issue on new install NAV 2013

I also faced the same problem even though I have been assigned the super privilege. It was strange but, after giving the sysadmin right to the network service user in SQL the problem got solved. Thank you posting the solution.
Community Member on at

Like (0)

Report

RE: Rapid Start Permissions issue on new install NAV 2013

We had to give the NAV service tier account sysadmin rights and this resolved our issue.
Alexander Thyssen 5 on at

Like (0)

Report

RE: Rapid Start Permissions issue on new install NAV 2013

We are encountering the same problem - cannot enter the worksheet window nor the table window in the rapid start menu.
Verified answer

Community Member on at

Like (0)

Report

RE: Rapid Start Permissions issue on new install NAV 2013

Hi Mark. Yes, we are an end-user using an end-user license for the BE edition (or Starter Pack in NAV 2013) when importing the package. It is possible that the the BASICConfig package contains AM data since we exported from Cronus, but we encountered the permissions issue even when we tried to create our own package and only import one table like payment terms. We just found a work-around solution by giving the NAV service account sysadmin rights in SQL but we are not sure why that would be required.
Marije Brummel 2,662 on at

Like (0)

Report

RE: Rapid Start Permissions issue on new install NAV 2013

Are you using an end-user license when importing the package? Does the package contain AM data whilst the customer uses BE?

Have you tried starting the debugger to see where it fails?