Multiple preview will crash NAV 4.0 SP2 client

lucian
lucian Member Posts: 5
edited 2007-03-14 in NAV/Navision Classic Client
Hello Everyone!

Our company recently aquired some NAV 4.0 modules but we have some problems with multiple preview of our reports.
If I want to see same or different reports (from the reports tab) usually after 14-16 reports in preview mode and without closing the others the client will crash.
The company that implemented NAV was recommended to reinstall the SO (Windows XP SP2) but we run into the same errors on every workstation no matter what reports are previewed.
Everything it seems to work fine until we "sum" around 15 reports in preview mode (maximized) on the same PC, then the client is crushing recommending to send the error to Microsoft and restart the NAV client.

Is there a way to solve this problem?

If more information is needed I will be glade to share it...

Comments

  • lubost
    lubost Member Posts: 633
    I think that your problem is caused by using all system resources for opened objects.

    I think that leaving more then 5 report opened is very unuseful for users, because some of them can block some tables and some transaction are not committed.

    I recommend: try find solution to close report, not how to leave them opened.
  • muksha
    muksha Member Posts: 274
    Please remember that when you are running more report you are using some cache memory of the client. The problem may be due to the less cache defined at the time of installation. But this is true that you should not open more reports at the client due to the aforesiad reason said by
    Lubost.
    Mukesh Sharma
  • lucian
    lucian Member Posts: 5
    edited 2007-03-14
    lubost wrote:
    I think that your problem is caused by using all system resources for opened objects.

    I think that leaving more then 5 report opened is very unuseful for users, because some of them can block some tables and some transaction are not committed.

    I recommend: try find solution to close report, not how to leave them opened.

    Yes... you were right, but... what I forgot to mention is that those "15" reports for "test-crush" were 4 pages long, so if you have longer reports you could get a "good" combination and crush it only with 5 reports.

    Also another "strange thing" - is that if the reports are previewed but NOT maximized, you could open almost double until NAV client will stop processing the command saying that is "not enough memory (stack) to process this function" but will NOT crash the client, but in this case you can't see anything in report (if is not maximized).

    So... is this a bug?... a memory leakage?... because we sometimes run into this error with less than 5 reports opened...

    Is there any way to avoid this?...
  • lubost
    lubost Member Posts: 633
    As I and muksha said:

    1. Increase cache
    2. Don't allow users to run a lot of reports because it is unsafe for other users. It doesn't depend on the length of report, but on code inside.
  • muksha
    muksha Member Posts: 274
    Hi Lucian,
    May we know the exact reason why do you want provide liberty to open more than 15 reports to a single user. Is it so critical?
    Mukesh Sharma
  • lucian
    lucian Member Posts: 5
    Thank you Muska and Lubost for your quick replies.

    1. It seems that increasing cache (In "tools\options\object cache" if this is the right option to change) didn't help. It crashes at same number as with initial setting.

    2. As I said is not important the number of reports but sometimes will crush with only 5 reports and sometimes I have coleagues that need 5 reports opened when searching something.

    But I will try at our "supplier" to show me the code behind these reports (if will be possible) if you said that doesn't matter the lenght of the report but code behind it - so maybe they did something wrong...
  • lubost
    lubost Member Posts: 633
    It may depends on amount of memory on client, number of running applications (services), quota for some folders and so on. It is not so easy to find the reason and then solution.
    Can you explain some reports which crashes?
  • lucian
    lucian Member Posts: 5
    lubost wrote:
    It may depends on amount of memory on client, number of running applications (services), quota for some folders and so on. It is not so easy to find the reason and then solution.
    Can you explain some reports which crashes?

    All I know about these reports is that:
    1. Are "custom made" - especially for our company
    2. Are just variations for Client/Account transactions list along a period of time
    3. The "15 reports - crush" mentioned is not a "magic number" it could crash with more or less reports but this depends on the operator and his "business needs". I just "fixed" myself on a single kind of report just for "test-crush" purposes so I can reproduce the error constantly, because if I ask each user that reported the crush they can't remember exactly what they were doing (evetually in the past 1-2 hours) and how many reports they opened...

    If they get the error message "that is not enough memory" is OK because this way will remember to close some windows... but when the program will crash they could loose some data (or at least this is the "accompaning message").

    Don't know if this matters but all the stations reporting this error were almost the same hardware & software: P4 HT (no dualcore), RAM - 512/1024 MB, Video card 64/128MB, Windows XP SP2, Office 2003 PRO SP2.

    Could be something that should be updated on the client side regarding the rendering process of the reports?...

Categories