Access 2013 Crashing

JamesSF

New member
Local time
Yesterday, 22:49
Joined
May 5, 2014
Messages
4
Hello - first time poster

I have an accdb running Access 2013 on Windows server 2012 R2/Windows Pro 8.1.

We are getting random crashes several times per hour - beginning a few months ago.

This is the error:

Problem signature:
Problem Event Name: APPCRASH
Application Name: MSACCESS.EXE
Application Version: 15.0.4601.1000
Application Timestamp: 530c82b1
Fault Module Name: acedao.dll
Fault Module Version: 15.0.4569.1503
Fault Module Timestamp: 52b0bead
Exception Code: c0000005
Exception Offset: 0000000000032375
OS Version: 6.3.9600.2.0.0.16.7
Locale ID: 1033

Notice the fault module is a different version than the application version - could this be a problem?

I have tried the usual suspects: decompile/recompile, export/import from text, new db shell, compact/repair

references include:
Outlook 15 object library - MSOUTL.OLB
XML v6.0 - msxml6.dll

Application has about 190 forms - some with navigation controls and with web browser controls.

any ideas?

thanks in advance.


 
A quick check online for appcrash and acedao.dll indicates the problem seems to occur when office is upgraded and/or changed from 32bit to 64bit.

You could try removing all references, save the file then add them back in again.

Otherwise the solution seems to be to reinstall office and/or access.

Another suggestion, probabably only relevent if only a single user is that there is a corruption in the .dll file
 
Thanks for the suggestions

These are all brand new installs of Office 2013 64 bit on brand new PCs and new Windows server. It happens on all PCs and the terminal server for all users.

Not only will it crash randomly on different forms and locations, it will crash for me when I press the compact/repair button or even copy and paste code in a vba module.
 
So you are saying the problem occurred when you installed Office 64bit?

It suggests to me that the program was written in 32bit so you need to modify any API calls to cater for 64bit. If you are using any 3rd party software these may also need to be upgraded to 64bit.

With regards the API calls, check all of your code modules for things like

Public Declare Function ....
Private Declare Function ....

And change them to

Public Declare PtrSafe Function ....
Private Declare PtrSafe Function ....
 
hmm. ok

I remember changing a few of them, but since it compiles ok - I thought I got them all. ill manually check everything now.

-> All declares have the PTRsafe
 
Last edited:

Users who are viewing this thread

Back
Top Bottom