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
- 310 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
NASSQL.exe Pegging CPU
JCHWSU
Member Posts: 2
We are running a VT100 for CK71 scanners. But few times per week, out scanners start having massive connection issues.
When this happens:
Event viewer is flooded with:
- "The terminal with ID xxx did not receive a reply from the CSS within 69000 milliseconds."
- "There was a problem replying to internal key xxx. A reply could not be received for terminal xxx. Terminal will be resetted. Thread: xxx"
Also:
- The nassql.exe process is also pegging out the CPU. Well, just the one thread of the cpu it uses.
- You cannot stop/restart the NAS service. You have to kill the nassql.exe process
- Sometimes this fixes it right away, other times the issue comes back in a few minutes.
We are running:
- NAV 2009 (NAV 6.0) on Server 2008 R2 (64bit) with SQL 2008 R2
- NAS is on a different Windows server 2008 R2 (64bit)
I am not sure if the CSS errors are the cause of the nassql.exe process wigging out, or if the nassql.exe wigging out is causing the CSS errors.
Does anyone have an opinion of what the issue might be?
When this happens:
Event viewer is flooded with:
- "The terminal with ID xxx did not receive a reply from the CSS within 69000 milliseconds."
- "There was a problem replying to internal key xxx. A reply could not be received for terminal xxx. Terminal will be resetted. Thread: xxx"
Also:
- The nassql.exe process is also pegging out the CPU. Well, just the one thread of the cpu it uses.
- You cannot stop/restart the NAS service. You have to kill the nassql.exe process
- Sometimes this fixes it right away, other times the issue comes back in a few minutes.
We are running:
- NAV 2009 (NAV 6.0) on Server 2008 R2 (64bit) with SQL 2008 R2
- NAS is on a different Windows server 2008 R2 (64bit)
I am not sure if the CSS errors are the cause of the nassql.exe process wigging out, or if the nassql.exe wigging out is causing the CSS errors.
Does anyone have an opinion of what the issue might be?
0
Answers