PC Review


Reply
Thread Tools Rate Thread

Database Access Crashes on Windows 2003 Terminal Server

 
 
Mike Schumann
Guest
Posts: n/a
 
      18th Aug 2005
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,
--
Mike Schumann


 
Reply With Quote
 
 
 
 
MikeD
Guest
Posts: n/a
 
      18th Aug 2005

"Mike Schumann" <mike-(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>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
Microsoft MVP Visual Basic


 
Reply With Quote
 
Mike Schumann
Guest
Posts: n/a
 
      19th Aug 2005
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

"MikeD" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
> "Mike Schumann" <mike-(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>>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
> Microsoft MVP Visual Basic
>
>



 
Reply With Quote
 
Mark Yudkin
Guest
Posts: n/a
 
      28th Aug 2005
I was not aware that Access 97 was supported on Windows 2003 Terminal
Server.
[Translation: I'm amazed it ever worked]
"Mike Schumann" <mike-(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>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,
> --
> Mike Schumann
>



 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
MS Access not running on Windows 2003 terminal server =?Utf-8?B?cnVzanc=?= Microsoft Access 5 6th Jun 2005 02:05 PM
Problem with Access 2000 Runtime on Windows 2003 Terminal Server. =?Utf-8?B?amVu?= Microsoft Access 2 17th Jan 2005 01:32 AM
Terminal Server Spooler service crashes sometime with Error 12: The access code Lonnie Microsoft Windows 2000 Terminal Server Applications 0 6th May 2004 03:56 PM
Windows 2003 Terminal Server and Windows 2000 Terminal server License server =?Utf-8?B?U2Vhbg==?= Microsoft Windows 2000 Terminal Server Applications 1 26th Nov 2003 09:16 PM
Windows 2003 Terminal doesn't find WK2 Terminal Server Licensing Server Don Surrett Microsoft Windows 2000 Terminal Server Applications 1 16th Sep 2003 02:40 AM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 02:31 AM.