Error 500: Error in processing report [Extended info: CP internal=100]

Posted by: oakshan on 4 August 2017, 3:24 pm EST

  • Posted 4 August 2017, 3:24 pm EST

    Hi,

    I'm looking at a really old report which I believe was done with ActiveReports 2.0. The weird thing happening is that the report seems to work the majority of the time but can sometimes generate this error by incrementing the date range. Looking closer at the data, nothing really jumps out as being the cause for the issue.

    I've google searched this error and did come up with these two forum links http://arhelp.grapecity.com/groups/topic/error-5000-9/ and http://arhelp.grapecity.com/groups/topic/error-message-cp-internal-100-when-running-a-report-with-a-subreport/.

    The first link suggests that this error normally means "normally indicates something has gone wrong with the data or data connection. Check the permissions to the data, the connection to the data and make sure there’s data returned for the report." In addition to that, both posts reference another link http://www.datadynamics.com/ShowPost.aspx?PostID=240 or http://arhelp.grapecity.com/ShowPost.aspx?PostID=240. In both cases, neither page actually exists.

    Anyway, it would be great to get some more guidance on just what is going on for this error.
  • Replied 4 August 2017, 3:24 pm EST

    Hi,

    Error 5000 CP Internal 100 is a generic error message, so there may be a number of different causes for this error.
    Some of the common causes are as follows:

    If the project is trying to dynamically add controls once the project has passed the ActiveReport_ReportStart Sub.
    If the project is using multiple group headers and all but the first one has the visible property set to false.
    If the project references physical controls from FetchData.
    If the project is an unbound report and does not use DataInitialize and FetchData events.

    Solution:
    First, make sure the project is not performing any of the above procedures. If the project is not, then add app.LogEvent at the beginning and end of every sub. By doing this, a log file will be generated when the project is compiled and ran. The log file will show every sub started and ever sub finished. Once the error fires, the Application Log in the Event Viewer will indicate which sub was the last to start and did not finish. From there, it will be possible to narrow down the code to find the line causing the problem.
    For more help on the app.logevent method please refer to the following MSDN link:
    https://msdn.microsoft.com/en-us/library/aa244132%28v=vs.60%29.aspx

    Regards
    Ruchir Agarwal
  • Replied 4 August 2017, 3:24 pm EST

    One thing I've just noticed is that the report seems to break when there are exactly 17 rows of data coming back. I verified this by changing the date range for the report.

    So, the report works when it's less or greater than 17 rows but not when it's exactly 17.

    Have you heard of a situation similar to this before?
  • Replied 4 August 2017, 3:24 pm EST

    Hello,

    It looks a very typical issue and seems unlikely that we would be replicate the issue. However, to know what might cause this I am discussing the same with the Development team and will get back to you if we need any further information from you.

    Regards
    Ruchir Agarwal
  • Replied 4 August 2017, 3:24 pm EST

    Hello,

    For investigating more about this issue, we would need your application, even a sample reproducing the issue would be enough.
    Therefore, we request you to please share the same.
    And if you cannot share your application at this public forum, you may send it to our support E-Mail address: activereports.support@grapecity.com.

    Regards
    Ruchir Agarwal
Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels