Logon Performance Via windows Authentication

surajv
Member Posts: 32
From 4.0 SP1 originally we experienced a delay on logon approx 30-40 sec. Then while on the 4.0 I applied a hofix which essentially became 4.0 SP2 and everyone noticed a much better performance at logon using Windows Authentication, the logon time reduced to fraction of second. Now that we are testing the 5.0 SP1 we have again seeing a performance issue which is taking a user approximately 30-40 seconds to logon.
Does anyone have any idea on how to make this any better?
Does anyone have any idea on how to make this any better?
0
Comments
-
Where is the point to migrate to old versions?
Why not to try 2009 R2?
BTW, never had any problem with logon time on any version of NAV. Must be IT issue.0 -
Go to File -> Database -> Alter, select Advanced tab, check Security Model setting. I bet it is Enhanced now.
Change it to Standard.Slawek Guzek
Dynamics NAV, MS SQL Server, Wherescape RED;
PRINCE2 Practitioner - License GR657010572SG
GDPR Certified Data Protection Officer - PECB License DPCDPO1025070-2018-030 -
I had a lot of customers who use enhanced. Never had any problem with it.0
-
No, just users, no dbo.0
-
I had a customer who was using enhanced security and wanted to change to standard as importing objects were taking so long.
So when the customer was carry out the task after an hour he concluded it crashed and end tasked. He asked me how long should this process take i said depends on the DB size and advised him to try on test database and surprising everything was done within 10 minutes.
Has anyone experienced a crash or taken over one hour to switch from enchancd to standard security?0 -
This can take the same or even more time as permissions synchronisation. Basically, when you changing security model to simple system will reset right on SQL tables for each user. This can take a while.0
-
But to do it, you need to put the DB in single-user mode.
If your database is opened by something else, your session remains blocked, showing nothing, until it can put the single-user mode. This can seem it takes a very long time to do the change but in reality your session is just waiting....
The best is to control with sp_who2 in SSMS to see who is blocking your session and killing that session if needed.Regards,Alain Krikilion
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!0 -
Yes session by NAS maybe causing the issue. I have recommended to stop NAS and try again i think this must be the cause.
Thanks0
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