Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1.1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 326 Dynamics CRM
- 110 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 994 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
SQL Server Permissions For Adding New Windows Logins
Jonathan2708
Member Posts: 552
Hi,
I've just had a customer who could not add a new Windows Login to their NAV database, the error message was "You do not have the required SQL Server permissions to perform the current security activity". The user trying this already had the 'db_owner' and 'db_securityadmin' roles for the NAV database, and they also had the 'securityadmin' server role. I added the 'db_securityadmin' role for the master database but this made no difference. In the end I added 'db_owner' role for the master database and this solved the problem.
I can never remember having this problem before, and having to give so many SQL privileges to enable adding a new Windows Login. Has anybody else encountered this before? The only difference I can think of is this is our first customer using SQL 2008R2, though we have many on SQL 2008.
Setup :
NAV 2009SP1 Classic Client
SQL Server 2008R2
SQL Server Security : Windows Authentication Only
Thanks
Jonathan
I've just had a customer who could not add a new Windows Login to their NAV database, the error message was "You do not have the required SQL Server permissions to perform the current security activity". The user trying this already had the 'db_owner' and 'db_securityadmin' roles for the NAV database, and they also had the 'securityadmin' server role. I added the 'db_securityadmin' role for the master database but this made no difference. In the end I added 'db_owner' role for the master database and this solved the problem.
I can never remember having this problem before, and having to give so many SQL privileges to enable adding a new Windows Login. Has anybody else encountered this before? The only difference I can think of is this is our first customer using SQL 2008R2, though we have many on SQL 2008.
Setup :
NAV 2009SP1 Classic Client
SQL Server 2008R2
SQL Server Security : Windows Authentication Only
Thanks
Jonathan
0