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
- 309 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
Help! NAV 3.7 login issue with SQL 2005
spark_ling
Member Posts: 2
We still use nav3.7 and several days ago, we migrated the db from SQL 2000 to SQL 2005 and keep the compatibility to 80. We can logon with admin accounts, however, when a end user tried to logon, it prompted "the user doesn't have permission to perform the action". Does anyone here know how to fix this? Thanks a lot.
0
Comments
2) I recommend to do technical upgrade to NAV 4.00SP3
3) The security is more strict on MS SQL 2005. For some backward compatibility you need to turn on trace flag 4616 (-t4616 runtime parameter for MS SQL service). See on-line books how to enable the flag globally.
4) There can be more issues...
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
You should ask yourself the question: Do I want to run my critical business application on an unsupported combination. If something goes wrong they will say you should not have used this combination.
Backup your database and restore in 4.0 SP3 hotfix 6. Turn off index hinting and put the locktimeout on 30 seconds.
Good luck.