Server is a Closed Box

rbuser

Hello,

We are running now quite some reports on a server. Very satisfied as
we always have been for the reports. But, the only remark i'm making
myself now is that the Server is a closed box. From time to time we
have a very heavy report (complicated & quite slow queries) that runs.

It happens that our server is stucking on that report, the client
finally gets a connection-time out, and ..... the report server hangs.

Although the 'Application' (we don't run as a service) is still
running, we can't see what is happening with the server, nor we can
see who is connected or what reports where running, started from what
machines....
I love the products but at such moments i could wish it to go to hell.

I hope there is a way to find out more what is happening at that
moment and that this problem is only due to my lack of knowledge on
the product.
It would be nice to be able to question the server for some of these
questions, and maybe even kill that 1 running report/thread.

Just some thoughts, but open for approvement.

nardmoseley

Thanks for the feedback. You are correct, there is currently no way to
internactively monitor server or webtier activity.

There is a Server log file and there is a WebTier log file. In the case of
the webtier there is a LogSettings.Verbose boolean. The Server and WebTier
are only aware of request that are made and responses that are sent.

The ReportVolume.PublishingOptions can be used to limit the amount of time
and the number of pages that a report can produce. This can preven run-away
reports.

For debugging purposes you could try adding some logging or codesite calls
to the report events themselves.


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