- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
Other questions
Adding another voice to this thread as it is happening to us as well. We have QB installed on 2 servers both are Windows Server 2019. I tried a repair of QB using the Tools Hub and saw it reinstalled the C++ redistr as needed, but it did not help.
I can also confirm that this fix worked for us:
1. Close QuickBooks.
2. Copy D3DCompiler_47.dll from C:\Windows\System32\.
3. Paste into the QuickBooks installation folder (C:\Program Files\Intuit\Quickbooks 2024\).
4. Open QuickBooks again. The error should not be present.
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
Other questions
I ran into the same error. Everything was working fine until I updated QuickBooks 24 on server 2019. The mapi64 error suggests it had to do with email. What I found out worked was after the update, I uninstalled Office 64 bit rebooted and then installed Office 32 bit. The error went away and everything worked as it should again. It seems to be an issue with 64bit Office and QuickBooks after the update. Hope that helps someone else.
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
Other questions
Yes, with windows server 2019 through a VPN about 3 weeks ago.
I spent 3 hours on the phone with a great technician, and many tries to work around, that this recent update does not work in windows server 19!!!! I am currently using my server as a data base server and running QuickBooks 24 Enterprise off my computer and have a mapped drive through my VPN as a work around.
This is horribly SLOW!
They know what is happening, so I am just patiently waiting for an update to resolve this. I am sure there are others who are having the same issue. No fix yet.
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
Other questions
- Close all QuickBooks instances (use Task Manager to kill qbmapi64.exe if necessary).
Locate C:\Program Files\Intuit\QuickBooks 2024\ (or your specific year).
Rename D3DCompiler_47.dll to D3DCompiler_47.dll.old.
Copy D3DCompiler_47.dll from C:\Windows\System32 and paste it into your QuickBooks installation folder.
This was our fix that worked. QB is such garbage software, intuit should be ashamed
- Close all QuickBooks instances (use Task Manager to kill qbmapi64.exe if necessary).
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
Other questions
Close all QuickBooks instances (use Task Manager to kill qbmapi64.exe if necessary).
Locate C:\Program Files\Intuit\QuickBooks 2024\ (or your specific year).
Rename D3DCompiler_47.dll to D3DCompiler_47.dll.old.
Copy D3DCompiler_47.dll from C:\Windows\System32 and paste it into your QuickBooks installation folder.
This was our fix that worked. QB is such garbage software, intuit should be ashamed.
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
Other questions
Bless your family for generations
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
Other questions
I just tried this and resolved our issue! THANKS MonopolyChamp!!
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
Other questions
Solved my issue QB Enterprise 24 on Server 2019.
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
Other questions
This error isn’t related to your QuickBooks file at all, it’s a Windows/runtime issue. The qbmapi64.exe entry point error with D3DCOMPILER_47.dll and CxxFrameHandler4 usually means your system is missing or has a broken Visual C++ component that QuickBooks depends on. That’s why support is pushing it off — it’s not strictly a QB data issue, but it still affects QB.
The fix is pretty straightforward: install or repair the Microsoft Visual C++ Redistributables (2015–2022, both 32-bit and 64-bit), run full Windows updates, and restart your system. You can also run the QuickBooks Install Diagnostic Tool to repair dependencies. Once those system components are fixed, QuickBooks should open normally. This isn’t file corruption, so tools like Stellar wouldn’t be relevant here unless the problem continues after fixing the system, which is unlikely for this specific error.
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
Other questions
This was the fix. Definitely a bad packaged .DLL on QB side.