Share
Report
389Hi all,
We desperately need help on our current NAV implementation. The connection to NAV frequently goes offline (for 3 weeks now) and at first a simple reboot would fix it. It has started to stop responding even after a reboot and continues to do this for a long time.
We have had 7 companies (around 20 users) since Nov 1st 2016 with no issues whatsoever. On the 1st Aug 2017 we implemented a new company and added 50 users. It was going fine for 1 week and since then it is continuously dropping out.
Over the weekend we moved it away from the original SQL server 2014 to a brand new SQL server 2014 (and hardware). We even created another server to handle the NAV apps. It was fine all day yesterday with no issues at all but now it's doing the same thing as the original environment. This rules out Hardware/Operating System/SQL.
When this happens, the SQL server management console cannot connect to itself (even via localhost). It can't be a network issue because none of the other servers / devices in the network have any issues (exchange, file server, AD etc). Sometimes, while NAV is not responding, we can still run Jet Reports.
Nothing shows up in the SQL logs or Windows Events when this happens it simply halts and all RTC's hang.
We have had engineers and consultants look at the problem but they are stumped.
I personally think it could be something in the new company data or MOD or something? We stopped all workflows, job queues etc to see if they were the cause but no luck. Can't understand how any problem like this can halt the entire SQL server.
Any suggestions ?
*This post is locked for comments
All responses (
Answers (
