MS Access Database Engine 2016 ERROR

[JeffatPrimex]

This is a joke right?

The only way to fix this for a DAY is to Reinstall Office Completely!

Please Someone Find a Fix!

ASAP!

[jallenDBQ7U]

I have the same error.   Could this be related to a Microsoft Update?  I haven't had an active update this week but who knows what IT does when my computer boots.

Patch Tuesday is usually the second Tuesday of each month.

[OP21]

I had the same issue after launching 2023  after installing the update it seems to be working.

https://knowledge.autodesk.com/support/autocad-electrical/troubleshooting/caas/sfdcarticles/sfdcarti...

[jallenDBQ7U]

The only problem is that the path they provide in that solution doesn't work for everyone.   ACADE 2022 didn't put a folder there for me.

[OP21]

Ok.  Try downloading the update from Microsoft.

https://knowledge.autodesk.com/support/autocad-electrical/troubleshooting/caas/sfdcarticles/sfdcarti...

After some extra digging, it seems that Autodesk also posted this:

https://knowledge.autodesk.com/support/inventor/troubleshooting/caas/sfdcarticles/sfdcarticles/Probl...

Their caveat if it doesn't work, try re-installing Office... 😞 which returns you back to square one....

[jallenDBQ7U]

It does appear that MS Access update does fix this bug (based on coworker results) but one must wonder why.  I have done software applications for database access with MS Access format.  They did not require MSOffice to be installed to run.   They also were not impacted by changes to MSOffice if it is installed or modified.  Obviously AutoDESK has issues they are not willing to fix.  They create numerous folder structures in user and public locations yet they can't put their own engine files there?  We are likely in a time bomb where this same drum will be played again.

[Nick_Hall]

If anyone is still having issues with this, here is a link to my problem, and the solution that worked for me

https://forums.autodesk.com/t5/autocad-electrical-forum/quot-microsoft-access-database-engine-quot-e...

Hopefully someone finds it useful

Nick

[JeffatPrimex]

I have ACE 2022 and 2023 installed with Office 365 version 16.0.14326.20852 and MS Access database enging 2016 16.0.5044.1000 and all is working fine. My custom apps using MS Excel com interop have not crashed. Once I got it all to run it would break the very next day. My solution was to disable all the office update tasks and triggers in Task Scheduler.

We'll see how long this works,

Best regards,

Jeff

[jallenDBQ7U]

Changing it to manual is okay, but I would recommend that you manually do an update check on a regular basis.  You can then have your MS Access engine update ready to do at the same time if Microsoft says it is needed.

I am not familiar with specific changes Microsoft is doing, but suspect it is quite often security changes.  A lot of big name companies have been infiltrated to steal data or nailed with ransomware lately.  The hackers now have entire suites of software such that if you accidentally click on a link that accesses a site they either control (or have hacked), it will open a hidden window and probe for what you may be using that isn't updated leaving an open door for them to get into your computer.   Microsoft got hacked not too long ago.

I think this link explains what we recently saw on the update issue.

https://thehackernews.com/2022/04/microsoft-issues-patches-for-2-windows.html 

[JeffatPrimex]

This is not a soultion it is a work-a-round until MS gets their act together and fixes it. What everyone here has suggested should help lead them to the cause.

Going back to an earlier verision is no different than not updating so what's the difference!

Best regards,
Jeff

[jallenDBQ7U]

Is it still occurring in ACADE Version 2023?  I haven't had a single additional instance since installing the update on version 2022.

EDIT*  I have Office 365 and get automatic updates (our IT department controls ours - I can't set to manual)
EDIT2* I don't blame MS on this.  I blame AutoDESK.  They should lock down third parties from impacting code by installing their own version of the DB engine.

[JeffatPrimex]

Yes ACE 2023 is working fine with MS access db enging 2016 on my system. As Nick_Hall's link reports MS is aware of this issue and have not come up with a solution. I'll stick with my work-a-round until it is fixed. I had enough with filedia, filedia, filedia!

Best regards,

Jeff 

[jallenDBQ7U]

That link is two weeks old.  Every company has issues occur on their software.  The key is to control your own where possible.  AutoCAD is getting dragged along on a Microsoft software issue only because AutoDESK is lazy and doesn't want to do software updates of their own.  We've had zero problems with Office 365 and have around a hundred users in our building here.

Since I updated the WD.env file I haven't had any occurrences of the FILEDIA issue.  The script automatically sets it to 1 routinely in the program, so if it does occur I don't see it.

[jallenDBQ7U]

Surprise Surprise.  It looks like I get to do the MSAccess reinstall again for version 2022.  I wish I could put my updates on manual like you.  At least I could then control when the update occurs instead of having AutoDESK shut me down right when I need to get work done.

What is crazy on this issue is that AutoDESK will do nothing hoping MS fixes it for them.  Maybe it will be gone by the time version 2024 or version 2025 arrives.

[zalant]

I just posted some information about this issue over in Nick's post from the other day. Hopefully, the additional details there will help to alleviate some of the frustration we're all dealing with on this one. To give some perspective, AutoCAD Electrical has always used Access MDB files so we've always relied upon the Access Database Engine. This goes back to before we purchased the product from VIA all those years ago. The recent shift in the way Office works, in general, is affecting any software vendor who has leveraged ODBC and other components of Office in their programs, us included. Our usage of the Access Database Engine is not unlike leveraging .NET Framework, Visual C++, or other programming structures that Microsoft makes available for all developers who make programs that run on Windows. At any point, a change to those underlying Windows components could impact all companies who rely on them for basic functionality. Some may call that arrangement a house of cards, and that (being a software company) we should just build/write everything ourselves, in-house to prevent having to rely on Microsoft substructures that can change without warning, but such is the software industry at this moment; we'll likely not be writing our own database engine driver any time soon. For now, our developers will continue to work on fixing this and all issues that affect our users, and I'll be here helping out on the Electrical support side of things. Thank you all.  

[phil.bunce]

Annoying isn't it !!

I found that closing down ACE 2022... go to Add / Remove Programs.. delete the accessdatabase_.. re-install the new one (that hasn't changed by the way), and you are good to go.  It takes a few minutes.. Actually I keep a copy resident on my HDD now as this has happed a few times to me.  Still, it is a royal pain in the ass and I need it to sop.

Phil

[zalant]

I've found that it's unnecessary to actually un/reinstall the Access Database Engine if you modify one specific registry key. Once you've done so, you can export that key to a .REG file, so the next time it happens, you can double-click it (the .REG file) to change the key back to a working state. Full details in my post here.

Also, un/reinstalling the Access Database Engine has the unwanted side effect of breaking Excel data links with AutoCAD, so that subsequently needs fixing (unless you don't need that feature to work).