A family of Microsoft spreadsheet software with tools for analyzing, charting, and communicating data.
The error has now been fixed in version 2.27.
But it would be nice if someone would give their opinion on the cause.
Our guess is that Excel is called to do some work. The work completed and the call to the Excel object model returns. But there is some side-effect in Excel which causes additional work, after the call returns.
On a slow computer or with a large pivot table or maybe with VBA event handlers getting called, the side-effect work occupies Excel. Then a subsequent call to Excel is made. Excel is busy and so throws an exception.
For the fixed version go to: