leeroypitre
asked on
ACCDE crashes
Using MS Access 2013, I've developed an application that's been running fine for over a year. Once development is completed on changes, I use debug compile to make sure no issues are found. Then I create an ACCDE and push the new release into out testing environment.
Something changed about a week ago. The ACCDB copy run fine. However, now each and every time I create a new ACCDE and try to launch the ACCDE it crashes every time.
I have spent numerous hours researching and have no idea what is causing this. I've attached a screen capture of the MS Access crash window.
VBA compiles cleanly. New ACCDE files from those affected ACCDB files still crash.
The plot thickens. Spent last Thursday & Friday recovering from an older ACCDB that compiles and ACCDE runs. At 7am I stopped, compacted, decompiled, made ACCDE. Runs fine. So made a backup of my ACCDB. At 8am, did same thing. Everything fine. At 10am did same thing, everything fine, made new backup. At 11am packed, decompiled, made ACCDE. Crashes. Copied back my 10am ACCDB. Made ACCDE, crashes. Went to my 8am backup. made new ACCDE, crashes.
I also attached a zipped copy of the error exported from the system event viewer.
This is driving me crazy. I cant work under these conditions. Any help will be greatly appreciated. I'm at a complete stand still until I figure this out.
MS-Access-2013-error-20190816-0734.zip
Capture.JPG
Something changed about a week ago. The ACCDB copy run fine. However, now each and every time I create a new ACCDE and try to launch the ACCDE it crashes every time.
I have spent numerous hours researching and have no idea what is causing this. I've attached a screen capture of the MS Access crash window.
VBA compiles cleanly. New ACCDE files from those affected ACCDB files still crash.
The plot thickens. Spent last Thursday & Friday recovering from an older ACCDB that compiles and ACCDE runs. At 7am I stopped, compacted, decompiled, made ACCDE. Runs fine. So made a backup of my ACCDB. At 8am, did same thing. Everything fine. At 10am did same thing, everything fine, made new backup. At 11am packed, decompiled, made ACCDE. Crashes. Copied back my 10am ACCDB. Made ACCDE, crashes. Went to my 8am backup. made new ACCDE, crashes.
I also attached a zipped copy of the error exported from the system event viewer.
This is driving me crazy. I cant work under these conditions. Any help will be greatly appreciated. I'm at a complete stand still until I figure this out.
MS-Access-2013-error-20190816-0734.zip
Capture.JPG
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Have you tried decompiling, compacting, compiling & compacting?
Have you tried creating a new blank db and imported everything?
Is everyone running Access 2013?
Is everyone running the same build no?
Have you tried creating a new blank db and imported everything?
Is everyone running Access 2013?
Is everyone running the same build no?
@kelvin
The eventlog he attached clearly refers to sentinelOne....so that would be the FIRST thing to look into.
But sure, it could be anything, windows patch, defective sectors on harddrive, neighbours cat chewing on powercable.... :-)
Edit: For all readers that didn't check the Eventlogfile Leeroypitre (the asker) provided us with:
The eventlog he attached clearly refers to sentinelOne....so that would be the FIRST thing to look into.
But sure, it could be anything, windows patch, defective sectors on harddrive, neighbours cat chewing on powercable.... :-)
Edit: For all readers that didn't check the Eventlogfile Leeroypitre (the asker) provided us with:
Faulting application name: MSACCESS.EXE, version: 15.0.5045.1000, time stamp: 0x5b0d194c
Faulting module name: InProcessClient32.dll, version: 3.2.4.54, time stamp: 0x5d13626b
Exception code: 0xc0000005
Fault offset: 0x00048d3e
Faulting process id: 0x1118
Faulting application start time: 0x01d5542eefa5b177
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\MSACCESS.EXE
Faulting module path: C:\Program Files\SentinelOne\SentinelAgent 3.2.4.54\InProcessClient32 .dll
Report Id: d736e5d9-6375-439b-8c82-2af50e59f577
Faulting package full name:
Faulting package-relative application ID:
Are you the only developer ?...do you develop on more than 1 machine ?...anything else we might missing ?
The way you describe it seems like you have a problematic reference that in one machine works because it's the correct version A.A.B ...on the other machine this doesn't work because it looks for Version A.A.B but you have installed version A.A.A
I have encountered this and it was a nightmare...and we are talking about (i think it was mscomctl) difference in version e.g. 6.1.98.32 to 6.1.98.35 (imaginary numbers i can't remember the correct ones but the version difference was almost negligible )
The way you describe it seems like you have a problematic reference that in one machine works because it's the correct version A.A.B ...on the other machine this doesn't work because it looks for Version A.A.B but you have installed version A.A.A
I have encountered this and it was a nightmare...and we are talking about (i think it was mscomctl) difference in version e.g. 6.1.98.32 to 6.1.98.35 (imaginary numbers i can't remember the correct ones but the version difference was almost negligible )
As Thomas said:
and ditto that. They've got anti-virus that's hooking itself to the process, and that's what faulted. The first step they need to do before anything else is get sentinel one out of the picture.
And maybe I got out of the wrong side of the bed this morning or something, but I wish you guys would take the time to read and understand the problem before polluting the thread with comments that don't yet apply.
if you have any comments regarding this comment, please private message me. I don't want another member complaining that they had to give up because they ended up with a thread they found confusing and over whelming.
Jim.
The eventlog he attached clearly refers to sentinelOne....so that would be the FIRST thing to look into.
and ditto that. They've got anti-virus that's hooking itself to the process, and that's what faulted. The first step they need to do before anything else is get sentinel one out of the picture.
And maybe I got out of the wrong side of the bed this morning or something, but I wish you guys would take the time to read and understand the problem before polluting the thread with comments that don't yet apply.
if you have any comments regarding this comment, please private message me. I don't want another member complaining that they had to give up because they ended up with a thread they found confusing and over whelming.
Jim.
It could be as simple as a Windows patch - check to updates history of the machine.
Kelvin