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.)

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.)

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.

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.

Thanks. I will use this as a workaround, but I will still need to find a permanent solution. I will go through  the Microsoft technotes.

Did you ever find a solution to this in the Terminal Services environment?  I am encountering the same issue.  

Users need to be Power Users on TS.

Hi There,

I have a user experiencing this issue, however their issue is very intermittent.  I have tried re-sharing the shared directory folder to the user and that seemed to have worked for about a week however they have come back to me again today and told me they are getting the "Description: Crystal Reports Error: Attempted to read or write protected memory. This is often an indication that other memory is corrupt." error when trying to email invoices.

Hoping someone can help me with this.

Thanks.

Turn off DEP.