qbmapi64 ERROR!!!

Which QB Desktop year version and Windows OS do you run?

Can you open the sample file?

We are running into the same error at my company on QB Enterprise 24 R19 running on Windows server 2019 when trying to open a file. Also selecting Help>About Automatic Update causes the error to pop up.

We restored back to QB R18_67 and everything is working.

Also having this error even when opening the sample company file.

Windows Server 2019

QB Enterprise 24

Hello, SrTeM and Max. The main reason this error pops up when opening a file is a compatibility issue between QuickBooks 2024 (or later) and your Microsoft components. The QuickBooks program was recently updated to a version that requires Microsoft Visual C++ 2015-2022 redistributable (version 14.38 or higher) to function properly. If your computer is using an older version of that library, QuickBooks attempts to call a command that does not yet exist in your system files.
 

To resolve this, please download and run the QuickBooks Tool Hub. Under Step 2, navigate to the Installation Issues tab. From there, run the QuickBooks Install Diagnostic Tool to repair the Microsoft Visual C++ and .NET Framework components.
 

If the error persists after running this tool, you can perform a manual repair by uninstalling and reinstalling Microsoft Visual C++. You can refer to this article for the complete steps: Uninstall or reinstall Microsoft Visual C++.
 

If you’re still seeing the error after these steps, please perform a clean installation of your software to ensure all necessary components are updated.
 

If you're hesitant to perform these steps on your own, you can contact our QuickBooks Desktop Live Support team or your local IT professional for assistance.

Please don't hesitate to leave us a response if you have other questions or concerns.

I performed all the suggested fixes but none of them worked. How can I rollback to r18? I don't have an older installer currently.

I performed all the suggested fixes but none of them worked. I still receive the error when opening the sample company file.

How can I rollback to R18? I don't have an installer from that version.

I appreciate your efforts in performing the suggested fixes, Max. Currently, the latest patch available for download from the official download site is the newer release (r19).

Since you have already gone through all the recommended troubleshooting steps and the issue persists, I suggest reaching out to our live support team. They have the right tools and permissions needed to identify the exact cause of the crash that standard troubleshooting can't fix. 

Start by going to the Help menu and selecting QuickBooks Desktop Help/Contact Us, which will open the Help window. In the search field, type in your question using relevant keywords and click on Contact Us, where you can choose to get a callback or chat with us. You can check their support hours to ensure you receive timely assistance.

Feel free to add a reply below if you have other concerns.

Same issue here.  Just did a QuickBooks update and got this same issue.  These errros happen 9 times out of 10 with QuickBooks updates.  Really wish there was good alternative.  I have tried the QuickBooks Tool Hub, reinstalling DirectX, reinstalling C++.  Nothing works.

We have the same issue. Ran all the toolhub, completely uninstalled and reinstalled, installed VC_redist, ran SFC. It's a QUICKBOOKS ISSUE.
FIX IT QUICKBOOKS.

This is ridiculous. I've done all the ToolHub, reinstalled several times, did SFC, DISM, redistributable download, fresh install from an old version to update, fresh install from the new version to update, windows updates, and it still has this error.

This is obviously on your end Intuit, I'm having to restore the entire server to yesterday before the update just so people can work, this isn't acceptable at all, stop putting out updates without testing them.

We have quite a few clients who ran the same error after upgraded to R19. We also spent an hour or so with QB support. Basically they (developers) are not addressing this issue at the moment or willing to fix.

This error is not across the board for our customers. The only thing they have in common was that their QuickBooks Enterprise 2024 are installed on Windows Server 2019 virtual environment because we host them in Azure. 

For the other customers who have their QuickBooks Enterprise 2024 installed on Windows Server 2019 physical servers or Windows Server 2022 on a VM (Azure), we are not seeing this error. 

So the workaround for us was to upgrade the server to Windows Server 2022 version.(with fresh installation of QB) It's been running 10 hours so far and no errors. 

Following this thread and anxiously awaiting a solution!  Experiencing this exact issue with 2 of our 5 users working remotely via VPN.  We have been unable to resolve using all the recommendations.  It makes our work incredibly dysfunctional.

We are seeing same error on Windows Server 2019 (physical server). Reverting back to 2023 for now. Quickbooks please address this issue!!

We are seeing the same error here in Windows Server 2019 (physical server). Reverting back to 2023 for now until this is resolved. Quickbooks please look into this!

I was able to resolve this issue for an instance of QuickBooks Premier Accountant running on a virtual instance of Server 2019 that multiple users access via RDP, all running QuickBooks under their own user sessions. Based on what worked I see no reason it wouldn't apply in other environments.

The version of D3DCompiler_47.dll that QuickBooks installs does not work; renaming or removing it just prompts QuickBooks to reinstall the same bad copy. The following steps did resolve:

1. Close out all instances of QuickBooks (may need to kill the qbmapi64.exe process).
2. Rename the copy of D3DCompiler_47.dll to D3DCompiler_47.dll.old in the install folder. Typically  this would be C:\Program Files\Intuit\QuickBooks 2024\
3. Locate the system copy of D3DCompiler_47.dll in System32 (C:\Windows\System32)
4. Copy this file and paste it into the QuickBooks install folder (C:\Program Files\Intuit\QuickBooks 2024\)

This resolved the issue for me.

The underlying cause appears to be a bad version of D3DCompiler_47.dll packaged with the latest release of QuickBooks 2024.

Has anyone gotten anywhere with Intuit yet on this issue?  We have the exact same situation - running QB on a virtual machine, which I have to believe is a very common thing.  Our IT company says that everyone they know of running QB locally does so on a server that is a VM, not physical.

Clearly, this is something that Intuit needs to step up & fix, if they haven't already.  I can confirm that I ran the QB update on 3/14 and got this failure.  The only solution I know of is to uninstall & reinstall QB, then intentionally NOT update it....

Intuit, it is ridiculous for you to hide behind the VM story to avoid this issue.  Let's see if we can determine how many companies are affected by this -- please comment on this thread & let us know!

This solution worked for us!

This resolved my Issue with QB 2024 Pro Plus

I found a solution!

• Press Win + R, type C:\Windows\System32 and hit Enter
• Find D3DCOMPILER_47.dll in that folder
• Copy it and paste it to: C:\Program Files\Intuit\QuickBooks 2024\
• When prompted, choose Replace the file
• Restart QuickBooks

Thanks Quickbooks. This is clearly an issue on their side. Fix this now.

Good evening,

If you're experiencing the qbmapi64 error upon logging into QuickBooks Desktop Enterprise 2024 on Server 2019, please try the below, as this just resolved it for my clients.

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. 

Please let me know if this worked for your issue. 

This worked for me as well, running Enterprise 24. I was told by Intuit that they do not  support virtual networks when we have been running it on VPN from the beginning of time. Time to find a contemporary saas replacement

We updated yesterday and have the same issue! It is criminal that Intuit mandates these updates but then shrugs their shoulders when their updates cause problems. I have not seen any updates yet that actually fix the bugs I would like to see fixed and we have not had an upgrade of QB that has not caused some sort of problem.

This fix worked for me. I tried everything above that others suggested, but the renaming and copying worked! Thanks