[Jason Wilder]

Since we have gone Live with NAV 2016 in Jan 2017 about twice a month our Service Tier crashes.  Most of the reasons have an explanation that we have gotten to the bottom to but there are two times that we are trying to figure out what happened.  I have a sneaking suspicion (based on user feedback) that it is a user hitting the send to excel button on a list screen with millions of records.

The most recent example is someone removed their filter on the Item Ledger Page and hit the Excel button which would try to send over 17 million ILE records to Excel.  NAV slowed to a crawl and then kicked everyone out.  Simply restarting the service tier solved the problem. 

Can anyone else confirm this has happened to them?

If yes I know the fix is to set the following property in the service tier to a more reasonable number:

——————————
Jason Wilder
Senior Application Developer
Stonewall Kitchen
York ME
——————————

[Mike Louis]

Hi Jason,

I haven’t had that experience, but if you have established that the user’s actions of exporting to Excel are the root cause, then one thing that you could try is this, but please research further before doing:

Source of information: https://msdn.microsoft.com/en-us/library/dd301077(v=nav.90).aspx

Have the user close out of NAV.
There is a config file at:
File name: ClientUserSettings.config
C:Users<username>AppDataRoamingMicrosoftMicrosoft Dynamics NAV90

Open the ClientUserSettings.config in Notepad.
Save a copy of the file in another folder in case you need to revert back.
Look for the row below, or if it doesn’t exist, please add in:
<add key=”MaxNoOfXMLRecordsToSend” value=”10000″/>
Save file (don’t overwrite the copy).
Start up NAV.

They should get an error message if they try to export more than the stated number of records (10,000). 

Best Regards,
Mike
*provided “AS IS”, no warranty expressed or implied, and confers no rights.

——————————
Mike Louis
Business Systems Analyst
Cogentix Medical
Minnetonka MN
——————————
——————————————-

[Geovanny Fuentes]

Please review the event viewer, it will tell you a lot. User causing issue, things leading up to it.
Could be a service pack update on the server.
Look at the server resources in task manager, user count, etc.

Find the routine then ask users who was doing what. 

Good luck.

——————————
Geovanny Fuentes
——————————
——————————————-