I have just downloaded and unzipped and followed the "change your IDs" part of the add-in steps here https://github.com/OfficeDev/Excel-Add-in-ASPNET-QuickBooks
When I try to load it by pressing F5 (Start Debug), Excel does start, and it looks like it's trying to load in a pane on the right (not a button on the ribbon like I'm expecting?), but it says Loading... for a while and then a red-X pops for a second too fast that I can see/click, but then it goes back to Loading... and my HDD is thrashing..
There are no errors that I can see, but I would like to know what that red-X is, and ultimately have the button show on the ribbon.
I don't have to do an "install" per-se, do I? I think that side pane is doing the install, but failing, and I can't find a log anywhere..
Turns out I needed an Excel update..
I had ProcMon running and tried to analyze minidumps and tried everything else that I could think of..
Still a touch of wonkiness (like having to copy my 32-bit .exe as the 64) but it at least loads in Excel now.
Related
Not sure if this is the correct place to post this but this issue is driving me insane....
The Issue:
I have come to use my PC after the weekend and for some reason the layout of the VBA Project stuff is completely messed up...
Usually when my VBA is set up very nicely in what I believe is the standard viewing mode IE the Project box to the left and the code to right and the intermediate window at the bottom...
For some reason now I get the following:
As you can see it is just the code...
I then click on the project explorer window and the project details appear, but as one ridiculously large page....
Then I minimise the window and alter its shape to try and get it at least look like it used to...
I can live with this to an extent although everything is floating and annoying... But now, every time I click onto a module (to view the code). It opens each module as its own seperate window!
This as you can imagine is unsustainable when working with as lot of code and having to flick between different modules
What I have Tried:
I have tried looking in different settings and I can not see anything different...
I have restarted my PC and it is still the same...
I have tired opening a different spreadsheet and still the same....
Does anyone have any suggestions? I just want it to be back to the simple layout of everything joined together etc...
I have an Excel add-in in AppSource. It has a bug: sometimes, when the add-in is launched via its button on Ribbon for the first time, the first page cannot be well loaded (thus there is just a blanc taskpane). Clicking on the button once again loads well the add-in.
I want to see how files are loaded while the add-in is being launched for the first time, and follow this method to debug:
Then, open the Office application and sideload your add-in.
Right-click the add-in and you should see an Inspect Element option in
the context menu. Select that option and it will pop the Inspector,
where you can set breakpoints and debug your add-in.
The problem of this approach is that we can only trigger the "Inspect Element" when the loading has finished. Then in the Network tab, we see all the files have already been loaded with no further information (e.g., time, size). This approach does not allow me to inspect the loading from the beginning:
Does anyone have a better way or better tool?
Have you tried typing window.location.reload() in the Console and pressing enter? At least on Windows, I have found this to be a very useful debugging technique for diagnosing issues that happen during the taskpane launch -- and it feels like it should force the JS files to be reloaded as well, for the scenario you're looking for.
Excel crashes when opening files that contain a userform
This is a known problem with a known solution workaround which is to delete a file called Excel.box from here:
C:\Users\SlowLearner\Application Data\Microsoft\Forms\Excel.box
According to this forum post the purpose of the Excel.box (& Word.box) file is:
Files such as Winword.box and Excel.box are associated with the
Control Toolbox you see when you are designing a UserForm in the
Visual Basic editor. The files contain information about the layout of
the Control Toolbox (additional tab pages, controls that have been
added or removed, custom icons, ...) If a user has never modified the
Control Toolbox in any way, there will probably be no .box file. By
deleting a .box file, you will restore the Control Toolbox to its
default (factory preset) configuration - this is the only way to do
that. Sometimes, the .box file becomes corrupted and must be deleted.
There are no negative side effects to deleting it.
Unfortunately Excel.box returns :(
It would seem that for most users the problem is fixed by deleting the file, sadly not for me.
I'd like to understand what is causing this problem to recur. A few points to note:
this (touch wood) is not impacting MS Word on my PC
I am using Office 2010, 64 bit version on Win10
I have not made any conscious change to form settings
if I delete the file > start Excel > UN-DELETE the file: everything works :-/
some other experiences with this issue here
For the time being I'll just check for and delete the file before launching Excel, but this is hardly an acceptable solution for the long term. Appreciate thoughts for a proper fix... TIA
Additional Information:
I have not fully explored the crash but so far it happens when:
starting the application by opening an xl?.m file with a userform
application does not get past the splash screen
crashes with the application's CRASH screen (... encounted an error...)
starting the application with a blank worksheet then adding a userform
crashes immediately with the applications CRASH screen displayed (see below)
The above crash happened after rebooting my PC, had a chance to explore it some more.
First I opened the file I had been working on (contains userforms):
annoyingly it opened without crashing
I did NOT enter the IDE
I closed the file (Excel closed normally)
Then I created a new worksheet
I opened the VBA IDE
right-click 'add UserForm' - Excel crashed immediately
(I aborted the recovery / search for a solution attempt)
Then I re-opened the file I had been working on
opened the VBA IDE (the project is PW protected)
the very instant that I entered the PW and hit enter Excel crashed
crash was same both times...
Safe Mode:
Crash still happens in safe mode - steps to reproduce:
Run: Excel /safe
Open VBA IDE
r-click add userform
crashes immediately
Creation of the EXCEL.box file
Based on visually observing the folder which had the Excel.box file I did some tests to try and see when it was created. Basically it seems to appear when one of the following happens:
- the UserForm tools box is closed
- the IDE is closed (after showing the userform)
I've also now tried to modify the userform toolbox by removing everything from it. Excel is still crashing after every restart of the application (which is odd as I was not able to crash it like that earlier).
Office Repair - not tested (yet)
Reluctant to try Office Repair as based on the following quote from here (scroll down: pg 1 reply 8 by Steve IT) I'm not expecting it to work :-/ (but will try if no other suggestions surface).
Thanks for the continued suggestions, however I have tried a repair and also removed Visual Studio 2013 and Office altogether (just in case VS was interfering) and reinstalled both, but it still throws the errors reported previously.
Other user profiles
Created a brand new user called 'test'. Test has the exact same problem.
This problem eventually resolved itself, not sure why. I continued to use Excel normally and it continued to crash so I would delete the offending .box file and start over...
As of Nov 2017 Excel no longer crashes with respect to this issue; my best guess is there was an automatic update that resolved the issue.
Looks like this issue still occurs and it is not just limited to Excel but also Powerpoint.
The fix as mentioned above works where you move / delete any files in the below folder location resolves the issue.
C:\Users\%username%\Application Data\Microsoft\Forms
It is highly likely that this error is caused by bad code in a macro or an Add-In that uses forms. The problem is replicating this can be difficult so you have to debug this in some way when it does crash out.
POWERPNT.box
EXCEL.box
are some of the files that get generated, where Excel or Powerpoint crash on the splash screen.
Try adding the command
ThisWorkbook.VBProject.VBComponents("UserForm").Activate
just before your
"UserForm".Show line.
I have the following problem in Excel:
I wasdevelopping a template in Excel VBA. I was tearing a sub routine in break mode and tried to stop it to change the code. When I pressed the stop button, however, Excel froze so I had to kill the process. Although before the crash everything was ok, opening the file would cause excel to freeze and crash again. Obviously the file got corrupt. I used a previous version of the file and decided to redo the changes. At some point the problem happened again. When I finally managed to open the file, everything seemed ok, but pressing the "developer tools" button on the ribbon crashes excel. I desperate. The Template is 90% but making even the slightest change feels like disarming a mine bomb that can blow the template up.
Does anyone know how to bypass the problem?
Here is what I would suggest:
get another PC with the same version of Excel installed,
Install the VBA CodeClener Add-in (http://www.appspro.com/Utilities/CodeCleaner.htm),
Copy your (prior) spreadsheet over to that PC, open it, open developer tools and run CodeCleaner.
Add your changes.
If that works, then reinstall Excel on your first PC. If not then you will have to take drastic measures:
Open the prior version,
Make one (or a few) change at a time,
After each small set of changes, save a new version of your Excel file, adding a version number to the file name (update the version/file name each time)
If it fails again, go back to the previous version, and the try to figure out which of the small set of changes may have corrupted the file.
I am having a strange Excel 2007 issue, and I am not quite sure how to explain this. So bear with me please....
I have created a few right click buttons to call various backend VBA functions that I have written. They were working fine earlier today, and now for some reason, a button is appearing that is not from the code in my worksheet. When you click it, it is attempting to open another worksheet and execute code from it. The two files are not in the same directory nor are they named anything similar. I deleted the file that the button is trying to execute from and now it just simply gives me an error 400.
So, I couldn’t figure that out, and have since deleted every single scrap of code in the backend of this file, and the button still appears. Any ideas what could be causing this? It seems like maybe its mixing files up or saving a copy somewhere in a temp directory and trying to access that instead of the actual code that is written in the VBA. Is there a cache I need to clear out or something?
I know I didn’t exactly do a great job describing this, so I will be more than happy to provide any and all other details that you may need. Just let me know what is going on.
EDIT #1 -- New Information ==
I can even open a new, completely blank excel file and the right click button is still there.
EDIT #2 -- Tried Diagnostics ==
I just tried running the Excel diagnostics and it found no problems. It is strange, it is like this macro has somehow became global or stored in some type of cache or something.
I hope I'm understanding your issue correctly.
If you know what right-click (context) menus the button is appearing in you should be able to fix them with a Reset command. For example if it's appearing in the Cell context menu, you could try this in the VBE's Immediate window:
Application.Commandbars("Cell").Reset
This will reset the entire menu to its default state.
Also, you might be interested in a tool I wrote, MenuRighter, that allows you to tweak your right-click menus. It also has a setting to show you the Caption and ID of any context menu.