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
- 271 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
NAV 2016 crashes when posting big batches
mikhael
Member Posts: 19
Hello Friends,
We have a problem with one of our customers in NAV 2016 that NAV sometimes crashes when posting very big batch of general journal rows (+50 000 rows) or sales invoices (+1000 invoices). Client just stops responding and nothing will get posted to GL.
We have another quite similar customer in NAV 2015 where we are posting around 1000 sales invoices at one batch every day, but have never had similar problems.
We also updated NAV 2016 CU4 to CU9 version last month, but the problem is still present.
- Have you experienced that kind of problems with NAV 2016 or with other NAV versions?
- Is there some kind of rule of thumb how many general journal rows NAV can post at once without problems?
- We have 8gb RAM installed on NAV Service server, 16gb on SQL server and 8gb RAM on NAV Client server, I think this should be enough because we have used same kind of configurations in NAV 2015 installations as well. Or do you think this is some kind of memory problem?
Thanks in advance for your thoughts!
We have a problem with one of our customers in NAV 2016 that NAV sometimes crashes when posting very big batch of general journal rows (+50 000 rows) or sales invoices (+1000 invoices). Client just stops responding and nothing will get posted to GL.
We have another quite similar customer in NAV 2015 where we are posting around 1000 sales invoices at one batch every day, but have never had similar problems.
We also updated NAV 2016 CU4 to CU9 version last month, but the problem is still present.
- Have you experienced that kind of problems with NAV 2016 or with other NAV versions?
- Is there some kind of rule of thumb how many general journal rows NAV can post at once without problems?
- We have 8gb RAM installed on NAV Service server, 16gb on SQL server and 8gb RAM on NAV Client server, I think this should be enough because we have used same kind of configurations in NAV 2015 installations as well. Or do you think this is some kind of memory problem?
Thanks in advance for your thoughts!
0
Best Answer
-
Options
fcipriano
Member Posts: 26
What is the Value on the propriety DataCacheSize on your service configuration?
I had one problem that sometimes NAV crashes due to the value is too low.
5
Answers
It is easy enough to check memory pressure using taskmgr and resource manager.
You don't say how many users you are supporting, but I would never put less than 16GB on a server out of principal and prefer to have at least 32GB RAM on both.
Log space shortage can also cause a crash - the batch will build the log file until it is committed.
Client - you can get buy maybe with 8GB RAM - but why? RAM is cheap these days.
http://mibuso.com/blogs/davidmachanick/
little hint: could be a RAM hardware malfunction in a RAM region which only be used when many data is processed.
We've monitored the system event log on our serice tier and found some error entries, luckily before any malfunction has occured. So we were able to exchange the faulty part before it came to an application error.
oki
Adding more RAM is not actually that straightforward since the servers are located on the external data center and alterations to those setups must be ordered elsewhere. In addition, we have successfully used same kind of configurations with NAV 2015 in servers where there are also other background processes running all the time.
However, it sounds logical that there can be somekind of RAM / cache shortage which will cause the crash. I will watch the memory pressure on the both SQL and NAV Service servers next time when the users are going to do those postings.
also sql log for more details
you could also run sql profiler when running that batch job.maybe there are some long runtime statements, blockings, timeouts.
Franz Kalchmair, MVP
Alias: Jonathan Archer
please like / agree / verify my answer, if it was helpful for you. thx.
Blog: http://moxie4nav.wordpress.com/
I had one problem that sometimes NAV crashes due to the value is too low.