By using this website, you agree to our Terms of Use (click here)
In order to allow me to focus on Consulting (click here) and Courses (click here), I continue to review all posts here in the Forums, but, in general, I'm only personally responding to posts that I mark as #AcumaticaTnT (click here). For Questions (click here), others may respond, or you can post over at Community.Acumatica.com (click here).
Sincerely,
Tim Rodman
I got an email from someone with a Velixo Reports Excel file attached.
When I try to open the Excel file and click Acumatica -> Refresh All, I get the following error message:
No workbook open.
Does anyone know why this happens?
Hey Fozzie,
When you open Excel files from an email or download one from the internet, Excel goes into protected mode which you can see in the yellow bar on the top of your screenshot. When this happens, some Excel Add-Ins like Velixo Reports get blocked by Excel.
First, you need to save the Excel file to your computer. I'll explain why later.
Then, click the Enable Editing button on the yellow bar:
But here's where it gets weird. You're going to get a bizarre error message:
Unhandled exception has occurred in a component in your application. If you click Continue, the application will ignore this error and attempt to continue.
Exception from HRESULTS: 0x800A03EC.
Then you click Continue like in the screenshot above, but you get get caught in an infinite loop.
So make sure you close Excel after clicking Continue to get out of the infinite loop, then re-open the file. This is why it's important to save the Excel file to your computer so Excel will remember that you marked Enable Editing on the file. If you re-open the file from email, it will get protected again, and you go through the same thing.
After you re-open the Excel file from your computer, it should open in unprotected mode and it should work.
Thanks @timrodman, that worked.
Kind of weird that you have to save the file to your computer every time, but it makes sense why that error happens.
Thanks Tim. This is a known issue and my plan is to improve error handling to show a proper error message to the user and avoid the infinite loop.