Illegal Operation

RachelSoonRachelSoon Member Posts: 202
edited 2006-06-29 in Navision Attain
Hi There,
My customer is using Navision 3.60 with hotfix from 1 to 20, dabase used 84%.

However, some of the PC will get the illegal operation error message occasionally. Below is the frequency for the message occurance :
1) 21 April 2005
2) 27 Aprial 2005
3) 26 Sept 2005

The message prompt during :
1) Printing invoice
2) Preview a report
3) perform posting
4) login to Navision main Menu. Have not go to any module.

The client PC are with sufficient resource with specifications as below :
window 98, PIII/PIV, 256 RAM, HD 10 to 20 GB.

How can i solve the problem above?

Thank you.

Regards
Rachel

Comments

  • RachelSoonRachelSoon Member Posts: 202
    Sorry, i left out the exact message displayed by the system.

    The error message displayed by the system is as below :

    "This program has performed an illegal operation and will be shut down.
    If the problem persists, contact the program vendor."
  • kinekine Member Posts: 12,562
    It is problem of the Win 98 platform. Navision 3.60 have problems with this system. Please, if you can, upgrade to the Win2k or XP. Or you can try to use some external programs, which is able to clear the memory, system resources etc.

    And second thing - recommanded is to have max. 75% of full DB... please, extend your DB...
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • ckndr47ckndr47 Member Posts: 100
    Hello,

    The DB i am using is SQL Server option and its memory is not fixed, its auto-incremental, but still i am getting the this error while running a code unit:

    The description for Event ID ( 1000 ) in Source ( Microsoft Business Solutions-Navision ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: finsql.exe, 4.0.1.21666, 430b4e86, finsql.exe, 4.0.1.21666, 430b4e86, 0, 0025be7a.
  • Alex_ChowAlex_Chow Member Posts: 5,063
    1. Upgrade to XP and get all the updates
    2. Check your C: drive and make sure it has enough space
    3. Make sure you have enough memory. At least 256k of memory should do.
  • bbrownbbrown Member Posts: 3,268
    Do not rely on SQL's Auto-Grow to expand the database size. Monitor and expand manually as required. Keep the database between 60-80%. Auto-Grow is should only be used as a safety net, in case the database suddenly fills up the system won't crash.
    There are no bugs - only undocumented features.
  • ara3nara3n Member Posts: 9,256
    Also how big is the log file and how big are the mdf and ldf files.
    Remember that anything you do in a db is recorded in the log file.
    So if you users run routines daily to create some records and then delete them, all is recorded into the log file.
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
Sign In or Register to comment.