Liveware Publishing Support Forum

Please help. This error message has become a regular occurrence. Our IT support and analytics team has been unable to correct the problem. ____"RSW frequently crashes when trying to preview a report (print preview). The error I receive is "The instruction at "0x73dd11d7" referenced memory at "0x00000004". The memory could not be "read". Click on OK to terminate the program." ____We are using RSW Version 12 Build 12.1.001____The default printer is set to Adobe PDF, but the problem also occurs with local and network printers. ____We have added the line _PDFDRIVER=0_ to the DEFAULTS section of c:windows sw.ini (and to rrw.ini), but the problem persists.____Any ideas?"____Thanks____

What happens if you open, save and the re-open and preview the report?____Kathleen__R&R Support

I just tried your suggestion, same memory error occurred.____The error also appears when I export the results to a DBF. ______

Did you ever get this problem resolved? I am on Ver 11 build 11.1.007 and I get this error as well. I can^t even print report specs to a printer or a file. When I make a change to a report and then save it, I sometimes get the error as it is saving. When I go back into the report, the change has been saved.

If you get errors on save, edit the file c:windows rw.ini and add the line:____LIBRARIAN=OFF____to the DEFAULTS section.____Kathleen__R&R Support

Hi Patty,____Just read your note. No, we haven^t been able to fix the error. I did find that if I remove all calculated fields from the group/sort areas and limit my scope to a few months of data (less than 2 million records), the report runs fine. The error usually occurs when using the SQL edition of RR.____We now do a straight (sql) data dump into various DBF files. The sql report was then rewritten using the xbase edition of RR and the process was automated through rapid runner. ____It^s an arduous "work around" for what appears to be a RR design flaw. If you search the forum history, you^ll see this issue has been asked many times before - and without resolution.__

This error is a generic one that might be caused by a number of different things. Are you sure that it was the number of returned rows that was indeed the culprit in your report? If so we can try some additional testing in house to see if we can reproduce/correct the problem.____Kathleen__R&R Support

Hi Kathleen. Sorry, I just read your most recent response. ____I^m not 100% certain that the problem is caused by the volume of returned records. That said, we have found that by reducing the volume of returned records, all the "Memory error 0x00000004" reports will run to completion.____I was waiting to see if the latest build 12.5 would fix the issue. It has not.____We have developed a work-around so this is no longer a pressing issue. However, if in the future a cure is discovered, please let me know.____thanks ____