Access 2010 SP1 – You receive random crashes in certain database or when opening the VBA window in those databases after installing Office 2010 SP1

Anonymous
2011-07-20T15:29:21+00:00

Issue:

After installing Office 2010 SP1, you may receive random crashes when opening objects in certain databases and when trying to open the VBA window in those databases.  If you look in the event viewer the crash info may look similar to the following:

Faulting application: msaccess.exe

Version: 14.0.6024.1000

Stamp: 4d83e4fc

faulting module: vbe7.dll

version: 7.0.16.19

stamp: 4d430aec

Workaround:

UPDATE: Microsoft is aware of the issue and has scheduled a fix to the VBE7.dll in the October 2011 Cumulative Update.  You can workaround the issue by performing the following steps to decompile and recompile the database.

1.      Make a copy / backup of your database.

2.      On the problematic machine decompile the database by running the following from a Run command line:  <path to database file> /decompile ex. C:\test.accdb  /decompile

3.      Close the database.

4.      Open the database again normally.

In addition to this, if you experience the crash please send the error report when prompted to do so after the crash.

2625046 Access 2010 crashes in VBE7.DLL after installing Office 2010 SP1

http://support.microsoft.com/default.aspx?scid=kb;EN-US;2625046

Best Regards,

Nathan Ost

Microsoft Online Community Support

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2011-10-29T04:36:47+00:00

Hey Everyone,

It looks like the hotfix for this issue has been released and can be downloaded from the link below:

Description of the Access 2010 hotfix package (Vbe7-x-none.msp): October 25, 2011 - http://support.microsoft.com/kb/2596585

In addition to this, KB 2625046 which describes this issue will also be updated to point to the fix above.

Best Regards,

Nathan Ost

Microsoft Online Community Support

Was this answer helpful?

4 people found this answer helpful.
0 comments

203 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2011-11-09T21:06:01+00:00

    I have office 2010 installed (including Access) and Office Service Pack 1.  I am running Windows 7 home premium (x64) with Service Pak 1.  When I try to install the hotfix for this proble, it says "There are no procducts affected by this package insalled on this system".  The hotfix I amk trying to install is "office2010-kb259685-fullfile-x640gib.exe.

    What do I do now?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2011-11-09T17:38:49+00:00

    Hi Johnmahoney,

    Based upon the version of the VBE7.dll file in your crash log, it doesn’t appear you have the hotfix installed.  The crash log is showing 7.0.16.19 for your VBE7.dll and the updated version in the hotfix would be 7.0.16.25.  I would try downloading the hotfix again and make sure you download the fix for the bit version of Access you are running.  If you are running Office 2010 32 bit, then you will want to install the X86 (32 bit) fix.  After you download the fix, you will also want to make sure you run the .exe file that you download to actually install it.

    Best Regards,

    Nathan O.

    Microsoft Online Community Support

    Was this answer helpful?

    0 comments
  3. Anonymous
    2011-11-09T17:01:22+00:00

    Faulting application name: MSACCESS.EXE, version: 14.0.6024.1000, time stamp: 0x4d83e4fc

    Faulting module name: VBE7.DLL, version: 7.0.16.19, time stamp: 0x4d430aec

    Exception code: 0xc0000005

    Fault offset: 0x00023081

    Faulting process id: 0x494

    Faulting application start time: 0x01cc9effb3a9b6ef

    Faulting application path: C:\Program Files (x86)\Microsoft Office\Office14\MSACCESS.EXE

    Faulting module path: C:\PROGRA~2\COMMON~1\MICROS~1\VBA\VBA7\VBE7.DLL

    Was this answer helpful?

    0 comments
  4. Anonymous
    2011-11-09T16:25:37+00:00

    Hi John,

    Unfortunately, like other users have mentioned, I have seen this same type of error happen in Access 2010 before SP1 was installed and in other versions of Access, so it is tough to guarantee some update caused it.  With that being said, there always is a chance that an update could have caused another issue.  If we can pinpoint a certain update that is causing the issue or if you can find a way to consistently reproduce the issue, then it may be beneficial to start a new thread to address that issue.  The problem with reporting all these issues in this same thread is it makes it tough to follow all of the different questions that are being asked or scenarios people are running into.

    If in fact you need this to be addressed immediately, then your best option will be to open a case because as mentioned, unless we have a way to isolate the problem and get a consistent repro of the issue, there isn’t much I can do to narrow down the problem.

    Best Regards,

    Nathan O.

    Microsoft Online Community Support

    Was this answer helpful?

    0 comments