Access 11 crash

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

One of our customers is running an application on MS Access 11 (on windows xp).
Sometimes they get the error:
"Microsoft Office Access has encountered a problem and needs to close. We
are sorry for the inconvenience"
This may happen a few times a day, while previewing a report, or while
editing a sales order, or while performing different unrelated business
transactions.
Other customers are running the same application of MS Access 11 without
problems.
How can we correct this problem? Thank you!
Here is what I get when I look at the error logged in the event viewer:

Type de l'événement : Erreur
Source de l'événement : Microsoft Office 11
Catégorie de l'événement : Aucun
ID de l'événement : 1000
Date : 05-01-05
Heure : 07:56:46
Utilisateur : N/A
Ordinateur : JOHANNE
Description :
Faulting application msaccess.exe, version 11.0.6355.0, stamp 40aa97a8,
faulting module msaccess.exe, version 11.0.6355.0, stamp 40aa97a8, debug? 0,
fault address 0x00007e8f.

Pour plus d'informations, consultez le centre Aide et support à l'adresse
http://go.microsoft.com/fwlink/events.asp.
Données :
0000: 41 00 70 00 70 00 6c 00 A.p.p.l.
0008: 69 00 63 00 61 00 74 00 i.c.a.t.
0010: 69 00 6f 00 6e 00 20 00 i.o.n. .
0018: 46 00 61 00 69 00 6c 00 F.a.i.l.
0020: 75 00 72 00 65 00 20 00 u.r.e. .
0028: 20 00 6d 00 73 00 61 00 .m.s.a.
0030: 63 00 63 00 65 00 73 00 c.c.e.s.
0038: 73 00 2e 00 65 00 78 00 s...e.x.
0040: 65 00 20 00 31 00 31 00 e. .1.1.
0048: 2e 00 30 00 2e 00 36 00 ..0...6.
0050: 33 00 35 00 35 00 2e 00 3.5.5...
0058: 30 00 20 00 34 00 30 00 0. .4.0.
0060: 61 00 61 00 39 00 37 00 a.a.9.7.
0068: 61 00 38 00 20 00 69 00 a.8. .i.
0070: 6e 00 20 00 6d 00 73 00 n. .m.s.
0078: 61 00 63 00 63 00 65 00 a.c.c.e.
0080: 73 00 73 00 2e 00 65 00 s.s...e.
0088: 78 00 65 00 20 00 31 00 x.e. .1.
0090: 31 00 2e 00 30 00 2e 00 1...0...
0098: 36 00 33 00 35 00 35 00 6.3.5.5.
00a0: 2e 00 30 00 20 00 34 00 ..0. .4.
00a8: 30 00 61 00 61 00 39 00 0.a.a.9.
00b0: 37 00 61 00 38 00 20 00 7.a.8. .
00b8: 66 00 44 00 65 00 62 00 f.D.e.b.
00c0: 75 00 67 00 20 00 30 00 u.g. .0.
00c8: 20 00 61 00 74 00 20 00 .a.t. .
00d0: 6f 00 66 00 66 00 73 00 o.f.f.s.
00d8: 65 00 74 00 20 00 30 00 e.t. .0.
00e0: 30 00 30 00 30 00 37 00 0.0.0.7.
00e8: 65 00 38 00 66 00 0d 00 e.8.f...
00f0: 0a 00 ..
 
Hi Groupe LCM,

Thanks for your posting!

From your descriptions, I understood that the Access crashes when it is
fine on other computers. Correct me if I was wrong.

First of all, please make sure you have upgraded to the latest service pack

Information about Jet 4.0 Service Pack 8
http://support.microsoft.com/kb/829558

Microsoft Data Access Components (MDAC) 2.8
http://www.microsoft.com/downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-
b037-185d0506396c&DisplayLang=en

Windows Update
http://windowsupdate.microsoft.com/

Office 2003 Service Pack 1
http://www.microsoft.com/downloads/details.aspx?FamilyID=9c51d3a6-7cb1-4f61-
837e-5f938254fc47&DisplayLang=en

Keep the latest updates for both your system and Access

Secondly, what kind of operation you do when Access crashes, or it crash
randomly? Generally speaking, this kind of crashes might be caused by
various factors and it's diffcult to locate the root cause in the newsgroup
thread. To effective troubleshooting this issue, we recommend that you
contact Microsoft Product Support Services and open a support incident and
work with a dedicated Support Professional. For a complete list of
Microsoft Product Support Services phone numbers, please go to the
following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp

Thirdly, I am not sure whether it is possible for your customer to
reinstall his box from Windows, I believe there must be something corrupted
system files.

Hope it helps.

Thank you for your patience and corporation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!


Sincerely yours,

Michael Cheng

Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
 
I received a similar type of error. In my case I traced to users accessing a
Access 2000 database using Access 2000 and Access 2003 (at the same time).
My solution was to convert the database to Access 2002/2003, effectively
eliminating anyone from opening the database using Access 2000. That seems
to have worked for me.
 
Back
Top