Home Server

ReportBuilder Services

edited October 2002 in Server
When I start the RBAdmin app and click start, the RBServices app and the
RBSampleServer immediately startup. So far, so good. I then kill the
RBSampleServer app using Task Manager. The ReadMe.doc file in
"RBServer\Windows Service" states that "In the event of a crash, your
report server application will automatically be restarted by the
service." However, the RBSampleServer app doesn't restart - I've waited
up to 30 minutes. The RBAdmin app still says "The ReportBuilder Server
is currently Running".

Any ideas on what's going on here?

Thanks,

Ed Vander Hoek

Comments

  • edited October 2002

    This only works within the context of a server crash.

    ---------------------------------------------------------------
    Article: Testing the ReportBuilder Services Auto-restart feature
    ----------------------------------------------------------------

    If the report server application encounters an unhandled exception then it
    does the following:

    1. Writes the error to the log.
    2. Notifies RB Services that it has encountered a fatal exception.
    3. Halts execution.
    4. RB Services then starts a new report server application process.

    If you want to test this, try adding some event-handler code to one of your
    reports. In the Report.BeforePrint event add code to crash the server:

    raise Exception.Create('Dummy Exception: Testing RB Services auto-restart');

    You can test the above with the RBServer\Demos\Servers\Main project.

    1. Open the project, compile and run. This will automatically register the
    application with RB Services.
    2. Close the application
    3. Modify one of the form based reports as described above. For my test I
    modified dm0001.pas.
    4. Compile the project.
    5. Use RB Services to run the report server application as a service.
    6. Use Task Manager to find the RBServer.exe process
    7. Run the demo client report explorer application and use it to access the
    server.
    8. Select and run the report containing the event-handler that raises the
    exception.
    9. Use the Task Manager to watch the RBServer.exe process terminate and then
    restart.
    10. Select any of the other reports and they should run correctly.




    --
    Nard Moseley
    Digital Metaphors
    http://www.digital-metaphors.com

    Best regards,

    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com
This discussion has been closed.