Since few weeks I have regular issues with “Web Intelligence Report Server” on my BO XI R2 (SP5) server.
Daily, there is an average of 35 user sessions on my server, but it can rise to 50.
Anyway, I think my problem isn’t there. I think it is rather the fact that many of these users run Web Intelligence reports (WebI) which are slow to update and containing too much data (up to 50 pages A4).
Could you tell me if my setting is correct considering the use made of my BO XI R2 server) and the characteristics of my server?
FYI, here are the characteristics of my Windows server:
Should I add a second WI Report Server? (NB: RAM = only 4 GB)
Our experience has been once the Webi Report service begins to get more than 24-25 connections, the problems begin. I would recommend reducing from 50 to 25. That should help quite a bit. If it doesn’t completely work try 20. You may need to add additional Webi Report services (dependant on your load and environment). Also, we had to increase our Maximum Binary File size to 100 MBytes.
Before you create another Webi, I was re-reading your post. When you say there are 35 user sessions on your server, is the CMS or Webi Server?
Also, having all BO services on 1 server (even quad core) may be your problem. If you could add even a 2 CPU server w/4GB RAM and put your webi processes on that, it would probably help.
In CMS, but I think it’s the same because all my users use only Web Intelligence Reports, isn’t it?
Yes I guess too, but I have no choice because … no more money for the moment! :?
Finally can I (must I) create a second WI Report Server?
Otherwise, could you explain me why all 3 checkboxes are unchecked?
[list][:c8f686517b]List of Values caching
[:c8f686517b]Enable viewing caching
[*:c8f686517b]Enable Real Time caching[/list]
Use caching doesn’t be a good idea?
I’m lost… These parameters are very unclear in SAP BO documentation!
CMS sessions are how many users are logged in. Users could be logged in to BO without actually running Webi reports constantly (some could be idle, away from desk, …etc). To see how many current requests a Webi Report service has you need to go into Central Management Console (CMC), select servers, click on your webi service and it will display “current connections”.
No, creating another Webi Report instance is not a must, not when all on one server. Check to see if there a pattern for the webi crashes; time of day, particular report(s) being ran at the time of crash? You may find a single report or a group of reports running at a particular time. The trick is to isolate if possible. Do you have monitoring on your server? If the webi report service is running out of memory (2GB max), that can show up with monitoring.
That does not seem unreasonable. I would try to isolate what reports are running when crash occurs. If you have auditting enabled and the audit universe setup, that could help.
I would be very surprised if this was causing Webi Report service to crash unless the server is running out of disk space on the C: drive or whatever drive the cache resides.
(BOB member since 2005-10-02)
