0

An unexpected error has occurred: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Pat Long

February 23, 2018 17:34

None

Follow

Hello, we are running a Jet Report in Excel 2016.

We are running

Jet Professional 2017 R3,

17.2.17209.1,

(32-bit)

-------------------------

We have also tried running this Jet Report in Excel 2013 on a server with 8 processors and 2016

 

The entire error is:

An unexpected error has occurred:
 Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
  System.AccessViolationException
   at System.RuntimeType.ForwardCallToInvokeMember(String memberName, BindingFlags flags, Object target, Int32[] aWrapperTypes, MessageData& msgData)
   at Microsoft.Office.Interop.Excel.Range.Calculate()
   at Jet.Excel.JetRange.as()
   at Jet.Excel.JetWorksheet.am()
   at Jet.Excel.JetWorkbook.ai()
   at g.a(Boolean A_0, Boolean A_1, Boolean A_2, Boolean A_3, Boolean A_4, Boolean& A_5)
   at g.a(Boolean A_0, Boolean A_1, Boolean A_2, Boolean& A_3)
   at Jet.JetDispatcher.a(Boolean A_0, Boolean A_1, Boolean A_2, Boolean A_3, Boolean A_4)
   at Jet.JetDispatcher.as()
   at Jet.JetDispatcher.b(Object[] A_0)
   at Jet.JetDispatcher.Dispatch(Object[]& args)

 

• Facebook
• Twitter
• LinkedIn

4 comments

• 0
  
  Harry Lewis April 02, 2018 15:41

  Hello Pat.

  I have seen this in using older versions of NAV (prior to NAV 2013).  The C/Front utility used to handle communications between NAV and other applications (such as the Jet Excel add-in) could run out of memory if a single query required C/Front to access an exceptionally large number of records.

  Otherwise, this could also be an issue with Excel's memory.  

  Excel uses memory for two purposes: in storing the workbook itself and in processing the calculations involved in the workbook.

  The first thing you can check is if Excel is having to store more than is necessary.  

  (a) Checking that Excel's "last cell" on each sheet is in the right place: using Ctrl-End or F5-->Special-->Last cell. When it's not where you want, for instance because of additional formatting or recently deleted cells, you can reset the last cell by deleting all columns to the right and rows below the correct last cell, and then saving, closing, and re-opening the workbook.

  When operating in native (not compatibility) mode, the 32-bit editions of Excel are limited to 2 Gigabytes of memory for the Excel process under Windows. This 2 Gigabyte limit is a limit on the "Virtual Memory" address space. The virtual memory used by a process is actually larger than the "working set memory" reported by Windows Task Manager, but we can use Task Manager to get an estimation of what the report is doing.

  While running the report, you could view the Task Manager Processes tab to see how much working set memory the Excel process is using. Assuming that the system has at least 2GB of RAM installed, as the process size approaches the 1.1GB-1.6GB level, we can start to expect issues like this.

  If that is the case, what can be done about it?

  There are a few possibilities, but not all apply to all reports.

  (b) If using Dynamics NAV and the report is having to search through some fairly large tables in NAV, having and using matching keys in NAV can be very helpful. In general, having a key in NAV that includes all the filters being applied in the Jet functions can improve speed and can decrease the amount of processing Excel has to do. Additionally, Jet Essentials provides the ability (on a function-by-function basis) to choose which NAV key to use. (this is the "Key=" feature).

  (c) If a report is having to calculate a great deal of NL(Sum) functions, one can try including SumIndexes in NAV to help NAV perform some of the calculations... thus freeing Excel from having to perform them.

  (d) The above methods seeks to limit the amount of information Excel has to examine. Obviously, another option lies in limiting the amount of information Excel needs to store.

  This would involve filtering the report so that less data is returned. The report could be broken up to examine a smaller range of accounts (running the report multiple times with different ranges to get a total) or a smaller date range to limit the size.

   

  If none of that seems to help or apply, I would recommend submitting a request with the Jet Technical Support team.

• 0
  
  Jeanette Dreiling October 24, 2018 21:11

  We are getting that same error on a jet report that we have been running daily for a few years using "refresh".  We put it in design mode to edit it and got this error when we tried to run it.  We pulled up an old report that runs fine if it is already in report mode.  It will refresh, but if you put it in design and click report or refresh, we get this error.

  We are using Excel 2013

  Jet Professional

  18.0.17321.0

  We have a universal licenses - connecting to a SQL database.

• 0
  
  Jeanette Dreiling October 24, 2018 21:12

  It also put the little diamond with a "?" in the cells and Excel freezes up and you have to End task to get it closed. 

• 0
  
  Harry Lewis October 24, 2018 22:47

  Hi Jeanette:

  Let's try a couple of experiments (do these individually).

  Test #1

  - Put the report in Design Mode
  - On your keyboard, hold down the Ctrl button and press the End button
  - How far down the sheet does Excel take you?
  - (if you report has more than one sheet, do this on each sheet)

  In this test, if you are taken WAY past where you actually have functions/formulas, do the following:

  - Save the file under a test name
  - Select the entire rows or columns of blank space and press the Delete key on your keyboard
  - Save the file
  - Close Excel
  - Open Excel
  - Open the test file
  - Run the report
  - Any change?

  Test #2

  - Go to your App Settings
  - Go to the Performance tab
  - Un-check Enable batch function execution
  - Run the report.
  - Any change?

  Edited by Harry Lewis October 24, 2018 22:49