Runtime Error -2147319779 (8002801d)

Question

Runtime Error -2147319779 (8002801d)

Lhoyd Henry 5

Anyone can shed light on the issue I'm having.

I have a software Wine software Backoffice, and it was installed on the majority of the computers it mainly runs using MS Access and consists of different modules. One of the modules is starting to not work on some of the computers.

I tried reinstalling the office but still had the same error message

I recreated a test program and mimicked the codes of the disabled module. Run the test on the working machine the test was successful, tried to run it on the computer which has an issue with the software, and it gave me an error message.

Error in Back Office

'Runtime Error -2147319779 (8002801d)

Method currentDb' of object'_Application failed

I tried to uninstall and remove all security, but I did get the same error message. I'm thinking that someone is blocking the app from working I just can't figure out which one.

Is there a way to check which one is interfering? Any possible suggestions that I can check to the system?

Thank you,

Stefan 0 Reputation points

2024-12-18T09:36:38.54+00:00

It seems we got the same problem, but on my side it happens on a customer PC since some days.
Stefan 0 Reputation points

2024-12-18T14:01:27.85+00:00

Our research shows that it seems to currently only affect Windows 11.
Lhoyd Henry 5 Reputation points

2024-12-18T16:00:49.4233333+00:00

Have you found any solution to this? I have been trying a lot of troubleshooting since the last week and none of them works.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Stefan 0 Reputation points

2024-12-19T14:43:14.74+00:00

No it's a mystery currently. Repairing Office didn't work. Setting it back to October did also not bring any results.
Lhoyd Henry 5 Reputation points

2024-12-26T16:14:02.91+00:00

Have you tried wiping the whole device? This was still ongoing not sure what to do anymore.
Stefan 0 Reputation points

2025-01-10T07:54:31.3433333+00:00

On our side the PC's which got the issue where:

Windows 10 + Office 2019

Windows 11 + Office 365

Office 2021 LTSC is also affected (we replaced the Office 2019)

On all cases we know of, only Dell Laptops were affected, but that might just be a coincidence. We suspected some Hardware issue in combination with Software. But we have a test case where we installed a "similar" (Win 11 instead of Win10, Office 2019) system on a different laptop and moved the drive to the system it was not working and afterwards there was no more issue on the previous affected machine. Which indicates that the issue is software based.
Stefan 0 Reputation points

2025-01-10T08:15:03.8866667+00:00
I prepared a test database where this issue can be tested without having to have a whole application. It consists of two databases, one opens the other and tries to access CurrentDB and fails on affected PC's.

Extracted code example:

Dim tApp As Application Set tApp = CreateObject("Access.Application") tApp.OpenCurrentDatabase sys_GetParentFolderName(CurrentDb.Name) & "\" & "Database2.accdb" Debug.Print tApp.CurrentDb.Name

https://pixeldrain.com/u/fShYJm5G

@ Microsoft you can contact us if you want access to a PC where this happens, as it is clearly an issue within Office, just not as widespread as the 2021 issue was...

1 answer

Your answer

Stefan 0 Reputation points

2024-12-18T09:36:38.54+00:00

It seems we got the same problem, but on my side it happens on a customer PC since some days.
Stefan 0 Reputation points

2024-12-18T14:01:27.85+00:00

Our research shows that it seems to currently only affect Windows 11.
Lhoyd Henry 5 Reputation points

2024-12-18T16:00:49.4233333+00:00

Have you found any solution to this? I have been trying a lot of troubleshooting since the last week and none of them works.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Stefan 0 Reputation points

2024-12-19T14:43:14.74+00:00

No it's a mystery currently. Repairing Office didn't work. Setting it back to October did also not bring any results.
Lhoyd Henry 5 Reputation points

2024-12-26T16:14:02.91+00:00

Have you tried wiping the whole device? This was still ongoing not sure what to do anymore.
Stefan 0 Reputation points

2025-01-10T07:54:31.3433333+00:00

On our side the PC's which got the issue where:

Windows 10 + Office 2019

Windows 11 + Office 365

Office 2021 LTSC is also affected (we replaced the Office 2019)

On all cases we know of, only Dell Laptops were affected, but that might just be a coincidence. We suspected some Hardware issue in combination with Software. But we have a test case where we installed a "similar" (Win 11 instead of Win10, Office 2019) system on a different laptop and moved the drive to the system it was not working and afterwards there was no more issue on the previous affected machine. Which indicates that the issue is software based.
Stefan 0 Reputation points

2025-01-10T08:15:03.8866667+00:00

I prepared a test database where this issue can be tested without having to have a whole application. It consists of two databases, one opens the other and tries to access CurrentDB and fails on affected PC's.

Extracted code example:

Dim tApp As Application Set tApp = CreateObject("Access.Application") tApp.OpenCurrentDatabase sys_GetParentFolderName(CurrentDb.Name) & "\" & "Database2.accdb" Debug.Print tApp.CurrentDb.Name

https://pixeldrain.com/u/fShYJm5G

@ Microsoft you can contact us if you want access to a PC where this happens, as it is clearly an issue within Office, just not as widespread as the 2021 issue was...

Answer 1

See https://learn.microsoft.com/en-us/office/troubleshoot/access/running-wizard-error-loading-dll#let-me-fix-it-myself

As described there C2R fixes itself, might be correct in the past, currently that's not working.

On one machine

HKEY_CLASSES_ROOT\TypeLib\{00025E01-0000-0000-C000-000000000046}\5.0\0\win32

was missing.

We made also sure that

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\SOFTWARE\Classes\TypeLib\{4AC9E1DA-5BAD-4AC7-86E3-24F4CDCECA28}\c.0\0\win32

and

HKEY_CLASSES_ROOT\TypeLib\{4AC9E1DA-5BAD-4AC7-86E3-24F4CDCECA28}\c.0\0\win32

points to C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE16\ACEDAO.DLL on a x86 System, on x64 see documentation.

BTW: The documentation is currently wrong as it tells you to look in sub path e.g. "15.0/ClickToRun" but this does not exist. But a parallel folder without the "15.0" is correct.

Share via

Runtime Error -2147319779 (8002801d)

1 answer

Your answer