An implementation of Visual Basic that is built into Microsoft products.
Open the VBA editor and remove or fix any faulty macros, then update or delete broken queries/connections under Data → Queries & Connections. Save and test the workbook again.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
.xlsm (macro-enabled workbook), corrupted macros or external connections might be contributing to the issue.An implementation of Visual Basic that is built into Microsoft products.
Open the VBA editor and remove or fix any faulty macros, then update or delete broken queries/connections under Data → Queries & Connections. Save and test the workbook again.
Thanks for reporting the issue. Since the file is macro-enabled, it may be affected by corrupted VBA code or broken external connections.
Please try the following:
Steps to Diagnose and Fix the Issue
Go to Developer → Visual Basic.
Check for any broken or outdated VBA code.
If the workbook uses Excel Interop, ensure all COM objects are properly released. Lingering objects can cause exceptions when calling Excel.Quit().
Let me know if the issue persists after following these steps. I’ll be happy to assist further if needed. If the issue has been resolved, kindly mark the response as answered