Crystal Reports Error: Attempted to read or write protected memory.

SUGGESTED

Sage 300 Advanced ERP 2012 PU1

Windows 7 Professional - All latest updates installed.

Microsoft Outlook 2010

On one workstation only, when printing invoices to e-mail from the A/R module the first invoice processes as normal.  The second and all subsequent invoices give the following error.

"Description: Crystal Reports Error: Attempted to read or write protected memory. This is often an indication that other memory is corrupt."

 

If I exit Sage 300 ERP and login again I can send one more invoice then the problem returns for all subsequent invoices.

Any assistance would be greatly appreciated.

Parents
  • 0
    SUGGESTED

    At the end of the day this seems to be a Windows 7 (64-Bit) compatibility issue. It was resolved by inserting the following registry entries on each workstation (forcing Accpac to run in Windows XP compatibility mode):

    [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]

    "\\\\...Insert your program directory path...\\Runtime\\accpac.exe"="WINXPSP3 RUNASADMIN"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]

    "\\\\...Insert your program directory path...\\Runtime\\accpac.exe"="WINXPSP3 RUNASADMIN"

    There is of course other means to accomplish the same end result as the registry entries identified above.

    As the error message itself is not indicative of a compatibility issue it may be so generic that could represent a wide variety of error conditions.  (i.e. This solution may or may not work for you.)

  • 0 in reply to Porta

    I have encountered this problem in a Terminal Services environment with 3 of their 20 users. When I change to running the program as administrator in XP SP3 compatibility mode, the error message changes to "Crystal Reports error. Invalid export options" I have moved the users to another Terminal Server and one user still encounters the problem. Needless to say that this is frustrating. Any further solutions will be appreciated.

  • 0 in reply to John B

    Try opening Outlook in the terminal session before printing to email. There are also some technotes on Microsoft forums relating to turning off the Outlook warning that a program is trying to send email on your behalf.

Reply Children