Interface Exception Error gridapp.ccp:1828

Problem Statement

Excel interface exception error gridapp.ccp:1828 SCODE = 0X80010001 is issued when a user attempts to close an nVision instance, drilldown, or other Excel workbook

Root Cause

Excel Interface Exception Errors are unfortunately a part of life with nVision. The messages given with them are often cryptic and no help at all in identifying the cause. 

After extensive testing I have identified that this error occurs under the following circumstances (I have reported this issue to Oracle Support SR #3-5976739951):

• The user has a large number of Excel files open (typically around 30+ files)
• The user attempts to close an Excel file from the file stack in the Excel Taskbar group, and importantly, the file they attempt to close has unsaved changes. The error occurs whether the user uses the X available in Excel 2010, or by right-clicking and selecting close in either Excel 2010 or Excel 2007. The error is issued with the Save dialog.

Note: The issue occurs frequently for our user community because many layouts select actuals and translate ledger data side by side and then sum them to the right. The ledger data columns are hidden using Excel grouping. To perform drilldowns on the ledger data, the users have to expand the grouping which places the instance into a "changed state" that Excel will issue a save dialog for when the user comes to close it.
 
We are running on Tools 8.52.06. I have replicated this error on both Windows 7 with Excel 2010, and Windows XP with Excel 2007. I have also been able to replicate the error in Tools 8.52.06 DMO. I have an SR open with Oracle on this issue which appears to be some kind of bug. 


Different error messages are issued once the user interacts with the Save dialog box. 


If the user clicks Yes to save the file, they are presented with a suggested file name of :.xlsx. This is an illegal name for Windows. Saving the file with an appropriate name results in errors that refer to Excel 4.0 Functions and Excel 4.0 Macros.

Excel 4.0 Function / Excel 4.0 Macro cannot be saved in a macro-free workbook

At this point the user finds themselves in a loop with a macro error being issued no matter what action they take. The best way to escape is to use Task Manager to close nVision and Excel.


Clicking No to the save dialog issues an error "Cannot run the macro 'NvdOnWindow'". The user is once again locked in a loop.

Workaround

We are currently testing the following workaround

• Do not close files from the Excel group stack in the Taskbar. Rather, select the file you wish to close from the stack, and with that file active, close it from the workbook itself.