Faulting application msaccess.exe --HELP--
I have an access database that we use to run reports. This database was developed my one of our developers who is co working on this problem with me the network admin.
This database suddenly started having a problem where it would crash and give an error. After the error the access application would just “close out” when we tried to use in on that PC. By “close out” I mean access will disappear from the screen and task manager without any error or notice; gone in a blink. Other PC’s would be fine until or if the get the initial crash. The only way I have been able to resolve this problem, once access was “closing out” is to re-install the entire OS and applications, nothing else seems fix the problem.
The error that initially happens seems to be one of two things, most of the time we get: event id 1000 Microsoft Office 10
Faulting application msaccess.exe, version 10.0.6501.0, faulting module ntdll.dll, version 5.0.2195.6899, fault address 0x0004caaf.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Some times the faulting module is vbe6.dll rather than ntdll.dll, but the problem stays the same regardless.
Anyone have any thoughts on this?
It seems to me that once we get this error some DLL on my system is corrupt or is conflicting with another and causing the “close out” problem. The weird thing is that some systems work fine while others have this problem consistently. While rebuilding the systems I have tried all different service pack levels and patch levels, nothing seems to make a difference.
I have tried rolling back the database to an older version about a month ago, before we started having this problem. So far that older database does not seem to make any difference, but I continue to try different scenarios with it to no avail.
Is it just me or is Access not really all that stable of a development tool? (don’t answer that)
Any help I could get on this issue would be greatly appreciated.
This database suddenly started having a problem where it would crash and give an error. After the error the access application would just “close out” when we tried to use in on that PC. By “close out” I mean access will disappear from the screen and task manager without any error or notice; gone in a blink. Other PC’s would be fine until or if the get the initial crash. The only way I have been able to resolve this problem, once access was “closing out” is to re-install the entire OS and applications, nothing else seems fix the problem.
The error that initially happens seems to be one of two things, most of the time we get: event id 1000 Microsoft Office 10
Faulting application msaccess.exe, version 10.0.6501.0, faulting module ntdll.dll, version 5.0.2195.6899, fault address 0x0004caaf.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Some times the faulting module is vbe6.dll rather than ntdll.dll, but the problem stays the same regardless.
Anyone have any thoughts on this?
It seems to me that once we get this error some DLL on my system is corrupt or is conflicting with another and causing the “close out” problem. The weird thing is that some systems work fine while others have this problem consistently. While rebuilding the systems I have tried all different service pack levels and patch levels, nothing seems to make a difference.
I have tried rolling back the database to an older version about a month ago, before we started having this problem. So far that older database does not seem to make any difference, but I continue to try different scenarios with it to no avail.
Is it just me or is Access not really all that stable of a development tool? (don’t answer that)
Any help I could get on this issue would be greatly appreciated.
Hi ctrunk514
I subscribed to this Q hoping someone will pop in so that I benefit too,
Let me tell you my case,
We have in our office identical PCs and the same OS and Office 2k,
and No problem.
PIII, WinME, Office 2k.
The Account is using his oun accounting package, besides our developed project tracking mdb,
he started getting these error messages, they took turns between the accounting package and Access, with different messages, including systems,
the fix was a format and reinstall everything back,
a month or 2 later the same problem,
Then I had to move him to WinXp pro, on the same PIII PC with office 2k,
No problem for about 6-9 months, then it started again,
Looking deeper in his PC, No virus, but I could find some of the internet spyware,
I removed it along with all the unnesssacery stuff,
Well the PC is back to normal again, for how long?
So I guess its a matter of what's in that PC.
Sometimes a Bad hardware can cause these problems too, especially the NIC.
Although I hate formating, but nothing better than a nice Full format and reinstall ONLY minimum software, AND instructing the user not to install anything.
I hope this piece of experience will help,
jaffer
I subscribed to this Q hoping someone will pop in so that I benefit too,
Let me tell you my case,
We have in our office identical PCs and the same OS and Office 2k,
and No problem.
PIII, WinME, Office 2k.
The Account is using his oun accounting package, besides our developed project tracking mdb,
he started getting these error messages, they took turns between the accounting package and Access, with different messages, including systems,
the fix was a format and reinstall everything back,
a month or 2 later the same problem,
Then I had to move him to WinXp pro, on the same PIII PC with office 2k,
No problem for about 6-9 months, then it started again,
Looking deeper in his PC, No virus, but I could find some of the internet spyware,
I removed it along with all the unnesssacery stuff,
Well the PC is back to normal again, for how long?
So I guess its a matter of what's in that PC.
Sometimes a Bad hardware can cause these problems too, especially the NIC.
Although I hate formating, but nothing better than a nice Full format and reinstall ONLY minimum software, AND instructing the user not to install anything.
I hope this piece of experience will help,
jaffer
ASKER
I have tired re-installing many times, sometime it helps and somestimes it does not.
The problem seems to work on some hardware and not others. I would agree with the dirver theory but except that this problem started happening on 2 PC all al the same time. Nothing had change on thouse PC which had been working with this access database for many months.
It kind of seems like some DLL's are conflicting and causing this problem. Im not sure what is causing the crash that starts the DLL's to conflict but once we get that crash access is hosed.
The problem seems to work on some hardware and not others. I would agree with the dirver theory but except that this problem started happening on 2 PC all al the same time. Nothing had change on thouse PC which had been working with this access database for many months.
It kind of seems like some DLL's are conflicting and causing this problem. Im not sure what is causing the crash that starts the DLL's to conflict but once we get that crash access is hosed.
Did you upgrade/update Windows OR any other software on those machines?
OR install any program?
Even Google bar or Yahoo bar might case the problem.
Well, our accountant is the kind who installs things on his PC without telling me, so you know what I mean.
Can you run another Access mdb on these machines and see if they crash, lets try to isolate the network from the problem.
OR install any program?
Even Google bar or Yahoo bar might case the problem.
Well, our accountant is the kind who installs things on his PC without telling me, so you know what I mean.
Can you run another Access mdb on these machines and see if they crash, lets try to isolate the network from the problem.
ASKER
I can not explain why this just all of a sudden started happening but what ended up being the problem was the default printer driver. I know is make not sence, but for whatever reason this driver must have changed on my problem systems and for some reason Access did not like this new driver.
The problem would happen when we ran reports that would auto email, which needs the printer for some reason.
It was a fluke that we even figured it out, but it seems to have solved the problem.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It was more the driver as apposed to the hardware, but I will give you the points anyways. You were the only one that responded.
Thank you
Thank you
Well, its the chicken and the egg stuff.
Thanks for the points anyway.
I learned something new too.
jaffer
Thanks for the points anyway.
I learned something new too.
jaffer
ASKER