Home Server
New Blog Posts: Merging Reports - Part 1 and Part 2

Stream Read Error

edited October 2004 in Server
Most of our reports are finished, we had to develop over 100 reports
and this took some time.
But, now that we start to use them in a live environment again we run
in some serious problems with the Rb Server. In previous attemps we
always had problems with the known issue of TeeChart. In this setup,
i took al TeeCharts out of the reports. The server is called by a
program that run the same report more than 100 times, each run with a
different set of autosearch values (we are building our historical
reports).
This run often makes the server crash with this ESocketError (I'm
running for testing, more like debugging the server on my development
machine). This results in this ESocketError after some reports.
Any suggestion on how to solve/find more in detail this problem.

Harry Leboeuf
D7.0, RB 7.04, TeeChart 7.01Beta, ADO To SqlServer2000

Comments

  • edited October 2004
    If any use, this is the call Stack

    TStream.ReadBuffer((no value),4096)
    TppPublisher.ReceivePage(???)
    TppEngine.GeneratePage(???,???)
    TppPublisher.DoOnPageRequest
    TppPublisher.Publish
    TppProducer.PublishReport
    TppProducer.PrintToDevices
    TppReport.PrintToDevices
    ThreadProc($CCB8A8)
    ThreadWrapper($CB21D0)
  • edited October 2004
    I'm leaving the office for today, but i added this line at the end of
    a single run
    rsClientReport.ClearSession;
    Until now, the 'runner' has been runnign over 250 reports, beofre it
    stopped postly between 40 & 50.
    I'll let yoy know tomorrow if it works fine now !
  • edited October 2004

    Ok, post again here later. This is not an issue that anyone else has
    reported. We are going to need a way to recreate the issue here.

    --
    Nard Moseley
    Digital Metaphors Corporation
    www.digital-metaphors.com



    Best regards,

    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com
  • edited October 2004
    The problem seems to be solved (in test-environment).
    I'll put it live today.
This discussion has been closed.