MS Office 2007 on Server 2008R2 Terminal Server crashing

We are using thin clients to run MSAccess on a terminal server.  Many times a day Access crashes.  The errors below come from the Event viewer on the terminal server.

Faulting application name: MSACCESS.EXE, version: 12.0.6606.1000, time stamp: 0x4e27ab6b
Faulting module name: MSVCR80.dll, version: 8.0.50727.6195, time stamp: 0x4dcddbf3
Exception code: 0xc0000005
Fault offset: 0x000172d7
Faulting process id: 0x17c0
Faulting application start time: 0x01cec8f00fff7f85
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office12\MSACCESS.EXE
Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll
Report Id: 5355b94d-34e3-11e3-9c9a-005056953adf

ID: 2, Application Name: Microsoft Office Access, Application Version: 12.0.6606.1000, Microsoft Office Version: 12.0.6612.1000. This session lasted 9 seconds with 0 seconds of active time.  This session ended with a crash.

Googling turned up turning off DEP for MSAccess.  We have done that.  No joy.

Any idea where we could look next?

Who is Participating?
gbnortonConnect With a Mentor Author Commented:
The problem was fixed by increasing the resources to the VM and improving the coding in the Access program.
JasonDuncanworksConnect With a Mentor Commented:
Have you gone through the usual stuff?

1. All updates for the server?
2. All updates for Office?
3. Check for Malware/Virus on server?
4. Clean all temp files with CCleaner or Cleanup?
5. Reboot server?

Is it one user or all users? If its one or the same group re-create profiles?
gbnortonAuthor Commented:
1,2,3,4,5 Yes

Further observation revealed it is one Access program crashing.  We have others that work well MOST of the time.  I'm modifying this program now to get and save data similar to the ones that are not crashing.  Hopefully, that will take care of it.  I'll update after.
gbnortonAuthor Commented:
The Access program is multi user.  Me, the amateur, was holding the database open too long.  It was fixed by changing the way records were saved.  And even improved on more by moving the data to Sql Server.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.