Memory Error

Hi, hoping that someone can help me with the fllowing error : (Just in Case the Pic does not work)…"Other concurrent activities have re-used the available space in the DB that contained your snapshot of data. This can occur in connection with time-consuming taks such as printing or making backups. Wait until there ar efewre concurrent updates of the db and try again… create more space " Basically what I was trying to do is run a dataport import data into a table - 4MB text file (only doing this to test the problem). The database has 250mb free. Machine is running as a service with a Back Office machine connecting to it at regular intervals. Now all this seems pretty standard and definately works on other “identical” machines. Which leads me to beleive that it could be a memory problem? What stumped me is that testing this same setup on a test machine I had no problem. Any ideas [?]

It is possible to get this error in a live environment with active users. 250 mb free is not necessarily a lot; it must be compared to the total size of the database. You should expand the database to avoid this problem.

It is running in a live environment, but then again there are 3 other “identical” machines that are working fine! Database Used = 154mb. Total Size = 500mb. Nav Ver = 3.70 OS = XP RAM = 320mb This is a my last hope before having to uninstall services and totaly evaluate the memory usage on that machine. Was thinking that maybe someone has had this before. It could be related to the Retail Addon installed (one of their tables) and I will contact them as well - but I doubt it!

OK! Found the problem! Navision → Tools - Opotions Menu. “DBMS Cache (KB)” was set at a default 8000kb. I changed this to 40,000kb. All is working fine now!

Oh, and I forgot, I also uninstalled the Navision server because it was set-up to use 200mb cache. This was probably done when using the server setup wizard and defaulted to the amount of free memory (which was 200mb). I re-installed the service using the command line method - using 50mb cache instead.