Will Standard Model Solve my Problem?

megawavez
Member Posts: 133
I recently just moved our database from SQL2000 to SLQ2008. I did a backup and restore. Unfortunately, I've been getting some weird permissions errors since the restore. Once user was trying to rename an item and got an error about SELECT from the "Item Price Change" table. I fixed that by granting access to Public, then I get and error about UPDATE to "Sales Shipment Line". I could error by error grant appropriate access, but it seems like it could be a painful process.
We are currently on "Enhanced" model. Will "Standard" solve the problem? There were no problems before the upgrade.
We are using Client 5.0 SP1 right now.
Thanks,
mega
We are currently on "Enhanced" model. Will "Standard" solve the problem? There were no problems before the upgrade.
We are using Client 5.0 SP1 right now.
Thanks,
mega
0
Comments
-
there have been a couple of post on this. Most are from 2K to 2k5, but it's the same issue.
You need to do NAV backup and restore.
The other option is to lookup the blog that kine or kriki posted on this.0 -
It's hard to tell if the choice of "Security Model" will solve the problem, as we don't know IF the SM is/was causing the problem ...
But actually I highly recommend the "Standard" SM anyway!Jörg A. Stryk (MVP - Dynamics NAV)
NAV/SQL Performance Optimization & Troubleshooting
STRYK System Improvement
The Blog - The Book - The Tool0 -
Thanks for the replies. I think I'm going to try standard and see if that fixes the problem. "Enhanced" seems a little unnecessary right now.0
-
Thought I'd post this reply for anybody reading these boards. A switch to standard model did solve the problem ! For some reason, the "Synchronize All Logins" was not properly updating permissions under enhanced.0
-
Yes, this confirms my guess. This "Enhanced" Security Model is really a pain :thumbsdown: ... I'm wondering who on earth is really needing this ... so far I haven't met anyone ...
And it's always great fun to explain that "Standard" is not the Standard setting, but "Enhanced" ... and "Enhanced" is actually not "Enhanced" but Limited ... ](*,)Jörg A. Stryk (MVP - Dynamics NAV)
NAV/SQL Performance Optimization & Troubleshooting
STRYK System Improvement
The Blog - The Book - The Tool0 -
stryk wrote:Yes, this confirms my guess. This "Enhanced" Security Model is really a pain :thumbsdown: ... I'm wondering who on earth is really needing this ... so far I haven't met anyone ...
And it's always great fun to explain that "Standard" is not the Standard setting, but "Enhanced" ... and "Enhanced" is actually not "Enhanced" but Limited ... ](*,)
Quite a pain - I had to restore from a backup to get Standard again.0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions