Skip to Content
avatar image
Former Member

Crystal reports 13.0.17 IIS Application Pool Crash


I am wondering if anyone has any insight into what the below Crystal code is doing at the time of this crash. Not looking for a solution - just an idea of where to look

It appears the exception is coming from crdb_ado!DbFreeErrorInfo

Full details below

Thread 299 - System ID 13252

Entry point msvcr80!endthreadex+80Create time 24/03/2017 10:04:57 p.m.Time spent in user mode 0 Days 00:00:00.124Time spent in kernel mode 0 Days 00:00:00.062

This thread is making a database operation using ADO.

The call to MSADO15!CSTDPROPSETPROPERTIES2::GET_ITEM originated from crdb_ado!DbFreeErrorInfo+19d84

Call Stack


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Mar 28, 2017 at 01:17 PM

    Hi Adam,

    The error suggests possibly too many connections open. This can happen if you are not closing and disposing of the report objects when done with them.

    Could also be IIS has too much memory fragmentation, CR requires contiguous memory space. Windows is not capable of defragging memory on the fly like UNIX OS can. Try cycling IIS when the error happens and try again.

    Or your ADO Dataset is too large, you need to limit the DS to about 5K rows and not many columns, if you go higher it can cause a memory problem. Exact numbers is not available because it all depends on what is available. MS does not allow access directly to the Dataset so CR has to make a copy of it which doubles the memory usage and then if you have tables that can group to be huge....

    Do you know the conditions when the error happens?


    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Mar 29, 2017 at 08:11 PM

    Hi Don,

    Firstly thank you for getting back to me so quickly. We are going to follow up your points. We know we have report disposal issues back in this version of our product and have made subsequent changes in our code an try to actively dispose of unused report objects rather than relying on the garbage collector. In this case we can see 200+ report objects waiting for collection

    Based on this and your thoughts above we are going to recommend our client move to our latest code base to see if the issue resolves.

    Thanks for your time on this, and all the other articles that have been of assistance on this site.


    Add comment
    10|10000 characters needed characters exceeded