Database Access Crashes on Windows 2003 Terminal Server

[Mike Schumann]

I have been running a Microsoft Access 97 application on Windows 2003
Terminal Server for almost a year now, with no problems.

About two weeks ago, I started to get the following errors in my event log:

Application Error; EventID: 1000
Faulting application msaccess.exe, version 8.0.0.5903, faulting module
VB5DB.DLL, version 6.0.81.69, fault address 0x00005867.

I am getting the same type of error with Visual Basic 6.0 applications using
Access databases that I am running on the same system.

Does anyone have any idea what is going on?

Thanks,

 

[MikeD]

I have been running a Microsoft Access 97 application on Windows 2003
Terminal Server for almost a year now, with no problems.

About two weeks ago, I started to get the following errors in my event
log:

Application Error; EventID: 1000
Faulting application msaccess.exe, version 8.0.0.5903, faulting module
VB5DB.DLL, version 6.0.81.69, fault address 0x00005867.

Have you updated anything? For example, installed a program or updated via
an SP or installed any other update (maybe even via Windows Update)? More
general, has *anything* about your system changed? If you have restore
points (I think Windows Server 2003 has these), then perhaps you should
restore to a point 2 weeks ago (since that's when you said the problem
started occuring). Then, re-apply updates one at a time, testing your app
thoroughly after applying each update. Eventually, you should be able to
determine which one (if any) could be causing the problem.

I am getting the same type of error with Visual Basic 6.0 applications
using Access databases that I am running on the same system.

What do you mean "same type of error"? Are you getting this *exact* same
error in VB6 as well? That doesn't make much sense to me unless you are
using Access Automation from your VB6 app. Also, what data access method
are you using (DAO, ADO, RDO)?

One final note: have you checked the MSKB to see if there are any known
problems using Access 97 (or DAO, since that's what Access 97 uses)with
Windows Server 2003?

 

[Mike Schumann]

I have a suspicion that the problem is related to running Windows Update.
My Visual Basic Code used DAO to interface with an Access Database. The
error I'm getting is also in VB5DB.DLL at the same offset.

Mike Schumann

 

[Mark Yudkin]

I was not aware that Access 97 was supported on Windows 2003 Terminal
Server.
[Translation: I'm amazed it ever worked]