Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
NAV 2015 Client is killed - Service tier still running task?
Jut
Member Posts: 72
Hallo!
I am involved in a migration project from NAV 5.0 to NAV 2015. During the first tests we experienced a problematic behavior of the new three-tier-setup. Users are used to killing their NAV Client (Task manager - end task) if NAV stops reacting for a long period of time. In some cases that may make sense if they for example forgot set a filter on a long-running report. However at the Service Tier I can see that the work load is still high after the client was killed. SQL-profiler actually shows that the Service Tier is just continuing the work. If a user is running a report that is locking some records, for some or the other reason kills his/her session (e.g. just because of a Windows-crash), they could run into locks when trying to re-run the report because of their own old "orphan" session.
Is there any way to avoid that problem aside from training users not to kill sessions and to change all long running processes to update a dialog-window regularly?
Thanks and regards,
Jut
I am involved in a migration project from NAV 5.0 to NAV 2015. During the first tests we experienced a problematic behavior of the new three-tier-setup. Users are used to killing their NAV Client (Task manager - end task) if NAV stops reacting for a long period of time. In some cases that may make sense if they for example forgot set a filter on a long-running report. However at the Service Tier I can see that the work load is still high after the client was killed. SQL-profiler actually shows that the Service Tier is just continuing the work. If a user is running a report that is locking some records, for some or the other reason kills his/her session (e.g. just because of a Windows-crash), they could run into locks when trying to re-run the report because of their own old "orphan" session.
Is there any way to avoid that problem aside from training users not to kill sessions and to change all long running processes to update a dialog-window regularly?
Thanks and regards,
Jut
0
Comments
IF CONFIRM (STRSUBSTNO('Are you sure you want to kill session %1.',"Session ID"),FALSE) THEN
STOPSESSION("Session ID")
IF CONFIRM('Are you sure you want to kill session %1.',FALSE,"Session ID") THEN STOPSESSION("Session ID");