Operating system: 18363.628 (Windows 10 Pro)
Processor: Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz
RAM: 8 GB
Storage: SSD CT250MX500SSD1
Microsoft Office: 16.0.12430.20264
QuickBooks 29.0.4011.2901 (Enterprise 19)
We have a customer who is currently having issues with emailing from Quickbooks. The first email (invoice) from the Quickbooks causes Quickbooks to totally hang up. The end user then has to use the task manager to kill Quickbooks. She can then email out invoices using quickbooks. We have troubleshooted this to the Nth degree, including calling Intuit support, running quickbooks file doctor, reinstalling quickbooks, reinstalling microsoft office, reloading the operating system on the computer, and using outlook to send emails instead of the built in email function on Quickbooks, but the issue still persists (even with using outlook as the mail client). We have tried having this user use a different quickbooks user account, but she still has issues.
When I have done remote support sessions with Intuit, the issue may happen once and then it seems to work for a while. Intuit support will then say "well it's working" and end the session, but the problem has been happening since December 2019.
The issue seems to resolve around 'qbmapi64.exe'. Here's some information from appcrashview:
?Version=1 EventType=APPCRASH EventTime=[removed]379599 ReportType=2 Consent=1 UploadTime=[removed]931891 ReportStatus=[removed] ReportIdentifier=b2019154-65b8-4b27-9b75-579fe0bb5ed6 IntegratorReportIdentifier=a2f7ba63-3451-4d34-b030-ee6cc6cd6f7f Wow64Host=34404 NsAppName=qbmapi64.exe OriginalFilename=QBMapi64.exe AppSessionGuid=[removed]-000f-ce67-295118b4d501 TargetAppId=W:0006af445c3b4345e3e3b66177a0a4cc[removed]!0000da18f77dd027c09f0a66bd1be62548439f45ae6e!qbmapi64.exe TargetAppVer=2017//04//20:08:29:43!21d03!qbmapi64.exe BootId=[removed] ServiceSplit=[removed] TargetAsId=27432 IsFatal=1 EtwNonCollectReason=1 Response.BucketId=3fa8c0dd251fdc541b298f5d95af2c9a Response.BucketTable=4 Response.LegacyBucketId=[removed]5207066 Response.type=4 Sig.Name=Application Name Sig.Value=qbmapi64.exe Sig.Name=Application Version Sig.Value=188.8.131.52 Sig.Name=Application Timestamp Sig.Value=58f87177 Sig.Name=Fault Module Name Sig.Value=mso20win32client.dll Sig.Name=Fault Module Version Sig.Value=0.0.0.0 Sig.Name=Fault Module Timestamp Sig.Value=5ddf2092 Sig.Name=Exception Code Sig.Value=c0000005 Sig.Name=Exception Offset Sig.Value=[removed]fa9a8 DynamicSig.Name=OS Version DynamicSig.Value=10.0.183184.108.40.206.256.48 DynamicSig.Name=Locale ID DynamicSig.Value=1033 DynamicSig.Name=Additional Information 1 DynamicSig.Value=aaa6 DynamicSig.Name=Additional Information 2 DynamicSig.Value=aaa66f[removed]2837d9a64bc4e DynamicSig.Name=Additional Information 3 DynamicSig.Value=adb6 DynamicSig.Name=Additional Information 4 DynamicSig.Value=adb6ece8e2c109c0a3e879301f312e40 UI=C:\Program Files (x86)\Intuit\QuickBooks Enterprise Solutions 19.0\qbmapi64.exe LoadedModule=C:\Program Files (x86)\Intuit\QuickBooks Enterprise Solutions 19.0\qbmapi64.exe LoadedModule=C:\Windows\SYSTEM32\ntdll.dll LoadedModule=C:\Windows\System32\KERNEL32.DLL LoadedModule=C:\Windows\System32\KERNELBASE.dll LoadedModule=C:\Windows\System32\USER32.dll LoadedModule=C:\Windows\System32\win32u.dll LoadedModule=C:\Windows\SYSTEM32\mfc140.dll LoadedModule=C:\Windows\System32\ADVAPI32.dll LoadedModule=C:\Windows\System32\GDI32.dll LoadedModule=C:\Windows\System32\gdi32full.dll LoadedModule=C:\Windows\System32\msvcrt.dll LoadedModule=C:\Windows\System32\sechost.dll LoadedModule=C:\Windows\System32\msvcp_win.dll LoadedModule=C:\Windows\System32\ucrtbase.dll LoadedModule=C:\Windows\System32\RPCRT4.dll LoadedModule=C:\Windows\System32\ole32.dll LoadedModule=C:\Windows\System32\combase.dll LoadedModule=C:\Windows\SYSTEM32\VCRUNTIME140.dll LoadedModule=C:\Windows\System32\bcryptPrimitives.dll LoadedModule=C:\Windows\SYSTEM32\MSVCP140.dll LoadedModule=C:\Windows\System32\OLEAUT32.dll LoadedModule=C:\Windows\System32\SHLWAPI.dll LoadedModule=C:\Windows\System32\IMM32.dll LoadedModule=C:\Windows\SYSTEM32\UxTheme.dll LoadedModule=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.18362.476_none_2a2a02a24667b734\Comctl32.dll LoadedModule=C:\Windows\System32\MSCTF.dll LoadedModule=C:\Windows\System32\kernel.appcore.dll LoadedModule=C:\Windows\System32\clbcatq.dll LoadedModule=C:\Windows\System32\bcrypt.dll LoadedModule=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.18362.476_none_e6c4b11b130f2595\Comctl32.dll LoadedModule=C:\Program Files\Microsoft Office\root\Office16\JitV.dll LoadedModule=C:\Program Files\Microsoft Office\root\Office16\AppvIsvSubsystems64.dll LoadedModule=C:\Windows\System32\SHELL32.dll LoadedModule=C:\Windows\System32\cfgmgr32.dll LoadedModule=C:\Program Files\Microsoft Office\root\Office16\c2r64.dll LoadedModule=C:\Windows\System32\shcore.dll LoadedModule=C:\Windows\System32\windows.storage.dll LoadedModule=C:\Windows\System32\profapi.dll LoadedModule=C:\Windows\System32\powrprof.dll LoadedModule=C:\Windows\System32\UMPDC.dll LoadedModule=C:\Windows\System32\cryptsp.dll LoadedModule=C:\Windows\SYSTEM32\USERENV.dll LoadedModule=C:\Program Files\Microsoft Office\Root\Office16\olmapi32.dll LoadedModule=C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.18362.476_none_17afa4006da19f63\gdiplus.dll LoadedModule=C:\Windows\SYSTEM32\WTSAPI32.dll LoadedModule=C:\Windows\SYSTEM32\wevtapi.dll LoadedModule=C:\Program Files\Common Files\Microsoft Shared\Office16\mso20win32client.dll LoadedModule=C:\Program Files\Common Files\Microsoft Shared\Office16\mso30win32client.dll LoadedModule=C:\Program Files\Common Files\Microsoft Shared\Office16\mso40uiwin32client.dll LoadedModule=C:\Windows\SYSTEM32\dwmapi.dll LoadedModule=C:\Program Files\Common Files\Microsoft Shared\Office16\mso50win32client.dll LoadedModule=C:\Program Files\Common Files\Microsoft Shared\Office16\mso98win32client.dll LoadedModule=C:\Program Files\Common Files\Microsoft Shared\Office16\mso.dll LoadedModule=C:\Windows\SYSTEM32\VERSION.dll LoadedModule=C:\Windows\SYSTEM32\msi.dll LoadedModule=C:\Windows\SYSTEM32\d2d1.dll LoadedModule=C:\Windows\SYSTEM32\WINSTA.dll LoadedModule=C:\Windows\SYSTEM32\dxgi.dll LoadedModule=C:\Windows\SYSTEM32\dxcore.dll LoadedModule=C:\Windows\SYSTEM32\Secur32.dll LoadedModule=C:\Windows\SYSTEM32\SSPICLI.DLL LoadedModule=C:\Windows\System32\Windows.Security.Authentication.Web.Core.dll LoadedModule=C:\Windows\SYSTEM32\wintypes.dll LoadedModule=C:\Windows\System32\netprofm.dll LoadedModule=C:\Windows\SYSTEM32\DWrite.dll LoadedModule=C:\Windows\SYSTEM32\davclnt.dll LoadedModule=C:\Windows\SYSTEM32\DAVHLPR.dll LoadedModule=C:\Windows\System32\npmproxy.dll LoadedModule=C:\Windows\SYSTEM32\d3d11.dll LoadedModule=C:\Windows\SYSTEM32\webservices.dll LoadedModule=C:\Windows\system32\wbem\wbemprox.dll LoadedModule=C:\Windows\System32\WS2_32.dll LoadedModule=C:\Windows\SYSTEM32\wbemcomn.dll LoadedModule=C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_38bfcb542ef4272e\igd10iumd64.dll LoadedModule=C:\Windows\SYSTEM32\ncrypt.dll LoadedModule=C:\Windows\SYSTEM32\NTASN1.dll LoadedModule=C:\Windows\System32\Normaliz.dll LoadedModule=C:\Windows\system32\wbem\wbemsvc.dll LoadedModule=C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_38bfcb542ef4272e\igdgmm64.dll LoadedModule=C:\Windows\SYSTEM32\urlmon.dll LoadedModule=C:\Windows\SYSTEM32\iertutil.dll LoadedModule=C:\Windows\SYSTEM32\CRYPTBASE.DLL LoadedModule=C:\Windows\SYSTEM32\WINHTTP.dll LoadedModule=C:\Windows\SYSTEM32\ntmarta.dll LoadedModule=C:\Windows\system32\wbem\fastprox.dll LoadedModule=C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_38bfcb542ef4272e\igc64.dll LoadedModule=C:\Windows\System32\OneCoreCommonProxyStub.dll LoadedModule=C:\Windows\SYSTEM32\WININET.dll LoadedModule=C:\Windows\SYSTEM32\IPHLPAPI.DLL LoadedModule=C:\Windows\System32\NSI.dll LoadedModule=C:\Windows\SYSTEM32\amsi.dll LoadedModule=C:\Program Files\Common Files\Microsoft Shared\Office16\riched20.dll LoadedModule=C:\Windows\SYSTEM32\dhcpcsvc6.DLL LoadedModule=C:\Windows\System32\vaultcli.dll LoadedModule=C:\Windows\system32\WRusr.dll LoadedModule=C:\Windows\System32\PSAPI.DLL LoadedModule=C:\Windows\SYSTEM32\MSIMG32.dll LoadedModule=C:\Windows\SYSTEM32\ondemandconnroutehelper.dll LoadedModule=C:\Windows\SYSTEM32\dhcpcsvc.DLL LoadedModule=C:\Windows\SYSTEM32\srpapi.dll LoadedModule=C:\Windows\System32\CRYPT32.dll LoadedModule=C:\Windows\System32\MSASN1.dll LoadedModule=C:\Windows\system32\mswsock.dll LoadedModule=C:\Windows\SYSTEM32\WINNSI.DLL LoadedModule=C:\Windows\system32\SFC.DLL LoadedModule=C:\Windows\SYSTEM32\sfc_os.DLL LoadedModule=C:\Windows\SYSTEM32\webio.dll LoadedModule=C:\Windows\SYSTEM32\usermgrcli.dll LoadedModule=C:\Windows\SYSTEM32\DNSAPI.dll LoadedModule=C:\Windows\System32\rasadhlp.dll LoadedModule=C:\Windows\System32\aadWamExtension.dll LoadedModule=C:\Windows\System32\fwpuclnt.dll LoadedModule=C:\Windows\system32\schannel.DLL LoadedModule=C:\Windows\SYSTEM32\mskeyprotect.dll LoadedModule=C:\Windows\system32\ncryptsslp.dll LoadedModule=C:\Windows\SYSTEM32\DPAPI.DLL LoadedModule=C:\Windows\System32\Windows.Web.dll State.Key=Transport.DoneStage1 State.Value=1 ProcessMetadata.Key=OfficeProcArch ProcessMetadata.Value=x64 ProcessMetadata.Key=InstallType ProcessMetadata.Value=2 ProcessMetadata.Key=DeviceClass ProcessMetadata.Key=Channel ProcessMetadata.Value=CC ProcessMetadata.Key=AudienceGroup ProcessMetadata.Value=Production OsInfo.Key=vermaj OsInfo.Value=10 OsInfo.Key=vermin OsInfo.Value=0 OsInfo.Key=verbld OsInfo.Value=18362 OsInfo.Key=ubr OsInfo.Value=476 OsInfo.Key=versp OsInfo.Value=0 OsInfo.Key=arch OsInfo.Value=9 OsInfo.Key=lcid OsInfo.Value=1033 OsInfo.Key=geoid OsInfo.Value=244 OsInfo.Key=sku OsInfo.Value=48 OsInfo.Key=domain OsInfo.Value=0 OsInfo.Key=prodsuite OsInfo.Value=256 OsInfo.Key=ntprodtype OsInfo.Value=1 OsInfo.Key=platid OsInfo.Value=10 OsInfo.Key=sr OsInfo.Value=0 OsInfo.Key=tmsi OsInfo.Value=39264 OsInfo.Key=osinsty OsInfo.Value=1 OsInfo.Key=iever OsInfo.Value=11.476.18362.0-11.0.160 OsInfo.Key=portos OsInfo.Value=0 OsInfo.Key=ram OsInfo.Value=8075 OsInfo.Key=svolsz OsInfo.Value=232 OsInfo.Key=wimbt OsInfo.Value=0 OsInfo.Key=blddt OsInfo.Value=190318 OsInfo.Key=bldtm OsInfo.Value=1202 OsInfo.Key=bldbrch OsInfo.Value=19h1_release OsInfo.Key=bldchk OsInfo.Value=0 OsInfo.Key=wpvermaj OsInfo.Value=0 OsInfo.Key=wpvermin OsInfo.Value=0 OsInfo.Key=wpbuildmaj OsInfo.Value=0 OsInfo.Key=wpbuildmin OsInfo.Value=0 OsInfo.Key=osver OsInfo.Value=10.0.18362.476.amd64fre.19h1_release.[removed] OsInfo.Key=buildflightid OsInfo.Key=edition OsInfo.Value=Professional OsInfo.Key=ring OsInfo.Value=Retail OsInfo.Key=expid OsInfo.Key=containerid OsInfo.Key=containertype OsInfo.Key=edu OsInfo.Value=0 FriendlyEventName=Stopped working ConsentKey=APPCRASH AppName=QuickBooks MAPI AppPath=C:\Program Files (x86)\Intuit\QuickBooks Enterprise Solutions 19.0\qbmapi64.exe NsPartner=windows NsGroup=windows8 ApplicationIdentity=1B2DE97F439620144FFDE4341FAD91DE MetadataHash=[removed] qbmapi64.exe Stopped working 12/16/2019 2:58:45 PM All Users 0xc0000005 Access Violation 0x000fa9a8 mso20win32client.dll 0.0.0.0 C:\Program Files (x86)\Intuit\QuickBooks Enterprise Solutions 19.0\qbmapi64.exe 21,960 C:\Users\All Users\Microsoft\Windows\WER\ReportArchive\AppCrash_qbmapi64.exe_966e6742ff338e705bf25c8513a64f759e42638_81bceb08_b2019154-65b8-4b27-9b75-579fe0bb5ed6\Report.wer
The customer and myself are at our wits ends in regards to this issue. The customer should not have to deal with quickbooks freezing each time they want to initially send out an invoice.
The other user who uses quickbooks on this same network doesn't have these issues. All the connections are hardwired as well.
Hi there, @RelevantNetworks.
Let me route you again to our support team to get this addressed right away.
Since your clients still having issues with sending emails from QuickBooks, I highly recommend contacting our Phone Support Team again. I understand that you've already contacted them before but they're the right support group to handle your escalated case. They can also create an investigation ticket if other users are experiencing the same.
To reach them:
In the meantime, you can let your clients send their transactions through Webmail. For more guidance, feel free to check out this article: Connect your email to QuickBooks Desktop.
Please touch base with me here for all of your QuickBooks needs, I'm always happy to help. Have a great day.
According to the Intuit support rep I spoke with, Quickbooks does not work well with click to run versions of Microsoft Office. The support rep stated that they do not support Office 365 and currently only support: Office 2010, Office 2013, Office 2016.
The affected individual has Quickbooks 2019 and Microsoft Office 365 (click to run). They continue to have the issue, even if we use gmail instead of yahoo.
Good afternoon, @machadojd.
Thank you for joining this thread. I'd be glad to lend a hand a provide some info about sending invoices from Outlook.
We can reset your Intuit ID settings within your company to refresh and here's how:
Once you've reset you're settings, let's set up your email account again.
Let me know if the step above did the trick. If you have any more questions or concerns, I'm only a few clicks away. Have a good rest of your day!
I have this same issue and get the same error message when I try to do the fix you just recommended in the Preferences tab under Edit. The frustration that this causes is immeasurable.
Have you tried changing the Internet Service Provider (ISP) and Port Information? If not, please follow these steps.
Once done, try sending an email again. If you're getting the same result or if you're done editing the port, please contact our Technical Support so we can investigate further.
Don't hesitate to reach out anytime if you have other questions. We're always here for you. Have a great day.
I have a user that is having issues with her Quickbooks crashing when trying to add/edit anything to do with setting up email preferences to send forms. Every time she gets an QBMAPI64:OUT OF MEMORY error.
As she has 32 GB of system ram, I do not think system ram is the issue. I believe this is some kind of corruption in quickbooks files that is throwing up a meaningless error.
I have done the following :
1. Rebuilt Windows 10 profile - no change
2. Removed/rebooted/deleted leftover INTUIT directories & reinstalled 2020 with all updates as of 4/27 - no change.
3. I was able to find RESET INTUIT ID SETTINGS as listed above (one has to search for INTUIT ID in order for it to show up in the HELP menu) and was able to reset the profile and then delete/re-create an email profile setting - however, trying to SEND FORMS still locks up Quickbooks - but looking at TASK MANAGER I see three items listed under the QB 32 bit application:
QuickBooks open with Company file
At this point
If I terminate the CefSharp.BrowserSubprocess then at least I get a menu of forms - stability was a bit
problematic and it crashed again.
This crashing happens using both OUTLOOK and WEB MAIL settings - same result.
I appreciate the effort you’ve done, @DaCheeze.
When you run or open a lot of programs at once, "Out Of Memory" error messages appeared due to desktop heap limitation. Closing some of the open windows before retrying the program may help.
But I would highly suggest contacting our Technical support team to fully investigate your concern. Reaching them can help modify your account and provide additional troubleshooting steps if necessary.
You can simply press F1 to route you to Contact us section, then choose to Get a callback to fix this immediately. You can refer to this screenshot for your visual reference:
You can find out what your computer needs to run the best QuickBooks Desktop experience through this link: System requirements for QuickBooks 2020 and Enterprise Solutions 20.0.
Get back to this thread if you have followed up question. I’ll make sure it will be taken care of.
FYI - I have OVER 30 years of SYSADMIN experience. I know how to troubleshoot a PC.
I have no other programs open during Quickbooks, I have rebooted the PC after crashing, I use a local sample file to open so I do not crash the production database, I disabled antivirus and shut down other applications. The client system is a CORE I7 running Windows 10 64 bit (latest build updates) with 32 GB of RAM and 2TB of available HDD space. Production database is running on a Windows server.
Please read what I have posted.
FYI - I have OVER 30 years of SYSADMIN experience - so I know a bit about PC troubleshooting.
The client system is a Windows 10 64 bit (latest build) running on a Core I7 with 32GB RAM and 2TB HDD with 90% space available. The system is always rebooted when troubleshooting (especially after QB crashes) and I have disabled AV software and any other open systray apps. NO APPLICATIONS are running when I troubleshoot this product.
Does support offer a removal tool that allows me to totally delete the software from a client's pc?
beyond what is stated by your support here...
Reinstall still picked up registration information and mapi configuration automatically, which tells me the above process does not fully clean out a previous install - either something still exists in the registry and/or a common folder somewhere.
Does a removal tool exist ? Where may I find it ?
Thanks for coming back, @DaCheeze. I appreciate you for trying all the steps to fix the crashing issue.
At the moment, QuickBooks isn't supporting the removal tool that allows you to delete the software from a client's pc. I know how this functionality is useful for you. I'll do my part to send this idea to our Product Development team for them to consider in the future.
Meanwhile, I'd suggest you contact our Customer Care team to check why the program always crashing even after you rebooted your PC. They have additional tools that can help you verify and to fix the issue.
To make sure you'll get the help that you need, check out our available hours of operation through this article before reaching us: Support hours and types.
Feel free to visit again if you have additional questions. I'm always delighted to help you some more.
We've had the same problem with emailing Invoices/Sales Orders for over a year now. We've been troubleshooting and trying just about everything. We too are running Office 365 click-to-run. I'm going to find a copy of Office 2016 and give it a try. If that works, I'll report back.
I've made at least 8 calls to tech support for over the last year and have begged to speak with someone on the Dev team to get this fixed. It's unfortunate that no one has contact info for the Dev team. There are a lot of IT consultants/Techs that could help improve this product if they had someone that knew what the software is doing on a technical level. This issues could be fixed quickly with the right people involved. If there is a known problem with Office 365, then let's get this info to the Dev team right now, and get this fixed please!
Customer care is non existent . It is someone that has no real knowledge of the product and in the end blames your computer. There is no ability to escalate. Office 365 has been in the mainstream for over 5 years and I cant even think of a client that is running a stand alone version of Office on the client box anymore. My client box is an i7 with 16GB RAM and no updates to Win 10 Pro in the past week or so and as of today showing an out of memory while trying to save an invoice or email an already created one.
Thanks for joining this thread, YB1.
You'll want to try the recommended troubleshooting steps from the above replies. If nothing works, I would suggest reaching out to our Customer Care Support Team. They have the necessary tools to do a screen-share with you and can further assist you with your concern.
Here's how to contact them:
Check out our support hours and contact us at a time convenient to you.
Please let me know if you have any other concerns. I'm always here to help.
Just following up here to my earlier post. I have since installed Office 2016 on 3 workstations and those users have successfully emailed Sales Orders, Invoices, & Sales Receipts and not one user reported the issue in 3 days now.
Please, instead of pushing us to your support team, can someone take some time and find a way to get the contact info for the Dev team and get this issue to them. As a user posted above, Office 365 is Microsoft's primary office version now and it's not going away. This needs to be addressed.
We here have identified the bug, shown that it's reproducible, and have now proved that it's tied to the integration between QB and Office 365 (I'm assuming via the QBMAPI64.exe application). We are trying to help you and other QB users. All we're asking is someone from QB help out and get this to the Dev team so they can get this fixed. So we all can go on using QB and O365 with no issues.
I will gladly work with the QB Dev team on this. Just give me a call.
I really appreciate the information you’ve shared with the Community page.
Contacting our QuickBooks Support team can help the user to raise their concern and let us know the things that need to be improved in the future.
Creating an investigation also provides ideas to the developers to work and build the best option that works best for your business.
I’ll take note of your feedback and rest assured to pass this to our product developers. I recommend visiting our Blog site. This is where we share recent happenings and future developments, such as updates to newly added features.
Thanks again for raising this to us. And let me know if there’s anything else you need. I’ll be here. Always take care.
Thanks for joining the thread, @eddiewillis1.
Allow me to provide some more information about the emailing issues you're having.
QuickBooks Desktop supports Microsoft Office 360 only if it's locally installed on your computer, which means it's not downloaded from the web. This is listed in the system requirements that you can check before downloading the program. However, if you're having the same issues as described above, I suggest uninstalling QuickBooks and Office 365 and reinstalling them. When reinstalling, you'll want to start with Office 360 then install Desktop to ensure the connection will work with QuickBooks.
Please let me know if this gets you back to business. I'll keep an eye out for your response.
It's Office 365, not Office 360.
The requirements actually state, "Note: Office 365 is only supported when it is locally installed, not the web version." Your statement that, "...which means it's not downloaded from the web." is misleading since the locally installed version may very well be downloaded from the web. Not sure if you misspoke or simply don't understand the difference.
Installing them in a particular order sounds like magical thinking/grasping for straws to me.
I recently upgraded to QB 2020 and I am on Office 365 but I am emailing via Gmail. I get the error 'qbmapi64 - Out of Memory' and then it kicks me out of QB. I've restarted the program and restarted my computer. Which of the above suggested fixes worked for anyone? I really need to get my invoices out - hoping someone has advice. Thank You!!!
I appreciate you for performing some troubleshooting to get this sorted out, JKennedy12.
Aside from restarting the program, let's register your email provider in the Web Mail settings.
Then, try sending you invoices again.
For more details about Microsoft Office 365, check out this article: Microsoft Office 2010, 2013, 2016, and 365 FAQ.
If the same thing happens, let's try uninstalling and reinstalling Microsoft Office 365 to fix any damaged data issues. I'd suggest contacting the Microsoft Office's support to assist you with this one.
Then, repair your QuickBooks Desktop to fix damaged components in the software.
If the problem persists, please reach out to our Technical Support Team. They'll pull up your account in a secure environment and investigate what's causing this issue.
I've got a link here where you can find articles about managing your invoices: https://quickbooks.intuit.com/learn-support/en-us/sales-and-customers/invoices/08?product=QuickBooks....
Keep me posted if you need a hand with creating memorized transactions or any QuickBooks elated. I'll be here to help. Have a great day ahead.
Fortunately - just going in and checking my email address set up as they described worked - I don't know why. I could not 'add' my email as it was already in there. I didn't even delete it and re-add it. I'm not complaining - it worked and I got my invoices out!! :)