Howdy, Stranger!
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
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 305 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 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
db_owner and posting error
fufikk
Member Posts: 104
Hi,
I'm facing a bit odd problem with finishing and posting prod. order: I get error message that Item Register xxx does not exist.
Little backgroud first: SQL server is 2012, NAV is 3.7 running with 5.0 client. Database has been moved recenlty from old server (don't know which version though).
There are 2 users: U1 (super & db_owner), U2 (SUPER, no db_owner, just public).
U1 is able to finish & post production order, while the other one can't. Sadly, I have no clue why that happens and I hope for your assistance.
Taking the easy way out and adding db_owner to everybody is not something I'd like to do... unless there is no other option.
Thanks in advance.
I'm facing a bit odd problem with finishing and posting prod. order: I get error message that Item Register xxx does not exist.
Little backgroud first: SQL server is 2012, NAV is 3.7 running with 5.0 client. Database has been moved recenlty from old server (don't know which version though).
There are 2 users: U1 (super & db_owner), U2 (SUPER, no db_owner, just public).
U1 is able to finish & post production order, while the other one can't. Sadly, I have no clue why that happens and I hope for your assistance.
Taking the easy way out and adding db_owner to everybody is not something I'd like to do... unless there is no other option.
Thanks in advance.
0
Comments
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
Interesting thing happened when checking the setting with user who is SUPER but not db_owner, I got this error:
Also was the db upgraded from an older sql version through sql backup?
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
I'm not 100% sure about that. On the other hand I haven't found anything that would say it isn't. Besides that particular posting problem I haven't heard of any other problems.
That I don't really know. However, yesterday I googled out someones problem with option caption string being slightly different that option string for Object Type field in Permission table. I checked it here as well to find out that there was no option caption for XMLPort for example. I'm not sure what to do with that knowledge right now, but I do remember a case from some time ago, where replacing existing tables in 2000000xxx range with "original" ones from target client version solved some problems.