NAV 2016 crashes when posting big batches

mikhael
mikhael Member Posts: 19
in NAV Three Tier
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!

Best Answer

Answers

  • davmac1
    davmac1 Member Posts: 1,283
    why would you have so little memory on your servers?
    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.
    David Machanick
    http://mibuso.com/blogs/davidmachanick/
  • oki
    oki Member Posts: 46
    Hi,
    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
  • mikhael
    mikhael Member Posts: 19
    No. of concurrent should not be a problem, there are maybe max. ~6-7 NAV users at the same time, but those batches to be posted are pretty heavy.

    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.
  • archer89
    archer89 Member Posts: 337
    edited 2016-08-04
    check windows eventlog for error entries
    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.
    best regards
    Franz Kalchmair, MVP
    Alias: Jonathan Archer

    please like / agree / verify my answer, if it was helpful for you. thx.
    Blog: http://moxie4nav.wordpress.com/

Categories