Background: Analysis for Office by SAP Business Objects was recently deployed to several hundred users in my environment as a virtual app using Microsoft App-V. The add-in does not get installed directly into Excel - it must be loaded using a Business Objects loader, which opens up an instance of Excel with the add-in.
After deployment of the software, many of the users suddenly started reporting that Excel takes 3-5 minutes to load any documents, even without the add-in, and takes the same amount of time to load a blank Excel document. SAP support suggests deleting Excel14.xlb as a fix for this issue, and I've verified that this works.
I currently am unable to replicate the issue at all, because the installation of the virtual add-in does not create or modify the Excel14.xlb file. I do notice that it creates its own XLB file in its AppV cache, but no action is needed with that one to resolve the issue. This issue only is affecting users that have installed this update.
I'm currently trying to find a more elegant and permanent fix for this issue, but am running into a lot of dead ends. Can anybody advise on why deleting Excel14.xlb seems to resolve an issue with a program that doesn't seem to meaningfully interact with it?
Thank you!