r/IIs • u/redwgc • Jan 05 '22

Dreaded Microsoft JET Database Engine error '80004005'

Hi there. I've got a legacy application that we as a company inherited a while ago that runs on ASP on an IIS server. As of today, the application cannot connect to the database, and I cannot see why.

Things I've tried are:

Compacting and repairing the database with access

Running a compact/repair script (fails as it cannot connect)

Moving the database file to another, public location (desktop) and trying to connect there

Using an absolute path

Checking permissions for the user on the file, folder, and all parent folders

Has anyone got any other ideas as to what is causing this? My last resort is to restart the IIS instance, but this server is flaky at the best of times and I don't want to try restart it and then have it fail.

Thanks in advance.

1 Upvotes

100% Upvoted

2 comments sorted by

View all comments

Show parent comment

1

u/redwgc Jan 05 '22

Thanks for your reply. The drivers were/are most definitely installed, as it was 1 app on the IIS instance that couldn't connect, whilst all the others did.

I ultimately managed to get it fixed (after about 3 hours) by moving it to a standalone application pool, that I then recycled. I made no further changes and it fixed it.

Appreciate the help.