Quote Originally Posted by stanl View Post
What is failing: can receive an unknown COM error in previous scripts (compiled Winbatch or Powershell) that automate Excel. Occurs when Powerpivot and Data Mining add-ins are installed and active which takes Excel more time to fully load.

Again, not a Powerpivot issue but more a timing issue starting Excel and setting properties. Issue was resolved by use of the .ready property, so the post was more an FYI.
In the new office there was this COM add-in which I didn't need but was installed as default. It would take Excel ages to start. Disabling improved start up time considerably.
Quote Originally Posted by Zack
What is failing exactly? I'm assuming this is a VBS file of sorts? And if so, why would a company/system/admin not allow macros in a workbook but allow a script file to run?? I would certainly think it would be the other way around.
It could be that the file is not at a trusted location [network drive] and macro security is "disable with notification".