OLE Error: Call was rejected by callee RRS feed

  • Question

  • User is experiencing this error:  'OLE Error:  Call was rejected by callee' when trying to export a large report to Excel.


    He is using Proclarity Web Professional  Our Proclarity databases are SQL2000.


    What can be causing this error?


    Wednesday, December 3, 2008 5:29 PM

All replies

  • In past cases we’ve seen the OLE errors when exporting large datasets from ProClarity to Excel. 37,000 to 50,000 rows is usually the point that errors start appears. This is due to the fact that this portion of the program was not designed for exports larger than this. Often times we recommend to customers who want to use ProClarity to export large data sets to ignore the errors and wait until the export completes.


    Also, ProClarity is an analytics tool and not designed for large reporting tasks such as this. SSRS, however, is for reporting so creating a report in SSRS and even adding a cube action for that report so it appears in ProClarity would probably be a more efficient approach to reaching a reasonable exporting system.

    ProClarity 6.3.2210 builds and later have support for Excel 2007 export row and column limitations.  Testing documents show that we support the export of >65k rows and >256 columns with this software.  However, there may still be a performance issue due to the reporting nature of this type of query.

    Wednesday, December 3, 2008 11:00 PM
  • Does the export continue even with the popup error message box on the screen?  If they click OK on the message box, does the export still continue?

    Thursday, December 4, 2008 3:12 PM
  • Hi Liz,


    In my experience yes the export usually continues after an OLE error appears.  I've seen exports of up to 700,000 rows taking place over 5 hrs.  The main point is anything past 50,000 rows is probably best for reporting software like SSRS.  For the specific error of "Call was rejected by callee" - check to make sure there isn't an active cell in Excel at the time of export.  If there is an active cell that error will appear and the export will stop.  The only workaround is to make sure there isn't an active cell at the time of export.





    Tuesday, December 9, 2008 6:17 PM
  • Sean,

    Not sure what you mean by an active cell? I have users experiencing the same issue as above and the export does not continue or returns a blank sheet.



    Wednesday, July 29, 2009 3:08 PM
  • An active cell would be a data cell where the cursor is blinking (as when typing text).  Are there any other error messages like "cannot find file *.xls" that the end users are seeing?
    Microsoft ProClarity | This posting is provided "AS IS" with no warranties, and confers no rights.
    Tuesday, August 4, 2009 1:47 PM